From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: andrew.cooper3@citrix.com, xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: [acooks@gmail.com: Re: [RFC PATCH v2 1/2] pci: Create PCIe requester ID interface]
Date: Mon, 5 Aug 2013 10:31:41 -0400 [thread overview]
Message-ID: <20130805143141.GG3321@phenom.dumpdata.com> (raw)
In-Reply-To: <51FFB4AD02000078000E943A@nat28.tlf.novell.com>
On Mon, Aug 05, 2013 at 01:20:29PM +0100, Jan Beulich wrote:
> >>> On 24.07.13 at 18:26, Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> wrote:
> > Does it make sense to integrate these PCI ids as part of the
> > phantom device? Right now we have a parameter where one
> > can specify them, but this is a nice complete list of the
> > actual devices.
>
> I don't mind adding such a table, but I'm also not eager to do
> so myself...
Hehe. OK, I will prep a patch and up-date it as it is done in Linux.
>
> Jan
>
> > Here's a table of affected devices with links to the
> > bug reports. In each case both functions 0 and 1 are used.
> >
> > static const struct pci_dev_dma_multi_source_map {
> > u16 vendor;
> > u16 device;
> > } pci_dev_dma_multi_source_map[] = {
> > /* Reported by Patrick Bregman
> > * https://bugzilla.redhat.com/show_bug.cgi?id=863653 */
> > { PCI_VENDOR_ID_MARVELL_EXT, 0x9120},
> >
> > /* Reported by Paweł Żak, Korneliusz Jarzębski, Daniel Mayer
> > * https://bugzilla.kernel.org/show_bug.cgi?id=42679 and by
> > * Justin Piszcz https://lkml.org/lkml/2012/11/24/94 */
> > { PCI_VENDOR_ID_MARVELL_EXT, 0x9123},
> >
> > /* Reported by Robert Cicconetti
> > * https://bugzilla.kernel.org/show_bug.cgi?id=42679 and by
> > * Fernando https://bugzilla.redhat.com/show_bug.cgi?id=757166 */
> > { PCI_VENDOR_ID_MARVELL_EXT, 0x9128},
> >
> > /* Reported by Stijn Tintel
> > * https://bugzilla.kernel.org/show_bug.cgi?id=42679 */
> > { PCI_VENDOR_ID_MARVELL_EXT, 0x9130},
> >
> > /* Reported by Gaudenz Steinlin
> > * https://lkml.org/lkml/2013/3/5/288 */
> > { PCI_VENDOR_ID_MARVELL_EXT, 0x9143},
> >
> > /* Reported by Andrew Cooks
> > * https://bugzilla.kernel.org/show_bug.cgi?id=42679 */
> > { PCI_VENDOR_ID_MARVELL_EXT, 0x9172}
> > };
>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
prev parent reply other threads:[~2013-08-05 14:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-24 16:26 [acooks@gmail.com: Re: [RFC PATCH v2 1/2] pci: Create PCIe requester ID interface] Konrad Rzeszutek Wilk
2013-08-05 12:20 ` Jan Beulich
2013-08-05 14:31 ` Konrad Rzeszutek Wilk [this message]
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=20130805143141.GG3321@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=xen-devel@lists.xenproject.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).