exporting __cpu_physical_id
I assume you're using cpu_physical_id() in your code? I don't mind exporting the physical id array, but Asit sent me an SMP cleanup patch which renames __cpu_physical_id to ia64_cpu_to_sapicid, so the actual name exported will be different. As long as your code uses cpu_physical_id(), you'll be fine, though.
--david
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line · Erich Focht
Erich> Hello, does anything speak against adding the line
Erich> EXPORT_SYMBOL(__cpu_physical_id);
Erich> somewhere into arch/ia64/kernel/smp.c ? I'd need to use the Erich> hardware CPU IDs from within a loadable module and I didn't Erich> find any other 'exported' function or array with the needed Erich> information...
Erich> Thanks in advance!
Erich> Best regards, Erich
OK, ia64_cpu_to_sapicid sounds good, too, if it's exported! Thanks for the warning...
Regards,
Erich
Quoted 22 lines · David Mosberger
I assume you're using
cpu_physical_id()in your code? I don't mind exporting the physical id array, but Asit sent me an SMP cleanup patch which renames__cpu_physical_idtoia64_cpu_to_sapicid, so the actual name exported will be different. As long as your code usescpu_physical_id(), you'll be fine, though.--davidQuoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line · Erich Focht
Erich> Hello, does anything speak against adding the line
Erich> EXPORT_SYMBOL(__cpu_physical_id);Erich> somewhere into
arch/ia64/kernel/smp.c? I'd need to use the Erich> hardware CPU IDs from within a loadable module and I didn't Erich> find any other 'exported' function or array with the needed Erich> information...Erich> Thanks in advance!
Erich> Best regards, Erich