Hi. On Wednesday 07 June 2006 09:55, Don Zickus wrote: > > > So my question is/was what is the proper way to handle processor level > > > subsystems during the suspend/resume path on an SMP system. I really > > > don't understand the hotplug path nor the suspend/resume path very > > > well. > > > > Make it work properly for CPU hotplug for individual CPU and then in > > suspend you take care of "global" state and the last CPU. > > So the assumption is treat all the cpus the same either all on or all off, > no mixed mode (some cpus on, some cpus off). I guess I was trying to hard > to work on the per-cpu level. This sounds wrong to me. Shouldn't the the effect of hotunplugging a cpu be to put the driver in a state equivalent to if that cpu simply didn't exist? Unplugging shouldn't assume we're going to subsequently have either a driver suspend, or a replug. Regards, Nigel -- Nigel, Michelle and Alisdair Cunningham 5 Mitchell Street Cobden 3266 Victoria, Australia
Attachment:
pgpFL5PeyyEsH.pgp
Description: PGP signature
- Follow-Ups:
- References:
- [2.6.17-rc5-mm2] crash when doing second suspend: BUG in arch/i386/kernel/nmi.c:174
- From: Jeremy Fitzhardinge <[email protected]>
- Re: [2.6.17-rc5-mm2] crash when doing second suspend: BUG in arch/i386/kernel/nmi.c:174
- From: Andi Kleen <[email protected]>
- Re: [2.6.17-rc5-mm2] crash when doing second suspend: BUG in arch/i386/kernel/nmi.c:174
- From: Don Zickus <[email protected]>
- [2.6.17-rc5-mm2] crash when doing second suspend: BUG in arch/i386/kernel/nmi.c:174
- Prev by Date: Re: [Patch] sched: mc/smt power savings sched policy
- Next by Date: Re: [2.6.17-rc5-mm2] crash when doing second suspend: BUG in arch/i386/kernel/nmi.c:174
- Previous by thread: Re: [2.6.17-rc5-mm2] crash when doing second suspend: BUG in arch/i386/kernel/nmi.c:174
- Next by thread: Re: [2.6.17-rc5-mm2] crash when doing second suspend: BUG in arch/i386/kernel/nmi.c:174
- Index(es):
 |