Re: [RFC patch] init default dma_ops to prepare intel_iommu_init failure

[David Woodhouse <dwmw2@infradead.org>]

On Thu, 2009-08-13 at 16:11 +0800, Luming Yu wrote:
> I treat this as -32 or -33 stuff, because I don't see a real system is blocking
> on the problem. I found this problem when I was trying to disable some drhd
> for debugging a real iommu issue...that one has priority.

(The real bug you were chasing is fixed, isn't it? Or worked around, at
least, since the BIOS in question is still closed source and broken.)

But by talking about disabling _some_ drhd units, you've just reminded
me that the problem is far more interesting -- we can have the IOMMU
active for _some_ devices but not others.

I was toying with the idea of putting the intel_dma_ops into
dev->archdata for each pci device at boot or hotplug time, and leaving
the global variable alone. We can calculate the dev->iommu mapping at
that point too. And we can stop being quite so broken w.r.t. PCI
hotplug...

-- 
David Woodhouse                            Open Source Technology Centre
David.Woodhouse@intel.com                              Intel Corporation