From: Alex Williamson <alex.williamson@redhat.com>
To: Steven DuChene <steven.duchene@hp.com>
Cc: kvm@vger.kernel.org
Subject: Re: Device is ineligible for IOMMU domain attach due to platform RMRR requirement
Date: Sat, 07 Mar 2015 07:41:12 -0700 [thread overview]
Message-ID: <1425739272.4675.83.camel@redhat.com> (raw)
In-Reply-To: <54FACF5A.9080504@hp.com>
On Sat, 2015-03-07 at 05:13 -0500, Steven DuChene wrote:
> Alex:
> What would be the result of running an earlier kernel that did not have
> your RMRR patch on a system that was known to have these problems with
> RMRR issues? Would there possibly be some instability when trying to do
> PCI passthrough of these same NVidia devices?
>
> We have a debian install on one of these same systems and it is running
> a 3.14.23-2 kernel and we are seeing some issues with PCI passthrough.
The potential problems depend on whether the RMRR memory region is
actually used, whether the device or the platform depend on that ongoing
access, and the address space consumed by the RMRR. In the case of a
VM, the fear is that the RMRR is used as a data reporting location by
the device, that use continues after the device is assigned to the VM,
and that the RMRR memory region overlaps guest RAM. If all of those
conditions hold true, then we have a memory integrity issue in the VM.
On the platform side, whatever data the platform was depending on the
device to report is now disconnected from specified data reporting range
and lost.
In the case of an Nvidia device, I'd speculate that the more likely
cause of issues for that kernel would be that the VT-d hardware may not
support snoop-control and the kvm-vfio interface that manages whether
KVM emulates cache coherence instructions wasn't added until kernel
v3.15. Thanks,
Alex
prev parent reply other threads:[~2015-03-07 14:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-06 5:20 Device is ineligible for IOMMU domain attach due to platform RMRR requirement Steven DuChene
2015-03-06 6:10 ` Alex Williamson
2015-03-07 3:10 ` Steven DuChene
2015-03-07 4:43 ` Alex Williamson
2015-03-07 10:13 ` Steven DuChene
2015-03-07 14:41 ` Alex Williamson [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=1425739272.4675.83.camel@redhat.com \
--to=alex.williamson@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=steven.duchene@hp.com \
/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