| commit | ee46a90b599952bb1a9dc67f894710017e7cc409 | |
| author | Milton Miller <miltonm@bga.com> | |
| Wed, 11 Apr 2007 08:32:17 +0000 (11 18:32 +1000) | ||
| committer | Paul Mackerras <paulus@samba.org> | |
| Mon, 25 Jun 2007 06:55:16 +0000 (25 16:55 +1000) | ||
| tree | 48b51d3bab9a37549cf6720d4a280929c04c4a49 | treesnapshot (tar.gz zip) |
| parent | e58ca3de64927e96beb2f1594975dc4a29b79459 | commitdiff |
[POWERPC] kexec: Send slaves to new kernel earlier
With this, when kexec-ing, we copy the code and start the slaves on
their journey to the next kernel's spin loop as soon as we copy the
kexec image into place.
The kernel doesn't know exactly which slaves are spinning in
kexec_wait. This allows us to pass more than max-cpus to the
next kernel. But it also means that we might leave some behind.
Moving the code here means they have the time it takes us to
clear the hash table to wake up and move on. Moving the code
any earlier would reuqire walking the image description to
search for the code, which could span multiple pages.
Signed-off-by: Milton Miller <miltonm@bga.com>
Signed-off-by: Paul Mackerras <paulus@samba.org>
With this, when kexec-ing, we copy the code and start the slaves on
their journey to the next kernel's spin loop as soon as we copy the
kexec image into place.
The kernel doesn't know exactly which slaves are spinning in
kexec_wait. This allows us to pass more than max-cpus to the
next kernel. But it also means that we might leave some behind.
Moving the code here means they have the time it takes us to
clear the hash table to wake up and move on. Moving the code
any earlier would reuqire walking the image description to
search for the code, which could span multiple pages.
Signed-off-by: Milton Miller <miltonm@bga.com>
Signed-off-by: Paul Mackerras <paulus@samba.org>
| arch/powerpc/kernel/misc_64.S | diffblobblamehistory |