public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: liguang <lig.fnst@cn.fujitsu.com>
Cc: "Len Brown" <lenb@kernel.org>, "Rafael J. Wysocki" <rjw@sisk.pl>,
	"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 1/3] drivers/platform/x86: add cpu physically hotplug driver
Date: Thu, 6 Jun 2013 11:34:02 +0200	[thread overview]
Message-ID: <20130606093402.GA21272@pd.tnic> (raw)
In-Reply-To: <1370482835-764-2-git-send-email-lig.fnst@cn.fujitsu.com>

On Thu, Jun 06, 2013 at 09:40:33AM +0800, liguang wrote:
> this driver will support cpu phyical add/removal automatically
> after online/offline. if cpu hotpluged, cpu will not
> online automatically, and for cpu offline, we try to
> do actually eject if allowed for cpu like
> "echo 1 > /sys/bus/acpi/devices/LNXCPU\:0X/eject"
> this "echo ..." is only present for recent kernel
> (sorry, can't figure out since when), for a little
> older kernel, there's not such approach AFAICS.
> 
> Signed-off-by: liguang <lig.fnst@cn.fujitsu.com>
> ---
>  drivers/platform/x86/Kconfig              |    8 ++++
>  drivers/platform/x86/Makefile             |    1 +
>  drivers/platform/x86/cpu_physic_hotplug.c |   60 +++++++++++++++++++++++++++++
>  3 files changed, 69 insertions(+), 0 deletions(-)
>  create mode 100644 drivers/platform/x86/cpu_physic_hotplug.c
> 
> diff --git a/drivers/platform/x86/Kconfig b/drivers/platform/x86/Kconfig
> index 8577261..39b2392 100644
> --- a/drivers/platform/x86/Kconfig
> +++ b/drivers/platform/x86/Kconfig
> @@ -789,4 +789,12 @@ config PVPANIC
>  	  a paravirtualized device provided by QEMU; it lets a virtual machine
>  	  (guest) communicate panic events to the host.
>  
> +config QEMU_CPU_PHYSIC_HOTPLUG

This is hillarious: have you actually checked the dictionary on the
meaning of "physic"?

Yep, "laxative" because the kernel is constipated and can't hold its
CPUs anymore.

LOOOL :-).

-- 
Regards/Gruss,
    Boris.

Sent from a fat crate under my desk. Formatting is fine.
--

  parent reply	other threads:[~2013-06-06  9:34 UTC|newest]

Thread overview: 15+ 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  9:34   ` Borislav Petkov [this message]
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 ` [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
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=20130606093402.GA21272@pd.tnic \
    --to=bp@alien8.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox