Ah, I understand now what you mean. Sounds to me like the generic module loader infrastructure needs to be changed to support the IA64-usage. On IA64, we want to have per-CPU variables remapped even on UP, because it allows for more efficient and TLB-pinned addressing (which is relied upon in some low-level code for correctness, IIRC).
--david On 8/30/05, Peter Chubb <[EMAIL PROTECTED]> wrote: > >>>>> "david" == david mosberger <[EMAIL PROTECTED]> writes: > > david> The module-loader does its own UP special-casing. For > david> example, percpu_modcopy() is a dummy routine in the UP case, > david> apparently because there is not supposed to be any per-CPU > david> module data for the UP case. > > Precisely. All the other architectures redefine the DECLARE_PER_CPU() > etc., to declare plain variables (i.e., not in a special section) for > UP. So the module loader doesn't have to do anything special for UP, > because for UP a per-cpu variable is just the same as a normal > variable. > > This doesn't work for IA64, which maps per_cpu variables into a > separate segment for both UP and SMP. > > -- > Dr Peter Chubb http://www.gelato.unsw.edu.au peterc AT gelato.unsw.edu.au > The technical we do immediately, the political takes *forever* > -- Mosberger Consulting LLC, voice/fax: 510-744-9372, http://www.mosberger-consulting.com/ 35706 Runckel Lane, Fremont, CA 94536 - To unsubscribe from this list: send the line "unsubscribe linux-ia64" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
