On Thu 2006-08-31 16:52:42, Jeremy Fitzhardinge wrote:
> Pavel Machek wrote:
> >We are doing virtual cpu hotplug/unplug... actually suspend to RAM
> >*and* disk. Just try it :-).
> >
>
> Yes, I know, but if you're replugging a CPU it should already have a GDT
> allocated, so the kmalloc() won't be called in the resume case. So if
> there's a problem, it can only be on the resume-from-disk path, on the
> assumption that that secondary CPU hasn't already been brought up.
I think gdt is destroyed on cpu unplug, no? I guess I'll have to redo
my testing...
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
--
VGER BF report: H 0.410571
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
