William Lee Irwin III wrote: >> ISTR potential ppc64 users coming out of the woodwork for something I >> didn't recognize the name of, but I may be confusing that with your >> patch. I can implement additional users (and useful ones at that) >> needing this in particular if desired.
On Wed, Mar 21, 2007 at 04:07:43PM +1100, Nick Piggin wrote: > Yes I would be interested in seeing useful additional users of this > that cannot use our regular virtual memory, before making it a general > thing. > I just don't want to see proliferation of these things, if possible. I'm tied up elsewhere so I won't get to it in a timely fashion. Maybe in a few weeks I can start up on the first two of the bunch. William Lee Irwin III wrote: >> Two fault handling methods callbacks raise an eyebrow over here at least. >> I was vaguely hoping for unification of the fault handling callbacks. On Wed, Mar 21, 2007 at 04:07:43PM +1100, Nick Piggin wrote: > I don't know if it would be so clean to do that as they are at different > levels. > Adam's fault is before the VM translation (and bypasses it), and mine is > after. Not much of a VM translation; it's just a lookup through the software mocked-up structures on everything save i386, x86_64, and some m68k where they're the same thing only with hardware walkers (ISTR ia64's being firmware a la Alpha despite the "HPW" name, though I could be wrong) reliant on them. The drivers/etc. could just as easily use helper functions to carry out the lookup, thereby accomplishing the unification. There's nothing particularly fundamental about a pte lookup. Normal arches that do software TLB refill could just as easily consult the radix trees dangled off struct address_space or any old data structure floating around the kernel with enough information to translate user virtual addresses to the physical addresses they need to fill the TLB with, and there are other kernels that literally do things like that. Basically, drop in to the ->fault() callback with no attempt at a pte lookup. The drivers using the standard pagetable format can call helper functions to do all the gruntwork surrounding that for them. Then the more sophisticated drivers can do the necessary work by hand. But others should really be consulted on this point. My notions in/around this area tend to be outside the mainstream. I can anticipate that the two ->fault() functions will look strange to people, but not what alternatives would be most idiomatic to mainstream Linux conventions. -- wli - 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/
