From: Rob Landley <rob@landley.net>
Cc: 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,
Hanjun Guo <hanjun.guo@linaro.org>,
trivial@kernel.org
Subject: Re: [PATCH] Documentation / cpu hotplug: remove outdated description for MADT entries
Date: Thu, 20 Jun 2013 23:30:19 -0500 [thread overview]
Message-ID: <1371789019.2776.139@driftwood> (raw)
In-Reply-To: <1371718482-452-1-git-send-email-hanjun.guo@linaro.org> (from hanjun.guo@linaro.org on Thu Jun 20 03:54:42 2013)
On 06/20/2013 03:54:42 AM, Hanjun Guo wrote:
> More than 256 entries in ACPI MADT is supported from ACPI 3.0
> Specification,
> So the outdated description for MADT entries should be removed.
>
> Signed-off-by: Hanjun Guo <hanjun.guo@linaro.org>
> ---
> Documentation/cpu-hotplug.txt | 3 ---
> 1 file changed, 3 deletions(-)
Acked-by: Rob Landley <rob@landley.net>
> diff --git a/Documentation/cpu-hotplug.txt
> b/Documentation/cpu-hotplug.txt
> index 9f40135..2e36e40 100644
> --- a/Documentation/cpu-hotplug.txt
> +++ b/Documentation/cpu-hotplug.txt
> @@ -370,9 +370,6 @@ 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.
> -
> User Space Notification
>
> Hotplug support for devices is common in Linux today. Its being used
> today to
> --
> 1.7.9.5
>
>
WARNING: multiple messages have this Message-ID (diff)
From: Rob Landley <rob@landley.net>
To: Hanjun Guo <hanjun.guo@linaro.org>
Cc: 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,
Hanjun Guo <hanjun.guo@linaro.org>,
trivial@kernel.org
Subject: Re: [PATCH] Documentation / cpu hotplug: remove outdated description for MADT entries
Date: Thu, 20 Jun 2013 23:30:19 -0500 [thread overview]
Message-ID: <1371789019.2776.139@driftwood> (raw)
In-Reply-To: <1371718482-452-1-git-send-email-hanjun.guo@linaro.org> (from hanjun.guo@linaro.org on Thu Jun 20 03:54:42 2013)
On 06/20/2013 03:54:42 AM, Hanjun Guo wrote:
> More than 256 entries in ACPI MADT is supported from ACPI 3.0
> Specification,
> So the outdated description for MADT entries should be removed.
>
> Signed-off-by: Hanjun Guo <hanjun.guo@linaro.org>
> ---
> Documentation/cpu-hotplug.txt | 3 ---
> 1 file changed, 3 deletions(-)
Acked-by: Rob Landley <rob@landley.net>
> diff --git a/Documentation/cpu-hotplug.txt
> b/Documentation/cpu-hotplug.txt
> index 9f40135..2e36e40 100644
> --- a/Documentation/cpu-hotplug.txt
> +++ b/Documentation/cpu-hotplug.txt
> @@ -370,9 +370,6 @@ 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.
> -
> User Space Notification
>
> Hotplug support for devices is common in Linux today. Its being used
> today to
> --
> 1.7.9.5
>
>
next prev parent reply other threads:[~2013-06-21 4:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-20 8:54 [PATCH] Documentation / cpu hotplug: remove outdated description for MADT entries Hanjun Guo
2013-06-20 19:52 ` Rafael J. Wysocki
2013-06-21 2:16 ` Hanjun Guo
2013-06-21 4:30 ` Rob Landley [this message]
2013-06-21 4:30 ` Rob Landley
2013-06-26 9:21 ` Jiri Kosina
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=1371789019.2776.139@driftwood \
--to=rob@landley.net \
--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=rusty@rustcorp.com.au \
--cc=trivial@kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.