On Wed, Feb 14, 2007 at 11:51:31AM +0100, Gerd Hoffmann wrote:
> Vivek Goyal wrote:
> > So what happens if somebody builds a SMP kernel and runs on a UP machine.
> > Later it hotplus one CPU. Then kernel will switch to SMP mode. Looking
> > at the code it looks like it will also try to patch init
Vivek Goyal wrote:
> So what happens if somebody builds a SMP kernel and runs on a UP machine.
> Later it hotplus one CPU. Then kernel will switch to SMP mode. Looking
> at the code it looks like it will also try to patch init text which is
> no more there and will corrupt something else?
There
Hi,
I just built a 2.6.20 kernel with CONFIG_RELOCATABLE=y. While going
through relocation entries for .smp_locks section, I see some relocation
entries present w.r.t to init section also. Below I am pasting just
few of them.
Relocation section '.rel.smp_locks' at offset 0x6079c8 contains 4662
Hi,
I just built a 2.6.20 kernel with CONFIG_RELOCATABLE=y. While going
through relocation entries for .smp_locks section, I see some relocation
entries present w.r.t to init section also. Below I am pasting just
few of them.
Relocation section '.rel.smp_locks' at offset 0x6079c8 contains 4662
Vivek Goyal wrote:
So what happens if somebody builds a SMP kernel and runs on a UP machine.
Later it hotplus one CPU. Then kernel will switch to SMP mode. Looking
at the code it looks like it will also try to patch init text which is
no more there and will corrupt something else?
There are
On Wed, Feb 14, 2007 at 11:51:31AM +0100, Gerd Hoffmann wrote:
Vivek Goyal wrote:
So what happens if somebody builds a SMP kernel and runs on a UP machine.
Later it hotplus one CPU. Then kernel will switch to SMP mode. Looking
at the code it looks like it will also try to patch init text
6 matches
Mail list logo