Displaying 5 results from an estimated 5 matches for "quirk_ioat_snb_local_iommu".
2016 Apr 28
3
[PATCH V2 RFC] fixup! virtio: convert to use DMA api
On Thu, 2016-04-28 at 17:34 +0300, Michael S. Tsirkin wrote:
> I see work-arounds for broken IOMMUs but not for
> individual devices. Could you point me to a more specific
> example?
I think the closest example is probably quirk_ioat_snb_local_iommu().
If we see this particular device, we *know* what the topology actually
looks like. We check the hardware setup, and if we're *not* being told
the truth, then we stick it in bypass mode because we know it *isn't*
actually being translated.
Actually, that's almost *identical* to what...
2016 Apr 28
3
[PATCH V2 RFC] fixup! virtio: convert to use DMA api
On Thu, 2016-04-28 at 17:34 +0300, Michael S. Tsirkin wrote:
> I see work-arounds for broken IOMMUs but not for
> individual devices. Could you point me to a more specific
> example?
I think the closest example is probably quirk_ioat_snb_local_iommu().
If we see this particular device, we *know* what the topology actually
looks like. We check the hardware setup, and if we're *not* being told
the truth, then we stick it in bypass mode because we know it *isn't*
actually being translated.
Actually, that's almost *identical* to what...
2016 Apr 28
0
[PATCH V2 RFC] fixup! virtio: convert to use DMA api
...1:54PM +0100, David Woodhouse wrote:
> On Thu, 2016-04-28 at 17:34 +0300, Michael S. Tsirkin wrote:
> > I see work-arounds for broken IOMMUs but not for
> > individual devices. Could you point me to a more specific
> > example?
>
> I think the closest example is probably quirk_ioat_snb_local_iommu().
OK, so for intel, it seems that it's enough to set
pdev->dev.archdata.iommu = DUMMY_DEVICE_DOMAIN_INFO;
for the device.
Do I have to poke at each iommu implementation to find
a way to do this, or is there some way to do it
portably?
> If we see this particular device, we *know* wha...
2016 Apr 27
2
[PATCH V2 RFC] fixup! virtio: convert to use DMA api
On Wed, 2016-04-27 at 21:17 +0300, Michael S. Tsirkin wrote:
>
> > Because it's a dirty hack in the *wrong* place.
>
> No one came up with a better one so far :(
Seriously?
Take a look at drivers/iommu/intel-iommu.c. It has quirks for all kinds
of shitty devices that have to be put in passthrough mode or otherwise
excluded.
We don't actually *need* it for the Intel
2016 Apr 27
2
[PATCH V2 RFC] fixup! virtio: convert to use DMA api
On Wed, 2016-04-27 at 21:17 +0300, Michael S. Tsirkin wrote:
>
> > Because it's a dirty hack in the *wrong* place.
>
> No one came up with a better one so far :(
Seriously?
Take a look at drivers/iommu/intel-iommu.c. It has quirks for all kinds
of shitty devices that have to be put in passthrough mode or otherwise
excluded.
We don't actually *need* it for the Intel