From: Parav Pandit <parav@nvidia.com> To: "Michael S. Tsirkin" <mst@redhat.com> Cc: Cornelia Huck <cohuck@redhat.com>, Heng Qi <hengqi@linux.alibaba.com>, "virtio-dev@lists.oasis-open.org" <virtio-dev@lists.oasis-open.org>, "virtio-comment@lists.oasis-open.org" <virtio-comment@lists.oasis-open.org>, Jason Wang <jasowang@redhat.com>, Alvaro Karsz <alvaro.karsz@solid-run.com>, David Edmondson <david.edmondson@oracle.com>, Xuan Zhuo <xuanzhuo@linux.alibaba.com> Subject: [virtio-dev] RE: [virtio-comment] RE: [PATCH v13] virtio-net: support the virtqueue coalescing moderation Date: Wed, 22 Mar 2023 17:02:52 +0000 [thread overview] Message-ID: <PH0PR12MB5481B513EF0CAD4020A4C246DC869@PH0PR12MB5481.namprd12.prod.outlook.com> (raw) In-Reply-To: <20230322125058-mutt-send-email-mst@kernel.org> > From: Michael S. Tsirkin <mst@redhat.com> > Sent: Wednesday, March 22, 2023 12:53 PM > > On Wed, Mar 22, 2023 at 04:49:58PM +0000, Parav Pandit wrote: > > > > > From: Michael S. Tsirkin <mst@redhat.com> > > > Sent: Wednesday, March 22, 2023 12:47 PM > > > > > > I agree with Cornelia here. Yes if devices do not want to trust > > > drivers then they will validate input but what exactly happens then is > currently up to device. > > > If we want to try and specify devices in all cases of out of spec > > > input that's a big project, certainly doable but I would rather not > > > connect it to this, rather boutique, feature. > > Both of your and Cornelia's comment is abstract to me. > > We cannot change past. > > But we can make sure things are consistent. Currently we don't describe device > behaviour if driver is out of spec and I see 0 reasons to start doing it with > coalescing commands specifically. > > > For the new command of interest here, hen driver supplied incorrect values, > the device will return error. > > It might be easier for device to just set NEEDS_RESET and stop responding. This approach of treating all errors as a fatal category is completely the opposite of making the device and driver resilient to (recoverable) errors. We shouldn't go this route. Different discussion... > For > a hypervisor implementation that's often better than returning error since > device state is then preserved making things easier to debug. > > > How to implement is upto the device to figure out. > > > what to do is also up to the device. Previously error code as not returned hence new command cannot return the error code is going backward. Returning the failure code is a way to indicate that the driver had a recoverable error. --------------------------------------------------------------------- To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org
WARNING: multiple messages have this Message-ID (diff)
From: Parav Pandit <parav@nvidia.com> To: "Michael S. Tsirkin" <mst@redhat.com> Cc: Cornelia Huck <cohuck@redhat.com>, Heng Qi <hengqi@linux.alibaba.com>, "virtio-dev@lists.oasis-open.org" <virtio-dev@lists.oasis-open.org>, "virtio-comment@lists.oasis-open.org" <virtio-comment@lists.oasis-open.org>, Jason Wang <jasowang@redhat.com>, Alvaro Karsz <alvaro.karsz@solid-run.com>, David Edmondson <david.edmondson@oracle.com>, Xuan Zhuo <xuanzhuo@linux.alibaba.com> Subject: RE: [virtio-comment] RE: [PATCH v13] virtio-net: support the virtqueue coalescing moderation Date: Wed, 22 Mar 2023 17:02:52 +0000 [thread overview] Message-ID: <PH0PR12MB5481B513EF0CAD4020A4C246DC869@PH0PR12MB5481.namprd12.prod.outlook.com> (raw) In-Reply-To: <20230322125058-mutt-send-email-mst@kernel.org> > From: Michael S. Tsirkin <mst@redhat.com> > Sent: Wednesday, March 22, 2023 12:53 PM > > On Wed, Mar 22, 2023 at 04:49:58PM +0000, Parav Pandit wrote: > > > > > From: Michael S. Tsirkin <mst@redhat.com> > > > Sent: Wednesday, March 22, 2023 12:47 PM > > > > > > I agree with Cornelia here. Yes if devices do not want to trust > > > drivers then they will validate input but what exactly happens then is > currently up to device. > > > If we want to try and specify devices in all cases of out of spec > > > input that's a big project, certainly doable but I would rather not > > > connect it to this, rather boutique, feature. > > Both of your and Cornelia's comment is abstract to me. > > We cannot change past. > > But we can make sure things are consistent. Currently we don't describe device > behaviour if driver is out of spec and I see 0 reasons to start doing it with > coalescing commands specifically. > > > For the new command of interest here, hen driver supplied incorrect values, > the device will return error. > > It might be easier for device to just set NEEDS_RESET and stop responding. This approach of treating all errors as a fatal category is completely the opposite of making the device and driver resilient to (recoverable) errors. We shouldn't go this route. Different discussion... > For > a hypervisor implementation that's often better than returning error since > device state is then preserved making things easier to debug. > > > How to implement is upto the device to figure out. > > > what to do is also up to the device. Previously error code as not returned hence new command cannot return the error code is going backward. Returning the failure code is a way to indicate that the driver had a recoverable error. This publicly archived list offers a means to provide input to the OASIS Virtual I/O Device (VIRTIO) TC. In order to verify user consent to the Feedback License terms and to minimize spam in the list archive, subscription is required before posting. Subscribe: virtio-comment-subscribe@lists.oasis-open.org Unsubscribe: virtio-comment-unsubscribe@lists.oasis-open.org List help: virtio-comment-help@lists.oasis-open.org List archive: https://lists.oasis-open.org/archives/virtio-comment/ Feedback License: https://www.oasis-open.org/who/ipr/feedback_license.pdf List Guidelines: https://www.oasis-open.org/policies-guidelines/mailing-lists Committee: https://www.oasis-open.org/committees/virtio/ Join OASIS: https://www.oasis-open.org/join/
next prev parent reply other threads:[~2023-03-22 17:03 UTC|newest] Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-03-22 12:51 [virtio-dev] [PATCH v13] virtio-net: support the virtqueue coalescing moderation Heng Qi 2023-03-22 12:51 ` [virtio-comment] " Heng Qi 2023-03-22 15:20 ` [virtio-dev] " Cornelia Huck 2023-03-22 15:20 ` [virtio-comment] " Cornelia Huck 2023-03-22 16:23 ` [virtio-dev] " Parav Pandit 2023-03-22 16:23 ` [virtio-comment] " Parav Pandit 2023-03-22 16:36 ` [virtio-dev] " Cornelia Huck 2023-03-22 16:36 ` [virtio-comment] " Cornelia Huck 2023-03-22 16:40 ` [virtio-dev] " Parav Pandit 2023-03-22 16:40 ` [virtio-comment] " Parav Pandit 2023-03-22 16:44 ` [virtio-dev] " Cornelia Huck 2023-03-22 16:44 ` Cornelia Huck 2023-03-22 16:46 ` [virtio-dev] " Parav Pandit 2023-03-22 16:46 ` Parav Pandit 2023-03-22 16:50 ` [virtio-dev] " Michael S. Tsirkin 2023-03-22 16:50 ` Michael S. Tsirkin 2023-03-22 16:46 ` [virtio-dev] " Michael S. Tsirkin 2023-03-22 16:46 ` Michael S. Tsirkin 2023-03-22 16:49 ` [virtio-dev] " Parav Pandit 2023-03-22 16:49 ` Parav Pandit 2023-03-22 16:53 ` [virtio-dev] " Michael S. Tsirkin 2023-03-22 16:53 ` Michael S. Tsirkin 2023-03-22 17:02 ` Parav Pandit [this message] 2023-03-22 17:02 ` Parav Pandit 2023-03-23 2:26 ` [virtio-dev] " Heng Qi 2023-03-23 2:26 ` [virtio-comment] " Heng Qi
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=PH0PR12MB5481B513EF0CAD4020A4C246DC869@PH0PR12MB5481.namprd12.prod.outlook.com \ --to=parav@nvidia.com \ --cc=alvaro.karsz@solid-run.com \ --cc=cohuck@redhat.com \ --cc=david.edmondson@oracle.com \ --cc=hengqi@linux.alibaba.com \ --cc=jasowang@redhat.com \ --cc=mst@redhat.com \ --cc=virtio-comment@lists.oasis-open.org \ --cc=virtio-dev@lists.oasis-open.org \ --cc=xuanzhuo@linux.alibaba.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.