Received: by 2002:a25:d7c1:0:0:0:0:0 with SMTP id o184csp4238543ybg; Tue, 29 Oct 2019 04:18:55 -0700 (PDT) X-Google-Smtp-Source: APXvYqzCpzQBPf5IvSYp24BelmkpHhaPyX0fJX38CH8QdEXacl5Zx2EdTCgOY2Q8KvVZlhHICOxr X-Received: by 2002:a17:906:1e02:: with SMTP id g2mr2682846ejj.6.1572347934955; Tue, 29 Oct 2019 04:18:54 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1572347934; cv=none; d=google.com; s=arc-20160816; b=tsox8MGnL2wa9j/dlYIDBFZle8i+MukXIcYMD3EJfW4Y5wcGaElxeokeh4sK1vgesE cPOeCbU4UrENp+ypqTbHoyCwZtemS2C0NwMzoLbss9ZHpAIbRhy4HDfzXvJjDzCIPFI0 nPJ1uUzAO3QTfjwhxZzBP0uZNMWzSEHt+s6OJ4ViIi9JyJPJuiBZTVBt2efMY/26jGTg aMYcndM1pR4ymjkqQFiv8DhV+WEnYWIDMAcTWk+x7ZepJg24xdDn4zvVXOgm83Q7kI1k S44FatseOi0w6/f7kXGsYh7L91XWTuyk3jHaYvcb7PhJazrcv43GqmFHvdXaDFjC8+Rh WVXw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject:dkim-signature; bh=8QKaEOxWqH0XbEXmeRTfx0XwaFmBJ9rzCJkgjIkFVeU=; b=XghsqwAxt1N+oAA6GhyNwc+x3W3VFAIJpsoe9i8/I76JvRYguSYXR45KnH4AjHyXZL tn3ixkUgl3aPidYV/BLOKDBu4cLcCDVEOO9B/3UlEpVIfQHASFm+42zVYGI3R8Aq2LHQ C898YEWy7CdrOmLB/W2PSrOuK+8v0FWGnKhe/izsb4R0pRloj8U8P+8LljbQrSdxTE3H r5Y36BP41Sy0E4O7Ta2gn4k7TREdRONHvDbFtUUYxD7DIA9b8B/enaV8NW3BENwtpkrE SjKdS2AXN6QsXqBFDTO4ADqyJu8vN657JIh1w8NGDtkoYQhGxMEg8B0YjUd9zdQotLDc G1Ww== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=Tt+d8fz9; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id v26si10244463edd.364.2019.10.29.04.18.31; Tue, 29 Oct 2019 04:18:54 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=Tt+d8fz9; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729994AbfJ2Knt (ORCPT + 99 others); Tue, 29 Oct 2019 06:43:49 -0400 Received: from us-smtp-2.mimecast.com ([205.139.110.61]:22045 "EHLO us-smtp-delivery-1.mimecast.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1726965AbfJ2Knt (ORCPT ); Tue, 29 Oct 2019 06:43:49 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1572345827; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=8QKaEOxWqH0XbEXmeRTfx0XwaFmBJ9rzCJkgjIkFVeU=; b=Tt+d8fz9rBLzEKRtR2jEWVJHoh/7v2uHuNhB644495Cp9YRg71PX4FOwIyi9ufLDFcaHQP QpRb9aqbbLnz0e4iLRNMXTuxUirp7L2rgm5ZOVZSC5NwZaryLYOytLKZGw1DagJczBz15/ U5tdiNyMiwqjUDDfuxlLFtw7re22sZY= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-280-f_q__00gOjOwW2LVCQTfjw-1; Tue, 29 Oct 2019 06:43:43 -0400 Received: from smtp.corp.redhat.com (int-mx02.intmail.prod.int.phx2.redhat.com [10.5.11.12]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id B317E1005500; Tue, 29 Oct 2019 10:43:39 +0000 (UTC) Received: from [10.72.12.223] (ovpn-12-223.pek2.redhat.com [10.72.12.223]) by smtp.corp.redhat.com (Postfix) with ESMTP id 902D960BF1; Tue, 29 Oct 2019 10:42:12 +0000 (UTC) Subject: Re: [PATCH V5 4/6] mdev: introduce virtio device and its device ops To: Zhu Lingshan , kvm@vger.kernel.org, linux-s390@vger.kernel.org, linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org, intel-gfx@lists.freedesktop.org, intel-gvt-dev@lists.freedesktop.org, kwankhede@nvidia.com, alex.williamson@redhat.com, mst@redhat.com, tiwei.bie@intel.com Cc: virtualization@lists.linux-foundation.org, netdev@vger.kernel.org, cohuck@redhat.com, maxime.coquelin@redhat.com, cunming.liang@intel.com, zhihong.wang@intel.com, rob.miller@broadcom.com, xiao.w.wang@intel.com, haotian.wang@sifive.com, zhenyuw@linux.intel.com, zhi.a.wang@intel.com, jani.nikula@linux.intel.com, joonas.lahtinen@linux.intel.com, rodrigo.vivi@intel.com, airlied@linux.ie, daniel@ffwll.ch, farman@linux.ibm.com, pasic@linux.ibm.com, sebott@linux.ibm.com, oberpar@linux.ibm.com, heiko.carstens@de.ibm.com, gor@linux.ibm.com, borntraeger@de.ibm.com, akrowiak@linux.ibm.com, freude@linux.ibm.com, lingshan.zhu@intel.com, idos@mellanox.com, eperezma@redhat.com, lulu@redhat.com, parav@mellanox.com, christophe.de.dinechin@gmail.com, kevin.tian@intel.com, stefanha@redhat.com References: <20191023130752.18980-1-jasowang@redhat.com> <20191023130752.18980-5-jasowang@redhat.com> From: Jason Wang Message-ID: <14410ac9-cc01-185a-5dcf-7f6c78aefd65@redhat.com> Date: Tue, 29 Oct 2019 18:42:11 +0800 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0 MIME-Version: 1.0 In-Reply-To: Content-Language: en-US X-Scanned-By: MIMEDefang 2.79 on 10.5.11.12 X-MC-Unique: f_q__00gOjOwW2LVCQTfjw-1 X-Mimecast-Spam-Score: 0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2019/10/29 =E4=B8=8B=E5=8D=883:42, Zhu Lingshan wrote: >> >> +=C2=A0=C2=A0=C2=A0 void (*set_status)(struct mdev_device *mdev, u8 stat= us); > > Hi Jason > > Is it possible to make set_status() return an u8 or bool, because this > may fail in real hardware. Without a returned code, I am not sure=C2=A0 > whether it is a good idea to set the status | NEED_RESET when fail. > > Thanks, > BR > Zhu Lingshan=20 Hi: It's possible but I'm not sure whether any user will care about it. E.g see virtio_add_status(): void virtio_add_status(struct virtio_device *dev, unsigned int status) { =C2=A0=C2=A0=C2=A0 might_sleep(); =C2=A0=C2=A0=C2=A0 dev->config->set_status(dev, dev->config->get_status(dev= ) | status); } EXPORT_SYMBOL_GPL(virtio_add_status); And I believe how it work should be: virtio_add_status(xyz); status =3D virtio_get_status(); if (!(status & xyz)) =C2=A0=C2=A0=C2=A0 error; Thanks