From: Nathan Lynch <ntl-e+AXbWqSrlAAvxtiuMwx3w@public.gmane.org>
To: Li Shaohua <shaohua.li-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: lkml <linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
ACPI-DEV
<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>,
Zwane Mwaikambo <zwane-T6AQWPvKiI1fDP7aoN8Z5Q@public.gmane.org>,
Len Brown <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
Pavel Machek <pavel-AlSwsSmVLrQ@public.gmane.org>
Subject: Re: Re: [RFC 5/6]clean cpu state after hotremove CPU
Date: Tue, 5 Apr 2005 23:28:50 -0500 [thread overview]
Message-ID: <20050406042850.GE3611@otto> (raw)
In-Reply-To: <1112666106.17861.62.camel-U5EdaLXB8smDugQYiPIPGdh3ngVCH38I@public.gmane.org>
On Tue, Apr 05, 2005 at 09:55:06AM +0800, Li Shaohua wrote:
> On Mon, 2005-04-04 at 23:33, Nathan Lynch wrote:
> > No. It should make zero difference to the scheduler whether the "play
> > dead" cpu hotplug or "physical" hotplug is being used.
> Keeping some fields like 'cpu_load' are meanless for a hotadded CPU to
> me. Just ignore them?
Reinitializing such things during the CPU_UP_PREPARE case in
migration_call should be sufficient, if it's not done already.
Nathan
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
WARNING: multiple messages have this Message-ID (diff)
From: Nathan Lynch <ntl@pobox.com>
To: Li Shaohua <shaohua.li@intel.com>
Cc: lkml <linux-kernel@vger.kernel.org>,
ACPI-DEV <acpi-devel@lists.sourceforge.net>,
Zwane Mwaikambo <zwane@linuxpower.ca>,
Len Brown <len.brown@intel.com>, Pavel Machek <pavel@suse.cz>
Subject: Re: [ACPI] Re: [RFC 5/6]clean cpu state after hotremove CPU
Date: Tue, 5 Apr 2005 23:28:50 -0500 [thread overview]
Message-ID: <20050406042850.GE3611@otto> (raw)
In-Reply-To: <1112666106.17861.62.camel@sli10-desk.sh.intel.com>
On Tue, Apr 05, 2005 at 09:55:06AM +0800, Li Shaohua wrote:
> On Mon, 2005-04-04 at 23:33, Nathan Lynch wrote:
> > No. It should make zero difference to the scheduler whether the "play
> > dead" cpu hotplug or "physical" hotplug is being used.
> Keeping some fields like 'cpu_load' are meanless for a hotadded CPU to
> me. Just ignore them?
Reinitializing such things during the CPU_UP_PREPARE case in
migration_call should be sufficient, if it's not done already.
Nathan
next prev parent reply other threads:[~2005-04-06 4:28 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-04 2:07 [RFC 5/6]clean cpu state after hotremove CPU Li Shaohua
2005-04-04 2:07 ` Li Shaohua
[not found] ` <1112580367.4194.344.camel-U5EdaLXB8smDugQYiPIPGdh3ngVCH38I@public.gmane.org>
2005-04-04 5:28 ` Nathan Lynch
2005-04-04 5:28 ` Nathan Lynch
2005-04-04 5:42 ` Li Shaohua
2005-04-04 5:42 ` [ACPI] " Li Shaohua
[not found] ` <1112593338.4194.362.camel-U5EdaLXB8smDugQYiPIPGdh3ngVCH38I@public.gmane.org>
2005-04-04 15:33 ` Nathan Lynch
2005-04-04 15:33 ` [ACPI] " Nathan Lynch
2005-04-04 22:14 ` Nigel Cunningham
2005-04-04 22:14 ` [ACPI] " Nigel Cunningham
[not found] ` <1112652864.3757.31.camel-r49W/1Cwd2ff0s6lnCXPX/uOuaPYTxhvJwvTLr3MMZM@public.gmane.org>
2005-04-04 22:46 ` Nathan Lynch
2005-04-04 22:46 ` [ACPI] " Nathan Lynch
2005-04-04 22:56 ` Nigel Cunningham
2005-04-04 22:56 ` Ashok Raj
2005-04-05 1:55 ` Li Shaohua
[not found] ` <1112666106.17861.62.camel-U5EdaLXB8smDugQYiPIPGdh3ngVCH38I@public.gmane.org>
2005-04-06 4:28 ` Nathan Lynch [this message]
2005-04-06 4:28 ` Nathan Lynch
2005-04-05 9:00 ` Li Shaohua
2005-04-05 9:00 ` [ACPI] " Li Shaohua
2005-04-04 19:11 ` Zwane Mwaikambo
2005-04-04 19:11 ` Zwane Mwaikambo
2005-04-05 1:06 ` Li Shaohua
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=20050406042850.GE3611@otto \
--to=ntl-e+axbwqsrlaavxtiumwx3w@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=pavel-AlSwsSmVLrQ@public.gmane.org \
--cc=shaohua.li-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=zwane-T6AQWPvKiI1fDP7aoN8Z5Q@public.gmane.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.