Re: CPU Hotplug: Hotplug Script And SIGPWR

[Matthias Urlichs]

Hi, Tim Hockin wrote:

> We already can not handle unexpected CPU removals gracefully, correct?  So
> we expect some user-provided notification, right?
> 
Well, if the CPU is executing userland (or idling), we conceivably could.
That would kill off one userspace process (which might be able to recover
given a signal and longjmp(), but such is life. ;-)

> So force userland to handle it before we give the OK to remove a CPU.

I like the idea of an "unrunnable" queue, that way you have the option to
fix the problem afterwards -- or just ignore it, if you decide it's OK for
processes to wait a few minutes while you replace the failing CPU fan.

It's like mount(). Usually you unmount cleanly, but sometimes you use -f
and something becomes inaccesible. At least WRT CPUs, the inaccessibility
is (usually) fixable. (I wish it were so, WRT NFS mounts.)

-- 
Matthias Urlichs   |   {M:U} IT Design @ m-u-it.de   |  smurf@xxxxxxxxxxxxxx
Disclaimer: The quote was selected randomly. Really. | http://smurf.noris.de
 - -
"Whenever the civil government forbids the practice of things
 that God has commanded us to do, or tells us to do things He
 has commanded us not to do then we are on solid ground in
 disobeying the government and rebelling against it."
               [Pat Robertson]

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