From: Yasuaki Ishimatsu <isimatu.yasuaki@jp.fujitsu.com>
To: li guang <lig.fnst@cn.fujitsu.com>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>, "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: Mon, 10 Jun 2013 12:51:45 +0900 [thread overview]
Message-ID: <51B54D51.2070505@jp.fujitsu.com> (raw)
In-Reply-To: <1370824567.21655.10.camel@liguang.fnst.cn.fujitsu.com>
2013/06/10 9:36, li guang wrote:
> Hi, Rafael
>
> 在 2013-06-06四的 13:00 +0200,Rafael J. Wysocki写道:
>> 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.
>
> Hmm... are you saying cpu online/offline designed to distinguish
> with real cpu plug/unplug?
> but, what the actual usage of online/offline?
> forgive my foolish.
>
>>
>> Why do you need this?
>>
>
> e.g. for QEMU case, if hot-plug a cpu,
> we have to online a cpu manually if there's
> no user space support like udev to do it automatically.
I could not understand why you do not use udev.
Please explain in detail.
> and also, I think maybe online/offline should be naturally
> integrated with real plug/unplug process of CPU.
I could not understand this explanation too.
Why do we need it?
Thanks,
Yasuaki Ishimatsu
>
>>
>>
>>> 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
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
next prev parent reply other threads:[~2013-06-10 3:51 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-06 1:40 [PATCH RFC v2 0/3] add cpu physically hotplug driver 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 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-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 ` [PATCH RFC v2 0/3] add cpu physically hotplug driver Rafael J. Wysocki
2013-06-10 0:36 ` li guang
2013-06-10 3:51 ` Yasuaki Ishimatsu [this message]
2013-06-10 4:04 ` li guang
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=51B54D51.2070505@jp.fujitsu.com \
--to=isimatu.yasuaki@jp.fujitsu.com \
--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 \
--cc=rjw@sisk.pl \
/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.