From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>, gordan@bobich.net
Subject: Re: Dealing with non-existent BDF devices in VT-d and in the hardware.
Date: Wed, 12 Mar 2014 10:22:03 -0400 [thread overview]
Message-ID: <20140312142203.GG3245@phenom.dumpdata.com> (raw)
In-Reply-To: <5320345702000078001231C2@nat28.tlf.novell.com>
On Wed, Mar 12, 2014 at 09:17:59AM +0000, Jan Beulich wrote:
> >>> On 11.03.14 at 18:30, Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> wrote:
> > To use this hack, apply the
> > 0001-xen-pci-Introduce-a-way-to-deal-with-buggy-hardware-.patch
> > to your hypervisor, compile and install.
>
> I'm still rather hesitant to consider such a pretty involved
> workaround for general inclusion. Did you investigate whether
> leveraging the grouping functionality (iommu_get_device_group())
> might be possible instead? We're talking about a legacy PCI bridge
> after all, and if done that way also covering the AMD IOMMU case
> might be more straightforward (after all that case is missing from
> your already large patch).
<nods>
I think other people have experienced other non-bridge issues.
I have CC-ed Gordan on this as he had a LSI card that was misbehaving.
I am curious to see what his lspci and lspci -vt looks for his culprit.
>
> While looking over this, I found that this only has a use in xend -
> another xl deficiency? And only for checking purposes, rather
Gosh.
> than to enforce the assignment of all (non-bridge?) devices in
> the group...
>
> Jan
>
next prev parent reply other threads:[~2014-03-12 14:22 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-11 17:30 Dealing with non-existent BDF devices in VT-d and in the hardware Konrad Rzeszutek Wilk
2014-03-11 17:36 ` Andrew Cooper
2014-03-11 17:49 ` Konrad Rzeszutek Wilk
2014-03-14 2:18 ` Zhang, Yang Z
2014-03-14 17:51 ` Konrad Rzeszutek Wilk
2014-03-17 1:03 ` Zhang, Yang Z
2014-03-17 20:00 ` Konrad Rzeszutek Wilk
2014-03-19 0:32 ` Zhang, Yang Z
2014-03-19 12:57 ` Konrad Rzeszutek Wilk
2014-03-19 14:24 ` Jan Beulich
2014-03-20 0:48 ` Zhang, Yang Z
2014-03-20 7:14 ` Gordan Bobic
2014-03-20 10:04 ` Jan Beulich
2014-03-20 9:58 ` Jan Beulich
2014-03-24 2:37 ` Zhang, Yang Z
2014-03-24 7:25 ` Jan Beulich
2014-03-12 9:17 ` Jan Beulich
2014-03-12 14:22 ` Konrad Rzeszutek Wilk [this message]
2014-03-12 17:10 ` Gordan Bobic
-- strict thread matches above, loose matches on Subject: below --
2014-03-20 1:34 Konrad Rzeszutek Wilk
2014-03-20 10:02 ` Jan Beulich
2014-03-20 19:44 ` Konrad Rzeszutek Wilk
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=20140312142203.GG3245@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=JBeulich@suse.com \
--cc=gordan@bobich.net \
--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).