From: "Michael S. Tsirkin" <mst@redhat.com>
To: Parav Pandit <parav@nvidia.com>
Cc: Lege Wang <lege.wang@jaguarmicro.com>,
Jason Wang <jasowang@redhat.com>,
"virtio-comment@lists.linux.dev" <virtio-comment@lists.linux.dev>,
"vattunuru@marvell.com" <vattunuru@marvell.com>,
"ndabilpuram@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
Date: Fri, 5 Jul 2024 04:25:04 -0400 [thread overview]
Message-ID: <20240705042420-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <PH0PR12MB5481C9F0175734E5036FA2A6DCDF2@PH0PR12MB5481.namprd12.prod.outlook.com>
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.
--
MST
next prev parent reply other threads:[~2024-07-05 8:25 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-01 3:44 [PATCH] VIRTIO_F_USED_EVENT_AUTO_DISABLE: add new used buffer notification suppression mechanism Xiaoguang Wang
2024-07-01 8:24 ` Lege Wang
2024-07-02 1:15 ` Xuan Zhuo
2024-07-02 5:30 ` [EXTERNAL] " Vamsi Krishna Attunuru
2024-07-02 7:40 ` Jason Wang
2024-07-03 4:32 ` Lege Wang
2024-07-03 5:10 ` Jason Wang
2024-07-03 7:37 ` Lege Wang
2024-07-03 7:59 ` Jason Wang
2024-07-03 8:36 ` Michael S. Tsirkin
2024-07-03 8:47 ` Jason Wang
2024-07-03 9:08 ` Michael S. Tsirkin
2024-07-04 5:37 ` Jason Wang
2024-07-04 8:30 ` Michael S. Tsirkin
2024-07-05 5:48 ` Jason Wang
2024-07-05 7:48 ` Michael S. Tsirkin
2024-07-08 1:39 ` Jason Wang
2024-07-02 12:00 ` Michael S. Tsirkin
2024-07-03 6:52 ` Lege Wang
2024-07-03 8:28 ` Michael S. Tsirkin
2024-07-03 12:14 ` Lege Wang
2024-07-03 12:34 ` Michael S. Tsirkin
2024-07-04 2:27 ` Lege Wang
2024-07-05 7:57 ` Michael S. Tsirkin
2024-07-05 11:12 ` Lege Wang
2024-07-05 11:29 ` Michael S. Tsirkin
2024-07-05 3:35 ` Lege Wang
2024-07-05 4:42 ` Parav Pandit
2024-07-05 7:52 ` Michael S. Tsirkin
2024-07-08 2:37 ` Parav Pandit
2024-07-05 8:25 ` Michael S. Tsirkin [this message]
2024-07-08 2:33 ` Parav Pandit
2024-07-05 8:00 ` Michael S. Tsirkin
2024-11-05 16:23 ` [EXTERNAL] " Vamsi Krishna Attunuru
2024-11-06 4:33 ` Jason Wang
2024-11-06 11:11 ` Vamsi Krishna Attunuru
2024-11-06 7:40 ` Michael S. Tsirkin
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=20240705042420-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=angus.chen@jaguarmicro.com \
--cc=jasowang@redhat.com \
--cc=lege.wang@jaguarmicro.com \
--cc=leo.liu@jaguarmicro.com \
--cc=ndabilpuram@marvell.com \
--cc=parav@nvidia.com \
--cc=vattunuru@marvell.com \
--cc=virtio-comment@lists.linux.dev \
/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: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox