In message <20030207001006.A19306@flint.arm.linux.org.uk> you write:
> And I'll promptly provide you with the other view. I'm still trying to
> sort out the best thing to do for ARM. We have the choice of:
>
> 1. load modules in the vmalloc region and build two jump tables, one for
> the init text and one for the core text.
Yes. PPC and PPC64 have the same issues: currently this is done by
(1) putting nothing in the .init sections (on PPC64), and (2) with
stubs when jumping outside the module code.
This gives the same effect as the previous userspace loader: for PPC64
noone cares about discarding init stuff, so it's firmly on the TODO
list. ARM's priorities are obviously different.
> 2. fix vmalloc and /proc/kcore to be able to cope with a separate module
> region located below PAGE_OFFSET. Currently, neither play well with
> this option.
x86_64 has this, as does sparc64: they do their own allocation. Does
ARM require something special in this regard? I'd love to see what
you've got...
Thanks!
Rusty.
-- Anyone who quotes me in their sig is an idiot. -- Rusty Russell. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Fri Feb 07 2003 - 22:00:22 EST