mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Hanjun Guo <hanjun.guo@linaro.org>
Cc: linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ACPI / processor: Make it possible to get local x2apic id via _MAT
Date: Fri, 01 Aug 2014 00:33:58 +0200	[thread overview]
Message-ID: <2739917.F5vOHu97Pp@vostro.rjw.lan> (raw)
In-Reply-To: <1406604470-4800-1-git-send-email-hanjun.guo@linaro.org>

On Tuesday, July 29, 2014 11:27:50 AM Hanjun Guo wrote:
> Logical processors with APIC ID values of 255 and greater are
> required to have a Processor Device object and must convey the
> processor's APIC information to OSPM using the Processor Local
> X2APIC structure, but not until ACPI 5.1, X2APIC structure was
> not supported in _MAT method.
> 
> _MAT is needed for CPU hotplug and system with more than 255
> CPUs will definitely need X2APIC structure, so add its support
> in map_mat_entry() to make it possible to get local x2apic id
> via _MAT based on ACPI 5.1.
> 
> Signed-off-by: Hanjun Guo <hanjun.guo@linaro.org>

Applied, thanks!

> ---
>  drivers/acpi/processor_core.c |    2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/drivers/acpi/processor_core.c b/drivers/acpi/processor_core.c
> index 00f48d1..e32321c 100644
> --- a/drivers/acpi/processor_core.c
> +++ b/drivers/acpi/processor_core.c
> @@ -129,6 +129,8 @@ static int map_mat_entry(acpi_handle handle, int type, u32 acpi_id)
>  		map_lapic_id(header, acpi_id, &apic_id);
>  	} else if (header->type == ACPI_MADT_TYPE_LOCAL_SAPIC) {
>  		map_lsapic_id(header, type, acpi_id, &apic_id);
> +	} else if (header->type == ACPI_MADT_TYPE_LOCAL_X2APIC) {
> +		map_x2apic_id(header, type, acpi_id, &apic_id);
>  	}
>  
>  exit:
> 

-- 
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.

      reply	other threads:[~2014-07-31 22:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-29  3:27 Hanjun Guo
2014-07-31 22:33 ` 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=2739917.F5vOHu97Pp@vostro.rjw.lan \
    --to=rjw@rjwysocki.net \
    --cc=hanjun.guo@linaro.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /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®