From: Alex Williamson <alex.williamson@redhat.com>
To: Peter Xu <peterx@redhat.com>
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
qemu-devel@nongnu.org, Marcel Apfelbaum <marcel@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] pci/pcie: don't assume cap id 0 is reserved
Date: Wed, 15 Feb 2017 19:52:35 -0700 [thread overview]
Message-ID: <20170215195235.660c45fe@t450s.home> (raw)
In-Reply-To: <20170216023528.GE15985@pxdev.xzpeter.org>
On Thu, 16 Feb 2017 10:35:28 +0800
Peter Xu <peterx@redhat.com> wrote:
> On Wed, Feb 15, 2017 at 10:49:47PM +0200, Michael S. Tsirkin wrote:
> > VFIO actually wants to create a capability with ID == 0.
> > This is done to make guest drivers skip the given capability.
> > pcie_add_capability then trips up on this capability
> > when looking for end of capability list.
> >
> > To support this use-case, it's easy enough to switch to
> > e.g. 0xffffffff for these comparisons - we can be sure
> > it will never match a 16-bit capability ID.
> >
> > Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
>
> Reviewed-by: Peter Xu <peterx@redhat.com>
>
> Two nits:
>
> (1) maybe we can s/0xffffffff/0xffff/ in the whole patch since ecap_id
> is 16 bits
The former is used because it's beyond the address space of a valid
capability. Using 0xffff just makes the situation different, not
better.
>
> (2) maybe we can add one more sentence in the comment below showing
> where the 0xffff thing comes from (it comes from PCIe spec 7.9.2)
The capability in hardware is 16bits, thus a value that exceeds 16 bits
can never match a valid ID. It has nothing to do with 7.9.2. Thanks,
Alex
> > ---
> > hw/pci/pcie.c | 11 +++++++----
> > 1 file changed, 7 insertions(+), 4 deletions(-)
> >
> > diff --git a/hw/pci/pcie.c b/hw/pci/pcie.c
> > index cbd4bb4..f4dd177 100644
> > --- a/hw/pci/pcie.c
> > +++ b/hw/pci/pcie.c
> > @@ -610,7 +610,8 @@ bool pcie_cap_is_arifwd_enabled(const PCIDevice *dev)
> > * uint16_t ext_cap_size
> > */
> >
> > -static uint16_t pcie_find_capability_list(PCIDevice *dev, uint16_t cap_id,
> > +/* Passing a cap_id value > 0xffff will return 0 and put end of list in prev */
> > +static uint16_t pcie_find_capability_list(PCIDevice *dev, uint32_t cap_id,
> > uint16_t *prev_p)
> > {
> > uint16_t prev = 0;
> > @@ -679,9 +680,11 @@ void pcie_add_capability(PCIDevice *dev,
> > } else {
> > uint16_t prev;
> >
> > - /* 0 is reserved cap id. use internally to find the last capability
> > - in the linked list */
> > - next = pcie_find_capability_list(dev, 0, &prev);
> > + /*
> > + * 0xffffffff is not a valid cap id (it's a 16 bit field). use
> > + * internally to find the last capability in the linked list.
> > + */
> > + next = pcie_find_capability_list(dev, 0xffffffff, &prev);
> >
> > assert(prev >= PCI_CONFIG_SPACE_SIZE);
> > assert(next == 0);
> > --
> > MST
>
> -- peterx
next prev parent reply other threads:[~2017-02-16 2:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-15 20:49 [Qemu-devel] [PATCH] pci/pcie: don't assume cap id 0 is reserved Michael S. Tsirkin
2017-02-15 21:33 ` Alex Williamson
2017-02-16 2:35 ` Peter Xu
2017-02-16 2:52 ` Alex Williamson [this message]
2017-02-16 3:04 ` Peter Xu
2017-02-16 3:49 ` Peter Xu
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=20170215195235.660c45fe@t450s.home \
--to=alex.williamson@redhat.com \
--cc=marcel@redhat.com \
--cc=mst@redhat.com \
--cc=peterx@redhat.com \
--cc=qemu-devel@nongnu.org \
/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;
as well as URLs for NNTP newsgroup(s).