qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Alex Williamson <alex.williamson@redhat.com>
To: Bandan Das <bsd@redhat.com>
Cc: jb-gnumlists@wisemo.com, leedom@chelsio.com, mst@redhat.com,
	qemu-devel@nongnu.org, anish@chelsio.com, mboksanyi@chelsio.com,
	Gabriel Laupre <glaupre@chelsio.com>,
	bsd@makefile.in
Subject: Re: [Qemu-devel] [PATCH v3] pci : Add pba_offset PCI quirk for Chelsio T5 devices
Date: Tue, 30 Jun 2015 16:28:41 -0600	[thread overview]
Message-ID: <1435703321.3700.544.camel@redhat.com> (raw)
In-Reply-To: <jpgbnfwoo44.fsf@redhat.com>

On Tue, 2015-06-30 at 17:58 -0400, Bandan Das wrote:
> Gabriel Laupre <glaupre@chelsio.com> writes:
> ...
> > +    /* Test the size of the pba variables and catch if they extend outside of
> > +     * the specified BAR. If it is the case, we have a broken configuration or
> > +     * we need to apply a hardware specific quirk. */
> > +    if (vdev->msix->table_offset >=
> > +        vdev->bars[vdev->msix->table_bar].region.size ||
> > +        vdev->msix->pba_offset >=
> > +        vdev->bars[vdev->msix->pba_bar].region.size) {
> > +
> > +        PCIDevice *pdev = &vdev->pdev;
> > +        uint16_t vendor = pci_get_word(pdev->config + PCI_VENDOR_ID);
> > +        uint16_t device = pci_get_word(pdev->config + PCI_DEVICE_ID);
> > +
> > +        /* Chelsio T5 Virtual Function devices are encoded as 0x58xx for T5
> > +         * adapters. The T5 hardware returns an incorrect value of 0x8000 for
> > +         * the VF PBA offset. The correct value is 0x1000, so we hard code that
> > +         * here. */
> > +        if (vendor == PCI_VENDOR_ID_CHELSIO && (device & 0xff00) == 0x5800) {
> > +            vdev->msix->pba_offset = 0x1000;
> 
> For the rare case where table_offset is wrong for the device being checked for
> above and pba_offset is actually correct, shouldn't we fail ?
> 
> > +        } else {
> > +            error_report("vfio: Hardware reports invalid configuration, "
> > +            "MSIX data outside of specified BAR");
> 
> Since we are printing anyway, and we have already made the check above, why
> not print exactly what's wrong instead of "MSIX data" ?

Probably diminishing returns to get too specific, we just need to know
that it's a hardware bug.  If we want the test to be more thorough, it
should be extracted from msix_init() so we're not duplicating code.
Thanks,

Alex

> > +            return -EINVAL;
> > +        }
> > +    }
> > +
> >      trace_vfio_early_setup_msix(vdev->vbasedev.name, pos,
> >                                  vdev->msix->table_bar,
> >                                  vdev->msix->table_offset,
> > diff --git a/include/hw/pci/pci_ids.h b/include/hw/pci/pci_ids.h
> > index 49c062b..d98e6c9 100644
> > --- a/include/hw/pci/pci_ids.h
> > +++ b/include/hw/pci/pci_ids.h
> > @@ -114,6 +114,8 @@
> >  #define PCI_VENDOR_ID_ENSONIQ            0x1274
> >  #define PCI_DEVICE_ID_ENSONIQ_ES1370     0x5000
> >  
> > +#define PCI_VENDOR_ID_CHELSIO            0x1425
> > +
> >  #define PCI_VENDOR_ID_FREESCALE          0x1957
> >  #define PCI_DEVICE_ID_MPC8533E           0x0030

  reply	other threads:[~2015-06-30 22:28 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-30 21:03 [Qemu-devel] [PATCH v3] pci : Add pba_offset PCI quirk for Chelsio T5 devices Gabriel Laupre
2015-06-30 21:35 ` Alex Williamson
2015-06-30 21:58 ` Bandan Das
2015-06-30 22:28   ` Alex Williamson [this message]
2015-06-30 22:59     ` Casey Leedom
2015-07-01  1:28   ` Gabriel Laupre
2015-07-01  1:47     ` Bandan Das
2015-07-01  1:53       ` Gabriel Laupre
2015-07-01  2:13       ` Gabriel Laupre
2015-07-01 18:10       ` Gabriel Laupre
2015-07-01 18:18         ` Alex Williamson
2015-07-01 18:27           ` 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=1435703321.3700.544.camel@redhat.com \
    --to=alex.williamson@redhat.com \
    --cc=anish@chelsio.com \
    --cc=bsd@makefile.in \
    --cc=bsd@redhat.com \
    --cc=glaupre@chelsio.com \
    --cc=jb-gnumlists@wisemo.com \
    --cc=leedom@chelsio.com \
    --cc=mboksanyi@chelsio.com \
    --cc=mst@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).