From: Alex Williamson <alex.williamson@redhat.com>
To: Bandan Das <bsd@redhat.com>
Cc: linux-kernel@vger.kernel.org, kvm@vger.kernel.org
Subject: Re: [PATCH] vfio/pci: Add extra test for extended capabilities
Date: Thu, 12 Jun 2014 14:29:02 -0600 [thread overview]
Message-ID: <1402604942.3707.17.camel@ul30vt.home> (raw)
In-Reply-To: <jpgwqclx4yw.fsf@nelium.bos.redhat.com>
On Thu, 2014-06-12 at 16:12 -0400, Bandan Das wrote:
> Alex Williamson <alex.williamson@redhat.com> writes:
>
> > If the PCI core set cfg_size isn't large enough for extended
> > capabilities, then they're not there. Extended config space may be
> > inaccessible due to a PCI bridge, in which case cfg_size may be cut
> > short.
>
> Just curious, is this part of the spec or just a convention ? I mean
> could there be devices with quirks ?
The PCIe bridge spec indicates that PCIe-to-PCI bridges should handle
extended config accesses as an unsupported request. But as in 78916b00,
we've seen that's not always the case. This just makes us trust
PCI-core before the capabilities we find on the device. The current
quirk in the referenced commit is for a relatively uncommon topology,
but never rule out that we couldn't have a device quirked to avoid
touching extended config space too. Thanks,
Alex
> > Signed-off-by: Alex Williamson <alex.williamson@redhat.com>
> > ---
> > drivers/vfio/pci/vfio_pci_config.c | 13 +++++++++----
> > 1 file changed, 9 insertions(+), 4 deletions(-)
> >
> > diff --git a/drivers/vfio/pci/vfio_pci_config.c b/drivers/vfio/pci/vfio_pci_config.c
> > index 83cd157..4a62a37 100644
> > --- a/drivers/vfio/pci/vfio_pci_config.c
> > +++ b/drivers/vfio/pci/vfio_pci_config.c
> > @@ -1027,8 +1027,11 @@ static int vfio_cap_len(struct vfio_pci_device *vdev, u8 cap, u8 pos)
> >
> > if (PCI_X_CMD_VERSION(word)) {
> > /* Test for extended capabilities */
> > - pci_read_config_dword(pdev, PCI_CFG_SPACE_SIZE, &dword);
> > - vdev->extended_caps = (dword != 0);
> > + if (pdev->cfg_size > PCI_CFG_SPACE_SIZE) {
> > + pci_read_config_dword(pdev, PCI_CFG_SPACE_SIZE,
> > + &dword);
> > + vdev->extended_caps = (dword != 0);
> > + }
> > return PCI_CAP_PCIX_SIZEOF_V2;
> > } else
> > return PCI_CAP_PCIX_SIZEOF_V0;
> > @@ -1041,8 +1044,10 @@ static int vfio_cap_len(struct vfio_pci_device *vdev, u8 cap, u8 pos)
> > return byte;
> > case PCI_CAP_ID_EXP:
> > /* Test for extended capabilities */
> > - pci_read_config_dword(pdev, PCI_CFG_SPACE_SIZE, &dword);
> > - vdev->extended_caps = (dword != 0);
> > + if (pdev->cfg_size > PCI_CFG_SPACE_SIZE) {
> > + pci_read_config_dword(pdev, PCI_CFG_SPACE_SIZE, &dword);
> > + vdev->extended_caps = (dword != 0);
> > + }
> >
> > /* length based on version */
> > if ((pcie_caps_reg(pdev) & PCI_EXP_FLAGS_VERS) == 1)
> >
> > --
> > To unsubscribe from this list: send the line "unsubscribe kvm" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2014-06-12 20:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-12 16:44 Alex Williamson
2014-06-12 20:12 ` Bandan Das
2014-06-12 20:29 ` Alex Williamson [this message]
2014-06-12 20:39 ` Bandan Das
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=1402604942.3707.17.camel@ul30vt.home \
--to=alex.williamson@redhat.com \
--cc=bsd@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®