Hi!
> > > Currently, we use the CPU hotplug to disable nonboot CPUs in the suspend
> > > code
> > > paths, but with the recent change of code ordering (ie. nonboot CPUs are
> > > disabled after freezing tasks _and_ devices) it has become quite
> > > troublesome.
> > > The reason of this is that
Hi,
On Monday, 9 April 2007 16:03, Pavel Machek wrote:
> > Currently, we use the CPU hotplug to disable nonboot CPUs in the suspend
> > code
> > paths, but with the recent change of code ordering (ie. nonboot CPUs are
> > disabled after freezing tasks _and_ devices) it has become quite
> > troub
Hi!
> Currently, we use the CPU hotplug to disable nonboot CPUs in the suspend code
> paths, but with the recent change of code ordering (ie. nonboot CPUs are
> disabled after freezing tasks _and_ devices) it has become quite troublesome.
> The reason of this is that there are some CPU hotplug not
"Rafael J. Wysocki" <[EMAIL PROTECTED]> writes:
> Hi,
>
> Currently, we use the CPU hotplug to disable nonboot CPUs in the suspend code
> paths, but with the recent change of code ordering (ie. nonboot CPUs are
> disabled after freezing tasks _and_ devices) it has become quite troublesome.
> The r
Hi,
Currently, we use the CPU hotplug to disable nonboot CPUs in the suspend code
paths, but with the recent change of code ordering (ie. nonboot CPUs are
disabled after freezing tasks _and_ devices) it has become quite troublesome.
The reason of this is that there are some CPU hotplug notifiers r
5 matches
Mail list logo