From: Pavel Machek <pavel@suse.cz>
To: Shaohua Li <shaohua.li@intel.com>
Cc: Andi Kleen <ak@suse.de>,
linux-kernel@vger.kernel.org, discuss@x86-64.org
Subject: Re: [PATCH] Add MCE resume under ia32
Date: Wed, 24 Aug 2005 15:43:31 +0200 [thread overview]
Message-ID: <20050824134331.GA2226@elf.ucw.cz> (raw)
In-Reply-To: <1124857915.5310.4.camel@linux-hp.sh.intel.com>
Hi!
> > > The boot code already initialized MCE for APs, it isn't required to
> > > initialize again. The MCE entries are cpuhotplug friendly, so for
> > > suspend/resume.
> >
> > Ok so you're saying the only change needed is to remove
> > the on_each_cpu() in the resume method? Fine I can do that.
> Yep, only BP needs it. But I'm not sure if we should do the same (add
> the sysdev class) in ia32, considering only BP needs it.
Adding sysdev class is nicer than #ifdef in the code, I'd say.
Pavel
--
if you have sharp zaurus hardware you don't need... you know my address
next prev parent reply other threads:[~2005-08-24 16:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1124762500.3013.3.camel@linux-hp.sh.intel.com.suse.lists.linux.kernel>
[not found] ` <20050823103256.GB2795@elf.ucw.cz.suse.lists.linux.kernel>
[not found] ` <1124846001.3007.7.camel@linux-hp.sh.intel.com.suse.lists.linux.kernel>
2005-08-24 1:52 ` [PATCH] Add MCE resume under ia32 Andi Kleen
2005-08-24 1:59 ` Shaohua Li
2005-08-24 3:12 ` Andi Kleen
2005-08-24 3:47 ` Shaohua Li
2005-08-24 3:59 ` Andi Kleen
2005-08-24 4:16 ` Shaohua Li
2005-08-24 4:26 ` Andi Kleen
2005-08-24 4:31 ` Shaohua Li
2005-08-24 13:43 ` Pavel Machek [this message]
2005-08-23 2:01 Shaohua Li
2005-08-23 10:32 ` Pavel Machek
2005-08-24 1:13 ` Shaohua Li
2005-08-24 8:50 ` Pavel Machek
2005-08-25 2:36 ` Shaohua Li
2005-08-25 9:08 ` Pavel Machek
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=20050824134331.GA2226@elf.ucw.cz \
--to=pavel@suse.cz \
--cc=ak@suse.de \
--cc=discuss@x86-64.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shaohua.li@intel.com \
/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