xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Gordan Bobic <gordan@bobich.net>
To: xen-devel@lists.xenproject.org
Subject: Re: Multi-bridged PCIe devices (Was: Re: iommuu/vt-d issues with LSI MegaSAS (PERC5i))
Date: Wed, 11 Sep 2013 12:44:47 +0100	[thread overview]
Message-ID: <8c1b11eec8ed133e55222fa57b4c08a8@mail.shatteredsilicon.net> (raw)
In-Reply-To: <fa31adeb4c9c128acf8bfd952c2c14dc@mail.shatteredsilicon.net>

 This got me thinking - if the problem is broken IOMMU implementation,
 is the IOMMU _actually_ required for PCI passthrough to HVM
 guests if all the memory holes and BARs are made exactly the same
 in dom0 and domU? If vBAR=pBAR, then surely there is no memory
 range remapping to be done anyway - which means that there
 is no need for the strict IOMMU requirements (over and above
 the requirements and caveats of PV domUs).

 In turn, this would enable PCI passthrough (incl. secondary VGA,
 unless I am very much mistaken) to HVM guests while running xen
 with iommu=0. It shifts the design from virtualization to
 partitioning, which I see having obvious advantages and no
 disadvantages (e.g. VM migration doesn't work with PCI
 passthrough anyway).

 The reason I am mentioning this is because I'm working on
 a vhole=phole+vBAR=pBAR patch set anyway, and this would
 be a neat logical extension that would help me work around
 yet more problems on what appears to be a fairly common
 hardware implementation bug.

 Gordan

 On Wed, 11 Sep 2013 12:25:18 +0100, Gordan Bobic <gordan@bobich.net> 
 wrote:
> It looks like I'm definitely not the first person to
> hit this problem:
>
> 
> http://www.gossamer-threads.com/lists/xen/users/168557?do=post_view_threaded#168557
>
> No responses or workarounds suggested back then. :(
>
> Gordan
>
> On Wed, 11 Sep 2013 12:05:35 +0100, Gordan Bobic <gordan@bobich.net> 
> wrote:
>> I found this:
>>
>> http://lists.xen.org/archives/html/xen-devel/2010-06/msg00093.html
>>
>> while looking for a solution to a similar problem. I am
>> facing a similar issue with LSI (8408E, 3081E-R) and
>> Adaptec (31605) SAS cards. Was there ever a proper, more general
>> fix or workaround for this issue?
>>
>> These SAS cards experience these problems in dom0. When running
>> a vanilla kernel on bare metal, they work OK without intel_iommu
>> set. As soon as I set intel_iommu, the same thing happens (on
>> bare metal, not dom0).
>>
>> Clearly there is something badly broken with multiple layers
>> of bridges when it comes to IOMMU in my setup (Intel 5520 PCIe
>> root hub -> NF200 bridge -> Intel 80333 Bridge -> SAS controller)
>>
>> I tried iommu=dom0-passthrough and it doesn't appear to have
>> helped.
>>
>> I am not seeing similar problems with other PCIe devices that
>> are also, in theory doing DMA (e.g. GPUs), but LSI and Adapted
>> controllers appear to be affected for some reason.
>>
>> Is there anything else I could try/do to make this work?
>>
>> Gordan
>>
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@lists.xen.org
>> http://lists.xen.org/xen-devel
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel

  reply	other threads:[~2013-09-11 11:44 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-11 11:05 Multi-bridged PCIe devices (Was: Re: iommuu/vt-d issues with LSI MegaSAS (PERC5i)) Gordan Bobic
2013-09-11 11:25 ` Gordan Bobic
2013-09-11 11:44   ` Gordan Bobic [this message]
2013-09-11 11:57     ` Jan Beulich
2013-09-11 12:19       ` Gordan Bobic
2013-09-11 12:56         ` Pasi Kärkkäinen
2013-09-11 11:53 ` Jan Beulich
2013-09-11 12:14   ` Gordan Bobic
2013-09-11 12:31     ` Jan Beulich
2013-09-11 12:45       ` Gordan Bobic
2013-09-11 13:03         ` Jan Beulich
2013-09-11 13:10           ` Gordan Bobic
2013-09-11 13:22             ` Jan Beulich
2013-09-11 13:26               ` Gordan Bobic
2013-09-11 13:36                 ` Jan Beulich
2013-09-12  6:20                   ` Zhang, Yang Z
2013-12-11 18:32                     ` Konrad Rzeszutek Wilk
2013-12-11 21:15                       ` Gordan Bobic
2013-12-11 21:30                         ` Konrad Rzeszutek Wilk
2013-12-13 11:13                           ` Jan Beulich
2013-12-13 14:43                             ` Konrad Rzeszutek Wilk
2013-12-13 14:56                               ` Jan Beulich
2013-12-13 15:27                                 ` Gordan Bobic
2014-01-06 20:26                                   ` Konrad Rzeszutek Wilk
2014-01-06 21:45                                     ` Konrad Rzeszutek Wilk
2014-01-07  3:17                                       ` Zhang, Yang Z
2014-01-07 10:35                                         ` Gordan Bobic
2014-01-07 10:38                                           ` Andrew Cooper
2014-01-07 10:44                                             ` Gordan Bobic
2014-02-21 19:08                                               ` Konrad Rzeszutek Wilk
2014-02-24 10:14                                                 ` Jan Beulich
2013-09-11 13:23           ` Gordan Bobic
2013-09-11 13:34             ` Jan Beulich
  -- strict thread matches above, loose matches on Subject: below --
2014-01-07 11:26 Wu, Feng
2014-01-07 11:35 ` Gordan Bobic
2014-01-07 12:15   ` Jan Beulich
2014-01-07 12:42     ` Gordan Bobic
2014-01-07 14:38       ` Konrad Rzeszutek Wilk
2014-01-07 14:47         ` Jan Beulich
2014-01-07 15:40           ` 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=8c1b11eec8ed133e55222fa57b4c08a8@mail.shatteredsilicon.net \
    --to=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).