Re: 2.6.32-rc4: Reported regressions from 2.6.31

[Linus Torvalds]

On Mon, 12 Oct 2009, David Woodhouse wrote:
> 
> > The other solution would be to just _enable_ (and do all the setup) of the 
> > IOMMU early. And then just leave a legacy mapping for the IOMMU, and then 
> > _after_all_devices_are_set_up_ can you then remove the legacy mapping.
> 
> That involves allocating a _shitload_ of page tables for a 1:1 mapping
> of all of physical memory.

I don't think that's true.

Nobody cares about "all physical memory". For one thing, we know that 
anything that we consider to be normal memory (ie it's listed in the e820 
tables as RAM) can't be all that interesting, since the BIOS definitely 
released that to us.

That said, as long as the IOMMU is clearly enabled after the quirks have 
run, for this particular case we don't much care.

But I could also imagine something similar happening for some BIOS-enabled 
ethernet device being set up to listen to packets into some BIOS data 
areas (left-overs from whatever bootp thing or other), which doesn't have 
a quirk, and which ends up doing DMA until we actually load the driver.

Of course, we'd hope that the DMA just fails and nothing bad really 
happens (hopefully the driver re-init will clear up any hung device). But 
I can also imagine the hardware simply being really really unhappy, and 
not recovering.

So in many ways it would be safest to leave memory that we don't know 
about and we don't own as DMA'able in the IOMMU.

And no, I don't think it would be a shitload of pages. Quite the reverse. 
It's probably not very many at all.

		Linus
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/