mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: liguang <lig.fnst@cn.fujitsu.com>
Cc: "Len Brown" <lenb@kernel.org>,
	"Matthew Garrett" <matthew.garrett@nebula.com>,
	linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org,
	platform-driver-x86@vger.kernel.org,
	"Andreas Färber" <afaerber@suse.de>,
	"Igor Mammedov" <imammedo@redhat.com>
Subject: Re: [PATCH RFC v2 0/3] add cpu physically hotplug driver
Date: Thu, 06 Jun 2013 13:00:31 +0200	[thread overview]
Message-ID: <5449620.11SBDUltzF@vostro.rjw.lan> (raw)
In-Reply-To: <1370482835-764-1-git-send-email-lig.fnst@cn.fujitsu.com>

On Thursday, June 06, 2013 09:40:32 AM liguang wrote:
> This patch-set try to support physically hot-plug/unplug
> a cpu automatically, that is:
> if you offline a cpu, it will automatically actually remove
> a cpu, and if you hot-plug a cpu, then it will online this
> cpu automatically.

No and no.

Why do you need this?

Rafael


> so, offline is just like eject, but eject attribute seems not
> available since recent kernel(can't figure out when), with
> this driver, if allowed, it will trigger a eject cpu process.
> and for automatically online, it was said there are objections,
> don't know the reason, so, send this patch-set boldly.
> 
> of course, this approach is for QEMU 's hotplug cpu emulation 
> only, but not limited, if someone like to explore ec space to
> implment cpu hot-plug/unplug for real platform please
> feel free to continue.
> 
> Li Guang (3)
> 	 drivers/platform/x86: add cpu physically hotplug driver
> 	 ec: add ec space notifier
> 	 cpu_physic_hotplug: register handler for ec space notifier
> 
> drivers/acpi/ec.c                         | 32 ++++++++++++++++++++++++++++++++
> drivers/platform/x86/Kconfig              |  8 ++++
> drivers/platform/x86/Makefile             |  1 +
> drivers/platform/x86/cpu_physic_hotplug.c | 90 +++++++++++++++++++++++++++++
> include/linux/acpi.h                      |  2 ++
> 5 files changed, 130 insertions(+), 3 deletions(-)
>  create mode 100644 drivers/platform/x86/cpu_physic_hotplug.c
-- 
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.

  parent reply	other threads:[~2013-06-06 10:51 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-06  1:40 liguang
2013-06-06  1:40 ` [PATCH RFC v2 1/3] drivers/platform/x86: " liguang
2013-06-06  2:24   ` Gu Zheng
2013-06-06  3:03     ` li guang
2013-06-06  9:34   ` Borislav Petkov
2013-06-06  1:40 ` [PATCH RFC v2 2/3] ec: add ec space notifier liguang
2013-06-06 10:59   ` Rafael J. Wysocki
2013-06-10  0:46     ` li guang
2013-06-10 11:43       ` Rafael J. Wysocki
2013-06-06  1:40 ` [PATCH RFC v2 3/3] cpu_physic_hotplug: register handler for " liguang
2013-06-06 11:00 ` Rafael J. Wysocki [this message]
2013-06-10  0:36   ` [PATCH RFC v2 0/3] add cpu physically hotplug driver li guang
2013-06-10  3:51     ` Yasuaki Ishimatsu
2013-06-10  4:04       ` li guang
2013-06-10 11:47         ` Rafael J. Wysocki

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=5449620.11SBDUltzF@vostro.rjw.lan \
    --to=rjw@sisk.pl \
    --cc=afaerber@suse.de \
    --cc=imammedo@redhat.com \
    --cc=lenb@kernel.org \
    --cc=lig.fnst@cn.fujitsu.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matthew.garrett@nebula.com \
    --cc=platform-driver-x86@vger.kernel.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 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®