search for: bdfs

...nmatched devices in that PCI domain. So... if you want some devices to be seen as *not* behind an IOMMU then they need to be in a PCI domain which *doesn't* have a catch-all IOMMU unit. So either you put them in a separate PCI domain all by themselves, or you explicitly list all (possible) PCI BDFs under the IOMMU unit and don't use the catch-all facility. Having said that... don't. Just put the damn thing behind an IOMMU. The guest OS doesn't *have* to use it; it either eschew the IOMMU completely or it can choose to use pass-through mode for specific devices. -- David Woodho...

...ing properly". I''ve spent a lot of time on this, maybe the experts can help here... :) Thanks in advance. Relevant logs are below. (apologize if duplicates are received, I sent earlier but I think the message size was too large.) Dave *Script to unbind devices on host: * #!/bin/sh BDFS="0000:03:00.0 0000:03:00.1 0000:00:1d.0 0000:00:1d.1 0000:00:1d.2 0000:00:1d.7 0000:04:00.0" modprobe xen-pciback for BDF in $BDFS do [ ! -e /sys/bus/pci/devices/$BDF/driver/unbind ] || \ echo -n $BDF > /sys/bus/pci/devices/$BDF/driver/unbind echo -n $BDF > /sys/bus/pci/drive...

On Sep 17, 2014 7:13 AM, "Michael S. Tsirkin" <mst at redhat.com> wrote: > > On Wed, Sep 17, 2014 at 08:02:31AM -0400, Benjamin Herrenschmidt wrote: > > On Tue, 2014-09-16 at 22:22 -0700, Andy Lutomirski wrote: > > > On non-PPC systems, virtio_pci should use the DMA API. This fixes > > > virtio_pci on Xen. On PPC, using the DMA API would break

On Sep 17, 2014 7:13 AM, "Michael S. Tsirkin" <mst at redhat.com> wrote: > > On Wed, Sep 17, 2014 at 08:02:31AM -0400, Benjamin Herrenschmidt wrote: > > On Tue, 2014-09-16 at 22:22 -0700, Andy Lutomirski wrote: > > > On non-PPC systems, virtio_pci should use the DMA API. This fixes > > > virtio_pci on Xen. On PPC, using the DMA API would break

This is the continuation of my proposal for virtio-iommu, the para- virtualized IOMMU. Here is a summary of the changes since last time [1]: * The virtio-iommu document now resembles an actual specification. It is split into a formal description of the virtio device, and implementation notes. Please find sources and binaries at [2]. * Added a probe request to describe to the guest different

This is the continuation of my proposal for virtio-iommu, the para- virtualized IOMMU. Here is a summary of the changes since last time [1]: * The virtio-iommu document now resembles an actual specification. It is split into a formal description of the virtio device, and implementation notes. Please find sources and binaries at [2]. * Added a probe request to describe to the guest different