RE: [PATCH] VIRTIO_F_USED_EVENT_AUTO_DISABLE: add new used buffer notification suppression mechanism

Parav Pandit
2024-07-08T02:33:22Z

> From: Michael S. Tsirkin <mst@redhat.com>
> Sent: Friday, July 5, 2024 1:55 PM
> To: Parav Pandit <parav@nvidia.com>
> Cc: Lege Wang <lege.wang@jaguarmicro.com>; Jason Wang
> <jasowang@redhat.com>; virtio-comment@lists.linux.dev;
> vattunuru@marvell.com; ndabilpuram@marvell.com; Leo Liu
> <leo.liu@jaguarmicro.com>; Angus Chen <angus.chen@jaguarmicro.com>
> Subject: Re: [PATCH] VIRTIO_F_USED_EVENT_AUTO_DISABLE: add new used
> buffer notification suppression mechanism
>
> On Fri, Jul 05, 2024 at 04:42:52AM +0000, Parav Pandit wrote:
> > 1. pci capability area (non-extended cap) is full to its capacity. New addition
> can only work in theory.
> > An obvious alternative is to add the extended cap and add there.
> > However, it is not a good idea either as the PCI spec strongly recommends
> to not keep adding vendor specific stuff in the PCI capability section.
> > (even though an option is kept for the vendor capability).
>
> To stress, we need to solve this problem, even if the specific issue can be
> worked around differently, we keep adding new caps.
>
Yes.
When the new use case arise, lets understand, whether its need to be discovered before device reset or after device reset.
Depending on use case capabilities can be learnt by different ways.