From: Toshi Kani <toshi.kani@hp.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: "lenb@kernel.org" <lenb@kernel.org>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
"bhelgaas@google.com" <bhelgaas@google.com>,
"shuahkhan@gmail.com" <shuahkhan@gmail.com>,
"liuj97@gmail.com" <liuj97@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 0/7] ACPI: Add _OST support for ACPI hotplug
Date: Wed, 23 May 2012 17:37:20 -0600 [thread overview]
Message-ID: <1337816240.16730.333.camel@misato.fc.hp.com> (raw)
In-Reply-To: <1336757092.16730.250.camel@misato.fc.hp.com>
On Fri, 2012-05-11 at 17:24 +0000, Kani, Toshimitsu wrote:
> On Fri, 2012-05-11 at 10:09 -0700, Andi Kleen wrote:
> > Toshi Kani <toshi.kani@hp.com> writes:
> >
> > > This patchset supports ACPI OSPM Status Indication (_OST) method for
> > > ACPI CPU/memory/container hotplug operations and sysfs eject. After
> > > ACPI hotplug operation has completed, OSPM calls _OST to indicate the
> > > result of the operation to the platform. If _OST is not present, this
> > > patchset has no effect on the platform.
> > >
> > > This _OST support can be enabled or disabled with a new config option
> > > CONFIG_ACPI_HOTPLUG_OST. This option is disabled by default. When
> > > this option is disabled, this patchset has no effect on the platform.
> >
> > Does that control compiling in/out significant sized code?
> >
> > Controlling code behaviour by CONFIG option has been long deprecated.
> > This is always better done as a runtime option.
> >
> > Just think what should a distribution who wants to use the same binary
> > on all systems set.
>
> Good question. The OS needs to tell the platform if it supports _OST at
> boot-time, and has to stick with it. Therefore, this feature may not be
> enabled/disabled during run-time. Another reason is that this feature
> depends on ACPI_HOTPLUG_CPU, ACPI_HOTPLUG_MEMORY and ACPI_CONTAINER
> config options in order to provide consistent behavior among multiple
> hotplug operations with regarding the _OST support.
Hi Andi,
Thinking this further, I have decided to remove this new CONFIG option.
Thanks for your valuable suggestion!
-Toshi
prev parent reply other threads:[~2012-05-23 23:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-11 16:36 Toshi Kani
2012-05-11 16:36 ` [PATCH v3 1/7] ACPI: Add CONFIG_HOTPLUG_OST option Toshi Kani
2012-05-11 16:36 ` [PATCH v3 2/7] ACPI: Add an interface to evaluate _OST Toshi Kani
2012-05-11 16:36 ` [PATCH v3 3/7] ACPI: Add _OST support for sysfs eject Toshi Kani
2012-05-11 16:37 ` [PATCH v3 4/7] ACPI: Add _OST support for ACPI CPU hotplug Toshi Kani
2012-05-11 16:37 ` [PATCH v3 5/7] ACPI: Add _OST support for ACPI memory hotplug Toshi Kani
2012-05-11 16:37 ` [PATCH v3 6/7] ACPI: Add _OST support for ACPI container hotplug Toshi Kani
2012-05-11 16:37 ` [PATCH v3 7/7] ACPI: Set hotplug _OST support bit to _OSC Toshi Kani
2012-05-11 17:09 ` [PATCH v3 0/7] ACPI: Add _OST support for ACPI hotplug Andi Kleen
2012-05-11 17:24 ` Toshi Kani
2012-05-23 23:37 ` Toshi Kani [this message]
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=1337816240.16730.333.camel@misato.fc.hp.com \
--to=toshi.kani@hp.com \
--cc=andi@firstfloor.org \
--cc=bhelgaas@google.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liuj97@gmail.com \
--cc=shuahkhan@gmail.com \
/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®