From: Alex Williamson <alex.williamson@redhat.com>
To: Chris Wright <chrisw@sous-sol.org>
Cc: Donald Dutile <ddutile@redhat.com>, kvm@vger.kernel.org, mst@redhat.com
Subject: Re: [PATCH v3] pci: correct pci config size default for cap version 2 endpoints
Date: Fri, 22 Jul 2011 15:30:31 -0600 [thread overview]
Message-ID: <1311370232.2653.100.camel@bling.home> (raw)
In-Reply-To: <20110722212422.GH9766@sequoia.sous-sol.org>
On Fri, 2011-07-22 at 14:24 -0700, Chris Wright wrote:
> * Donald Dutile (ddutile@redhat.com) wrote:
> > diff --git a/hw/device-assignment.c b/hw/device-assignment.c
> > index 36ad6b0..34db52e 100644
> > --- a/hw/device-assignment.c
> > +++ b/hw/device-assignment.c
> > @@ -1419,16 +1419,18 @@ static int assigned_device_pci_cap_init(PCIDevice *pci_dev)
> > }
> >
> > if ((pos = pci_find_cap_offset(pci_dev, PCI_CAP_ID_EXP, 0))) {
> > - uint8_t version;
> > + uint8_t version, size;
> > uint16_t type, devctl, lnkcap, lnksta;
> > uint32_t devcap;
> > - int size = 0x3c; /* version 2 size */
> >
> > version = pci_get_byte(pci_dev->config + pos + PCI_EXP_FLAGS);
> > version &= PCI_EXP_FLAGS_VERS;
> > if (version == 1) {
> > size = 0x14;
> > - } else if (version > 2) {
> > + } else if (version == 2) {
> > + /* don't include slot cap/stat/ctrl 2 regs; only support endpoints */
> > + size = 0x34;
>
> That doesn't look correct to me. The size is fixed, just that some
> registers are Reserved Zero when they do not apply (e.g. endpoint only).
Apparently it can be interpreted differently. In this case, we've seen
a tg3 device expose a v2 PCI express capability at offset 0xcc. Using
0x3c bytes, we extend 8 bytes past the legacy config space area :(
Alex
next prev parent reply other threads:[~2011-07-22 21:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-22 15:59 [PATCH v3] pci: correct pci config size default for cap version 2 endpoints Donald Dutile
2011-07-22 17:00 ` Alex Williamson
2011-07-22 21:24 ` Chris Wright
2011-07-22 21:30 ` Alex Williamson [this message]
2011-07-22 21:35 ` Chris Wright
2011-07-24 8:12 ` Michael S. Tsirkin
2011-07-24 8:41 ` Michael S. Tsirkin
2011-07-24 10:58 ` Michael S. Tsirkin
2011-07-25 19:37 ` Don Dutile
2011-07-25 20:20 ` Alex Williamson
2011-07-25 20:42 ` Don Dutile
2011-07-26 10:46 ` Michael S. Tsirkin
2011-08-08 18:44 ` Chris Wright
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=1311370232.2653.100.camel@bling.home \
--to=alex.williamson@redhat.com \
--cc=chrisw@sous-sol.org \
--cc=ddutile@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mst@redhat.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: 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