Andi Kleen wrote:
BTW I changed my copy sorry. I redid the early PDA support to not be in assembler.
I went to the trouble of making the PDA completely set up before any C code ran. Did you undo that?
Andrew mentioned that people have various hacks which hook into mcount, and want to use current/smp_processor_id, which means that that they have to work from the first function prologue. It also simplifies things to get all that set up ASAP so there's no bootstrap dependency problem.
J - 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/
- Follow-Ups:
- Re: [PATCH 5/7] Use %gs for per-cpu sections in kernel
- From: Andi Kleen <[email protected]>
- Re: [PATCH 5/7] Use %gs for per-cpu sections in kernel
- References:
- [PATCH 0/7] Using %gs for per-cpu areas on x86
- From: Rusty Russell <[email protected]>
- [PATCH 1/7] Use per-cpu GDT tables from early in boot
- From: Rusty Russell <[email protected]>
- [PATCH 2/7]
- From: Rusty Russell <[email protected]>
- [PATCH 3/7] Update sys_vm86 to cope with changed pt_regs and %gs usage.
- From: Rusty Russell <[email protected]>
- [PATCH 4/7] Fix places where using %gs changes the usermode ABI.
- From: Rusty Russell <[email protected]>
- [PATCH 5/7] Use %gs for per-cpu sections in kernel
- From: Rusty Russell <[email protected]>
- Re: [PATCH 5/7] Use %gs for per-cpu sections in kernel
- From: Andi Kleen <[email protected]>
- [PATCH 0/7] Using %gs for per-cpu areas on x86
- Prev by Date: Re: [Kgdb-bugreport] compiling kernel with -O0 flag (For optimal debugging with kgdb and/or crash).
- Next by Date: [BUG] warning at kernel/cpu.c:38/lock_cpu_hotplug()
- Previous by thread: Re: [PATCH 5/7] Use %gs for per-cpu sections in kernel
- Next by thread: Re: [PATCH 5/7] Use %gs for per-cpu sections in kernel
- Index(es):
 |