From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Pavel Machek <pavel@ucw.cz>
Cc: Andrew Morton <akpm@osdl.org>,
kernel list <linux-kernel@vger.kernel.org>
Subject: Re: cpu_init is called during resume
Date: Thu, 31 Aug 2006 16:52:42 -0700 [thread overview]
Message-ID: <44F7764A.7060707@goop.org> (raw)
In-Reply-To: <20060831223121.GG12847@elf.ucw.cz>
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.
J
next prev parent reply other threads:[~2006-08-31 23:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-31 13:55 cpu_init is called during resume Pavel Machek
2006-08-31 16:11 ` Jeremy Fitzhardinge
2006-08-31 22:31 ` Pavel Machek
2006-08-31 23:52 ` Jeremy Fitzhardinge [this message]
2006-09-02 11:21 ` Pavel Machek
2006-09-03 0:00 ` Jeremy Fitzhardinge
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=44F7764A.7060707@goop.org \
--to=jeremy@goop.org \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox