From: Toshi Kani <toshi.kani@hp.com>
To: shuahkhan@gmail.com
Cc: lenb@kernel.org, linux-acpi@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/5] ACPI: Add _OST support for ACPI hotplug
Date: Wed, 11 Apr 2012 12:50:47 -0600 [thread overview]
Message-ID: <1334170247.20190.34.camel@misato.fc.hp.com> (raw)
In-Reply-To: <1334161991.2226.18.camel@lorien2>
On Wed, 2012-04-11 at 10:33 -0600, Shuah Khan wrote:
> On Tue, 2012-04-10 at 16:21 -0600, Toshi Kani wrote:
> > This series of patches supports ACPI _OST (OSPM Status Indication)
> > method for ACPI-based CPU and memory hotplug operations. After
> > ACPI-based hotplug operation completed, OSPM calls _OST to convey
> > the completion status to ACPI firmware. If _OST is not present,
> > this change has no effect on the platform.
> >
> > The _OST definition can be found in section 6.3.5 of ACPI 5.0 spec.
> > The HPPF spec below also describes hotplug flows with _OST.
> >
> > DIG64 Hot-Plug & Partitioning Flow (HPPF) Specification R1.0
> > http://www.dig64.org/home/DIG64_HPPF_R1_0.pdf
> >
> > The change was tested by overriding DSDT with fake _OST methods.
>
> Could you please elaborate what it means by fake _OST method? I am
> assuming based on the above that this patch set was never tested on real
> hardware that has support for _OST method? Is that correct? If so why
> not wait until you have the opportunity to test it on real hardware
> before sending the patch?
Hi Shuah,
The fake _OST methods print arguments to verify successful execution of
the methods. Since the purpose of _OST is firmware-internal
communication, there is no difference in testing on real firmware from
the OS perspective. Overriding DSDT with fake ACPI methods is a
well-established and widely used testing method as well.
Pre-enablement of new features will benefit us because:
1. There is a timeline gap between support in the upstream kernel and
distribution kernels. Also, a new platform often needs to support older
stable kernels as well.
2. Pre-enablement in the OS allows platform vendors to design new
platforms that utilize the new feature.
Thanks,
-Toshi
> -- Shuah
> >
> > ---
> > Toshi Kani (4):
> > ACPI: Set hotplug _OST support bit to _OSC
> > ACPI: Add acpi_evaluate_ost() for calling _OST
> > ACPI: Add _OST support for ACPI CPU hotplug
> > ACPI: Add _OST support for ACPI memory hotplug
> >
> > drivers/acpi/acpi_memhotplug.c | 43 +++++++++++++++++++++++++++++----------
> > drivers/acpi/bus.c | 5 ++++
> > drivers/acpi/processor_driver.c | 28 ++++++++++++++++++-------
> > drivers/acpi/utils.c | 34 ++++++++++++++++++++++++++++++
> > include/acpi/acpi_bus.h | 3 ++
> > include/linux/acpi.h | 26 ++++++++++++++++++++++-
> > 6 files changed, 119 insertions(+), 20 deletions(-)
> >
> > --
> > 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:[~2012-04-11 18:52 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-10 22:21 [PATCH 0/5] ACPI: Add _OST support for ACPI hotplug Toshi Kani
2012-04-10 22:21 ` [PATCH 1/4] ACPI: Set hotplug _OST support bit to _OSC Toshi Kani
2012-04-26 15:16 ` Bjorn Helgaas
2012-04-26 17:10 ` Toshi Kani
2012-04-27 22:05 ` Toshi Kani
2012-05-02 21:20 ` Toshi Kani
2012-04-10 22:21 ` [PATCH 2/4] ACPI: Add acpi_evaluate_ost() for calling _OST Toshi Kani
2012-04-10 22:21 ` [PATCH 3/4] ACPI: Add _OST support for ACPI CPU hotplug Toshi Kani
2012-04-26 15:22 ` Bjorn Helgaas
2012-04-26 17:20 ` Toshi Kani
2012-04-10 22:21 ` [PATCH 4/4] ACPI: Add _OST support for ACPI memory hotplug Toshi Kani
2012-04-11 16:33 ` [PATCH 0/5] ACPI: Add _OST support for ACPI hotplug Shuah Khan
2012-04-11 18:50 ` Toshi Kani [this message]
2012-04-12 14:19 ` Shuah Khan
2012-04-13 14:24 ` Jiang Liu
2012-04-13 15:23 ` Shuah Khan
2012-04-13 16:05 ` Toshi Kani
2012-04-13 18:34 ` Shuah Khan
2012-04-16 18:24 ` Toshi Kani
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=1334170247.20190.34.camel@misato.fc.hp.com \
--to=toshi.kani@hp.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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