From: "Michael S. Tsirkin" <mst@redhat.com>
To: Parav Pandit <parav@nvidia.com>
Cc: Sergio Lopez <slp@redhat.com>,
"virtio-comment@lists.linux.dev" <virtio-comment@lists.linux.dev>
Subject: Re: [PATCH 1/3] shared-mem: introduce page alignment restrictions
Date: Tue, 4 Mar 2025 05:52:49 -0500 [thread overview]
Message-ID: <20250304055002-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <CY8PR12MB7195A2AFBB7530874D228954DCC12@CY8PR12MB7195.namprd12.prod.outlook.com>
On Sun, Feb 23, 2025 at 05:21:00AM +0000, Parav Pandit wrote:
> Overall extending pci cap structure is not good idea even though it may appear as small change for below reasons.
>
> 1. PCI spec already ran out of total bytes that can be stored in the capability section. Extending it will not help.
> A virtio level extended capability is not good either due to below guidance from PCI-SIG.
>
> 2. PCI spec highly discouraged putting vendor specific bits like this in the capability section.
> Citation: "It is strongly recommended that PCI Express devices place no registers in Configuration Space other than those in
> headers or Capability structures architected by applicable PCI specifications."
We can argue about new capabilities, but this is not doing it - it is
merely extending the existing one.
So I do not really get any of these arguments.
I'd be open to an alternative way to discover capabilities, as long as
we don't do that, I don't really see a reason to block minor tweaks
like this one.
At the same time, I am not sure why this is a capability at all.
why not in config space?
--
MST
next prev parent reply other threads:[~2025-03-04 10:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-17 11:52 [PATCH 0/3] shared-mem: introduce page alignment restrictions Sergio Lopez
2025-02-17 11:52 ` [PATCH 1/3] " Sergio Lopez
2025-02-23 5:21 ` Parav Pandit
2025-02-26 17:49 ` Sergio Lopez Pascual
2025-03-05 11:18 ` Parav Pandit
2025-03-05 19:08 ` Sergio Lopez Pascual
2025-03-06 3:09 ` Parav Pandit
2025-03-04 10:40 ` Michael S. Tsirkin
2025-03-04 10:52 ` Michael S. Tsirkin [this message]
2025-03-04 10:58 ` Parav Pandit
2025-03-04 12:50 ` Michael S. Tsirkin
2025-02-17 11:52 ` [PATCH 2/3] transport-pci: VIRTIO_F_SHM_PAGE_SIZE support Sergio Lopez
2025-02-17 11:52 ` [PATCH 3/3] transport-mmio: VIRTIO_F_SHM_PAGE_SIZE Sergio Lopez
2025-02-20 2:15 ` [PATCH 0/3] shared-mem: introduce page alignment restrictions Dmitry Osipenko
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=20250304055002-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=parav@nvidia.com \
--cc=slp@redhat.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 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.