From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Hanjun Guo <hanjun.guo@linaro.org>
Cc: Rob Landley <rob@landley.net>,
Rusty Russell <rusty@rustcorp.com.au>,
Srivatsa Vaddagiri <vatsa@in.ibm.com>,
linux-acpi@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, patches@linaro.org,
linaro-kernel@lists.linaro.org
Subject: Re: [PATCH v2] Documentation / cpu hotplug: Rephrase the outdated description for MADT entries
Date: Mon, 24 Jun 2013 14:00:53 +0200 [thread overview]
Message-ID: <2689985.7MvxW2GhJV@vostro.rjw.lan> (raw)
In-Reply-To: <1371805758-2841-1-git-send-email-hanjun.guo@linaro.org>
On Friday, June 21, 2013 05:09:18 PM Hanjun Guo wrote:
> More than 256 entries in ACPI MADT is supported from ACPI 3.0, so the
> information should be updated.
>
> -v2: Rephrase the information instead of simply removing it according
> to Rafael's advice.
Queued up for 3.11.
Thanks,
Rafael
> Suggested-by: Rafael J. Wysocki <rjw@sisk.pl>
> Signed-off-by: Hanjun Guo <hanjun.guo@linaro.org>
> ---
> Documentation/cpu-hotplug.txt | 6 ++++--
> 1 file changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/cpu-hotplug.txt b/Documentation/cpu-hotplug.txt
> index 9f40135..67f733d 100644
> --- a/Documentation/cpu-hotplug.txt
> +++ b/Documentation/cpu-hotplug.txt
> @@ -370,8 +370,10 @@ A: There is no clear spec defined way from ACPI that can give us that
> CPUs in MADT as hotpluggable CPUS. In the case there are no disabled CPUS
> we assume 1/2 the number of CPUs currently present can be hotplugged.
>
> - Caveat: Today's ACPI MADT can only provide 256 entries since the apicid field
> - in MADT is only 8 bits.
> + Caveat: ACPI MADT can only provide 256 entries in systems with only ACPI 2.0c
> + or earlier ACPI version supported, because the apicid field in MADT is only
> + 8 bits. From ACPI 3.0, this limitation was removed since the apicid field
> + was extended to 32 bits with x2APIC introduced.
>
> User Space Notification
>
>
--
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
prev parent reply other threads:[~2013-06-24 11:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-21 9:09 Hanjun Guo
2013-06-24 12:00 ` Rafael J. Wysocki [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=2689985.7MvxW2GhJV@vostro.rjw.lan \
--to=rjw@sisk.pl \
--cc=hanjun.guo@linaro.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@linaro.org \
--cc=rob@landley.net \
--cc=rusty@rustcorp.com.au \
--cc=vatsa@in.ibm.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®