From: Khalid Aziz <khalid.aziz@hp.com>
To: Toshi Kani <toshi.kani@hp.com>
Cc: Jiang Liu <liuj97@gmail.com>,
lenb@kernel.org, linux-acpi@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ACPI: Add ACPI CPU hot-remove support
Date: Tue, 10 Jul 2012 16:56:18 -0600 [thread overview]
Message-ID: <1341960978.1065.12.camel@lyra> (raw)
In-Reply-To: <1341608402.16730.730.camel@misato.fc.hp.com>
On Fri, 2012-07-06 at 15:00 -0600, Toshi Kani wrote:
> Yes, offlining and eject are similar operations to a core as it alone
> cannot be removed physically. Ejecting a core is a logical eject
> operation, which updates the status (_STA) of the object in ACPI after
> offlining. The difference from the offlining is that the ejected core
> is no longer assigned to the partition. Here is one example. Say, a
> core is assigned to a guest partition as a dedicated resource (ex. 100%
> of its CPU time is bound to the partition). Offlining this core saves
> the power-consumption, but this core is still bound to the partition.
> Ejecting the core removes it from the partition (logically), and allows
> it to be assigned to other partition as a dedicated resource with
> hot-add.
>
Ejecting a core is reasonable when eject happens from a guest. I still
wonder what firmware would do if kernel calls eject method on a core
when running on the native host platform. If firmware behavior is not
well defined in this case, there might be some risk associated with
calling eject method on core.
Makes sense?
--
Khalid Aziz <khalid.aziz@hp.com>
next prev parent reply other threads:[~2012-07-10 22:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-29 14:51 [PATCH] ACPI: Add ACPI CPU hot-remove support Toshi Kani
2012-07-06 3:02 ` Yasuaki Ishimatsu
2012-07-06 14:17 ` Toshi Kani
2012-07-06 16:27 ` Jiang Liu
2012-07-06 19:13 ` Toshi Kani
2012-07-06 20:09 ` Khalid Aziz
2012-07-06 21:00 ` Toshi Kani
2012-07-10 22:56 ` Khalid Aziz [this message]
2012-07-10 23:30 ` Toshi Kani
[not found] ` <CAOEr4mpL952Z2iPuhfad+jhxUpOdHPRenEVmTUkU9LC8kKR29w@mail.gmail.com>
2012-08-13 15:21 ` Toshi Kani
2012-07-16 4:53 ` Pandarathil, Vijaymohan R
2012-07-16 14:48 ` Toshi Kani
[not found] <16070.2632544146$1340981518@news.gmane.org>
2012-07-10 11:29 ` IgorMammedov
2012-07-10 17:36 ` Toshi Kani
-- strict thread matches above, loose matches on Subject: below --
2012-06-29 14:47 y
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=1341960978.1065.12.camel@lyra \
--to=khalid.aziz@hp.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liuj97@gmail.com \
--cc=toshi.kani@hp.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