public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Li Shaohua <shaohua.li@intel.com>
Cc: ncunningham@cyclades.com, Andrew Morton <akpm@osdl.org>,
	lkml <linux-kernel@vger.kernel.org>,
	ACPI List <acpi-devel@lists.sourceforge.net>,
	Zwane Mwaikambo <zwane@linuxpower.ca>,
	Len Brown <len.brown@intel.com>
Subject: Re: [ACPI] Re: [RFC 0/6] S3 SMP support with physcial CPU hotplug
Date: Mon, 4 Apr 2005 11:10:27 +0200	[thread overview]
Message-ID: <20050404091027.GA14765@elf.ucw.cz> (raw)
In-Reply-To: <1112604263.4194.367.camel@sli10-desk.sh.intel.com>

Hi!

> > I'm switching suspend2 to use hotplug too. Li, I'll try adding your
> > patches as well as Zwane's if you like 
> Great!
> 
> > (suspend2 can enter S3, S4 or S5
> > after writing the image). I'd love to try it on my HT desktop, and
> > hotplug will get more testing too :>
> Unfortunately, my patches break Pavel's swsusp SMP, as my patches break
> current 'cpu_up' mechanism. S4 doesn't require to boot AP CPUs from real
> mode.

Uh, I don't like that one. Is it possible to put secondary CPUs back
to the real mode so that cpu_up mechanism can handle them?

								Pavel
-- 
People were complaining that M$ turns users into beta-testers...
...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl!

  reply	other threads:[~2005-04-04  9:10 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-04  2:05 [RFC 0/6] S3 SMP support with physcial CPU hotplug Li Shaohua
     [not found] ` <1112580342.4194.329.camel-U5EdaLXB8smDugQYiPIPGdh3ngVCH38I@public.gmane.org>
2005-04-04  2:37   ` Andrew Morton
     [not found]     ` <20050403193750.40cdabb2.akpm-3NddpPZAyC0@public.gmane.org>
2005-04-04  2:42       ` Li Shaohua
     [not found]         ` <1112582553.4194.349.camel-U5EdaLXB8smDugQYiPIPGdh3ngVCH38I@public.gmane.org>
2005-04-04  2:48           ` Andrew Morton
     [not found]             ` <20050403194807.32fd761a.akpm-3NddpPZAyC0@public.gmane.org>
2005-04-04  2:49               ` Li Shaohua
     [not found]                 ` <1112582947.4194.352.camel-U5EdaLXB8smDugQYiPIPGdh3ngVCH38I@public.gmane.org>
2005-04-04  8:01                   ` Nigel Cunningham
     [not found]                     ` <1112601670.3757.6.camel-r49W/1Cwd2ff0s6lnCXPX/uOuaPYTxhvJwvTLr3MMZM@public.gmane.org>
2005-04-04  8:44                       ` Li Shaohua
2005-04-04  9:10                         ` Pavel Machek [this message]
2005-04-04  9:24                           ` [ACPI] " Li Shaohua
     [not found]                             ` <1112606651.4194.391.camel-U5EdaLXB8smDugQYiPIPGdh3ngVCH38I@public.gmane.org>
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
2005-04-04 11:31         ` [ACPI] " Pavel Machek
     [not found]           ` <20050404113129.GA7120-jyMamyUUXNJG4ohzP4jBZS1Fcj925eT/@public.gmane.org>
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=20050404091027.GA14765@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=acpi-devel@lists.sourceforge.net \
    --cc=akpm@osdl.org \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ncunningham@cyclades.com \
    --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