From: Nigel Cunningham <ncunningham@cyclades.com>
To: Andrew Morton <akpm@osdl.org>
Cc: Li Shaohua <shaohua.li@intel.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
ACPI List <acpi-devel@lists.sourceforge.net>,
zwane@linuxpower.ca, len.brown@intel.com, pavel@suse.cz
Subject: Re: [ACPI] Re: [RFC 0/6] S3 SMP support with physcial CPU hotplug
Date: Mon, 04 Apr 2005 19:54:04 +1000 [thread overview]
Message-ID: <1112608444.3757.17.camel@desktop.cunningham.myip.net.au> (raw)
In-Reply-To: <20050403193750.40cdabb2.akpm@osdl.org>
Hi.
On Mon, 2005-04-04 at 12:37, Andrew Morton wrote:
> Li Shaohua <shaohua.li@intel.com> wrote:
> >
> > The patches are against 2.6.11-rc1 with Zwane's CPU hotplug patch in -mm
> > tree.
>
> Should I merge that thing into mainline? It seems that a few people are
> needing it.
Perhaps we should address the MTRR issue first.
I've had code in Suspend2 for quite a while (6 months+) that removes the
sysdev support for MTRRs and saves and restores them with CPU context,
thereby avoiding the smp_call-while-interrupts-disabled issue. Perhaps
it would be helpful here?
Nigel
--
Nigel Cunningham
Software Engineer, Canberra, Australia
http://www.cyclades.com
Bus: +61 (2) 6291 9554; Hme: +61 (2) 6292 8028; Mob: +61 (417) 100 574
Maintainer of Suspend2 Kernel Patches http://suspend2.net
next prev parent reply other threads:[~2005-04-04 9:52 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-04 2:05 Li Shaohua
2005-04-04 2:37 ` Andrew Morton
2005-04-04 2:42 ` Li Shaohua
2005-04-04 2:48 ` Andrew Morton
2005-04-04 2:49 ` Li Shaohua
2005-04-04 8:01 ` [ACPI] " Nigel Cunningham
2005-04-04 8:44 ` Li Shaohua
2005-04-04 9:10 ` Pavel Machek
2005-04-04 9:24 ` Li Shaohua
2005-04-04 9:32 ` Pavel Machek
2005-04-04 9:55 ` Nigel Cunningham
2005-04-04 8:44 ` Pavel Machek
2005-04-04 9:54 ` Nigel Cunningham [this message]
2005-04-04 11:31 ` [ACPI] " Pavel Machek
2005-04-04 11:46 ` Nigel Cunningham
2005-04-04 19:42 ` Zwane Mwaikambo
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=1112608444.3757.17.camel@desktop.cunningham.myip.net.au \
--to=ncunningham@cyclades.com \
--cc=acpi-devel@lists.sourceforge.net \
--cc=akpm@osdl.org \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
--cc=shaohua.li@intel.com \
--cc=zwane@linuxpower.ca \
/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
all inboxes | Powered by JetHome®