Matthew Wilcox wrote:
On Fri, Feb 13, 2009 at 04:32:47PM +, Mark McLoughlin wrote:
- Secondary Bus Reset (SBR) allows software to trigger a reset on all
devices (and functions) behind a PCI bridge.
- A PCI Power Management D-state transition (D3hot to D0) can be used
to reset a
Hi,
KVM has support for PCI device assignment using VT-d and AMD IOMMU, but
there are a number of inter-related issues that need some further
discussion:
- Unbinding devices from any existing device driver before assignment
- Resetting devices before and after assignment
- Helping users
On Fri, Feb 13, 2009 at 04:32:47PM +, Mark McLoughlin wrote:
Driver Unbinding
Before a device is assigned to a guest, we should make sure that no host
device driver is currently bound to the device.
We can do that with e.g.
$ echo -n 8086 10de
On Fri, 2009-02-13 at 08:56 -0800, Greg KH wrote:
On Fri, Feb 13, 2009 at 04:32:47PM +, Mark McLoughlin wrote:
Driver Unbinding
Before a device is assigned to a guest, we should make sure that no host
device driver is currently bound to the device.
We can do
On Fri, Feb 13, 2009 at 04:32:47PM +, Mark McLoughlin wrote:
Hi,
You raise some interesting points. Thanks for doing that rather than
going off and creating a big pile of patches and demanding they be
applied ;-)
This gets confusing, so some background constraints first:
-
* Matthew Wilcox (matt...@wil.cx) wrote:
On Fri, Feb 13, 2009 at 04:32:47PM +, Mark McLoughlin wrote:
- Conventional PCI devices (i.e. PCI/PCI-X, not PCIe) behind the same
bridge must be assigned to the same VT-d domain - i.e given device
A (:0f:1.0) and device B (and
* Chris Wright (chr...@redhat.com) wrote:
* Matthew Wilcox (matt...@wil.cx) wrote:
I might suggest a second approach which would be to have an explicit
echo to the bind file ignore the list of ids. Then you wouldn't need to
'echo -n 8086 10de' to begin with.
I tried that first, and it
