Jeffrey Gardner <[EMAIL PROTECTED]> posted [EMAIL PROTECTED],
excerpted below, on  Fri, 04 May 2007 12:36:58 -0500:

> Processor type and features
> [ ] IOMMU support

Note that for AMD64, if you have >3.5 gig memory, you'll WANT IOMMU 
support, which uses the APGART hardware on AMD.  On Intel, they don't 
have a hardware IOMMU but the kernel emulates it, using the same basic 
options, so I believe you'll want it there as well.

Only four gig of memory is addressable from legacy 32-bit PCI devices, 
and there's a memory hole at the top of 4-gig memory (so beyond 3.5 gig) 
in ordered to allow device i/o memory access.  With the correct BIOS 
settings, the machine will remap the unavailable memory behind that 
memory hole above 4 gig, but it and any memory you had beyond 4 gig 
already will not be directly accessible to DMA and the like from those 
legacy 32-bit PCI devices.  IOMMU = input/output memory management unit.  
The hardware device maps high memory onto accessible addresses in the 
memory hole for the devices that need it, and of course the software 
emulation necessary for Intel machines does the same thing.  

Without that IOMMU, access to that > 4 gig area (because of the memory 
hole, to memory above ~3.5 gig) will be limited, and much slower for some 
devices if they work at all.  Here, I simply cannot boot without IOMMU 
support (unless I disable part of my memory), as the kernel panics when 
it tries to read my hard drives.  Apparently, either the SATA chipset 
they use or the kernel drivers supporting them are legacy 32-bit, and 
without the IOMMU, they simply cannot see the memory they are supposed to 
be DMAing stuff into.

Of course, if you are still on legacy 32-bit x86 or have < 3.5 gig of 
memory (or are on a different arch entirely), the rules are somewhat 
different.  I'm not sure how the IOMMU may be used there, or how much 
attempting to do without it might slow things down.

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman

-- 
[EMAIL PROTECTED] mailing list

Reply via email to