Displaying 7 results from an estimated 7 matches for "virtio_f_bus_address".
2014 Sep 02
0
[PATCH v4 0/4] virtio: Clean up scatterlists and use the DMA API
...on
x86.
Step 2: Update the virtio spec. Virtio 1.0 PCI devices should set a
new bit if they are physically addressed. If that bit is clear, then
the device is assumed to be addressed in accordance with the
platform's standard addressing model for PCI. Presumably this would
be something like VIRTIO_F_BUS_ADDRESSING = 33, and the spec would say
something like "Physical devices compatible with this specification
MUST offer VIRTIO_F_BUS_ADDRESSING. Drivers MUST implement this
feature." Alternatively, this could live in a PCI configuration
capability.
Step 3: Update virtio-pci to use the DMA API f...
2014 Sep 02
1
[PATCH v4 0/4] virtio: Clean up scatterlists and use the DMA API
On Tue, 2014-09-02 at 16:11 -0700, Andy Lutomirski wrote:
> I don't think so. I would argue that it's a straight-up bug for QEMU
> to expose a physically-addressed virtio-pci device to the guest behind
> an emulated IOMMU. QEMU may already be doing that on ppc64, but it
> isn't on x86_64 or arm (yet).
Last I looked, it does on everything, it bypasses the DMA layer in
2014 Sep 02
1
[PATCH v4 0/4] virtio: Clean up scatterlists and use the DMA API
On Tue, 2014-09-02 at 16:11 -0700, Andy Lutomirski wrote:
> I don't think so. I would argue that it's a straight-up bug for QEMU
> to expose a physically-addressed virtio-pci device to the guest behind
> an emulated IOMMU. QEMU may already be doing that on ppc64, but it
> isn't on x86_64 or arm (yet).
Last I looked, it does on everything, it bypasses the DMA layer in
2014 Sep 02
3
[PATCH v4 0/4] virtio: Clean up scatterlists and use the DMA API
On Tue, Sep 2, 2014 at 3:10 PM, Benjamin Herrenschmidt
<benh at kernel.crashing.org> wrote:
> On Tue, 2014-09-02 at 14:37 -0700, Andy Lutomirski wrote:
>
>> Let's take a step back from from the implementation. What is a driver
>> for a virtio PCI device (i.e. a PCI device with vendor 0x1af4)
>> supposed to do on ppc64?
>
> Today, it's supposed to send
2014 Sep 02
3
[PATCH v4 0/4] virtio: Clean up scatterlists and use the DMA API
On Tue, Sep 2, 2014 at 3:10 PM, Benjamin Herrenschmidt
<benh at kernel.crashing.org> wrote:
> On Tue, 2014-09-02 at 14:37 -0700, Andy Lutomirski wrote:
>
>> Let's take a step back from from the implementation. What is a driver
>> for a virtio PCI device (i.e. a PCI device with vendor 0x1af4)
>> supposed to do on ppc64?
>
> Today, it's supposed to send
2014 Sep 03
5
[PATCH v4 0/4] virtio: Clean up scatterlists and use the DMA API
...ate the virtio spec. Virtio 1.0 PCI devices should set a
> new bit if they are physically addressed. If that bit is clear, then
> the device is assumed to be addressed in accordance with the
> platform's standard addressing model for PCI. Presumably this would
> be something like VIRTIO_F_BUS_ADDRESSING = 33, and the spec would say
> something like "Physical devices compatible with this specification
> MUST offer VIRTIO_F_BUS_ADDRESSING. Drivers MUST implement this
> feature." Alternatively, this could live in a PCI configuration
> capability.
I'll let you sort that...
2014 Sep 03
5
[PATCH v4 0/4] virtio: Clean up scatterlists and use the DMA API
...ate the virtio spec. Virtio 1.0 PCI devices should set a
> new bit if they are physically addressed. If that bit is clear, then
> the device is assumed to be addressed in accordance with the
> platform's standard addressing model for PCI. Presumably this would
> be something like VIRTIO_F_BUS_ADDRESSING = 33, and the spec would say
> something like "Physical devices compatible with this specification
> MUST offer VIRTIO_F_BUS_ADDRESSING. Drivers MUST implement this
> feature." Alternatively, this could live in a PCI configuration
> capability.
I'll let you sort that...