why is trampoline.S code copied for each cpu?

• Next message: willy@thepuffingroup.com: "Re: why is trampoline.S code copied for each cpu?"
• Previous message: Khimenko Victor: "Re: [linux-audio-dev] lowish-latency patch and toolchain"
• Next in thread: willy@thepuffingroup.com: "Re: why is trampoline.S code copied for each cpu?"
• Reply: willy@thepuffingroup.com: "Re: why is trampoline.S code copied for each cpu?"
• Maybe reply: James Bottomley: "Re: why is trampoline.S code copied for each cpu?"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Hi guys,

The arch/i386/kernel/smpboot.c:do_boot_cpu() uses setup_trampoline() to
copy the trampoline.S code for each cpu. Why not point all of them to the
same copy? So I looked in trampoline.S and discovered the answer to this
question - because each instance writes some magic number a5a5a5a5 to its
code. Ok, so then the answer becomes - why does it do that?

Any ideas?

Regards,
Tigran

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/

• Next message: willy@thepuffingroup.com: "Re: why is trampoline.S code copied for each cpu?"
• Previous message: Khimenko Victor: "Re: [linux-audio-dev] lowish-latency patch and toolchain"
• Next in thread: willy@thepuffingroup.com: "Re: why is trampoline.S code copied for each cpu?"
• Reply: willy@thepuffingroup.com: "Re: why is trampoline.S code copied for each cpu?"
• Maybe reply: James Bottomley: "Re: why is trampoline.S code copied for each cpu?"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Sat Jul 15 2000 - 21:00:12 EST