On Sat, 2007-12-01 at 10:03 +0900, Paul Mundt wrote: > There are of course things that make this more attractive on x86, > especially with regards to the global bit and preservation across a > TLB > flush, there's a note in arch/sh/mm/init.c above __set_fixmap() about > that. fixmap doesn't really have any special behaviour that makes an > architecture implementation problematic at least.
On ppc, we are mostly looking into memory mapped config space, which for some new PCIe bridges is huge (about 512M per port on the 440SPe). Those processors have 36 bits physical addresses and 32 bits virtual. So I suppose we can just move our current kmap_atomic implementation out of highmem, call it fixmap, and add a slot for use by PCI config space access (those are fully spinlocked, so the per-cpu aspect is just what we need, just like kmap_atomic). Ben. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/