public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Hanjun Guo <hanjun.guo@linaro.org>
To: Dou Liyang <douly.fnst@cn.fujitsu.com>,
	"Rafael J. Wysocki" <rjw@rjwysocki.net>,
	rafael@kernel.org, "Zheng, Lv" <lv.zheng@intel.com>
Cc: linux-acpi@vger.kernel.org
Subject: Re: Two questions about the MADT in ACPI table
Date: Wed, 15 Feb 2017 10:38:11 +0800	[thread overview]
Message-ID: <46ea45ad-e2de-27f6-e71a-6908703a48cf@linaro.org> (raw)
In-Reply-To: <5f035cfc-3de1-235d-b387-cd7add94a5e1@cn.fujitsu.com>

On 2017/2/13 21:31, Dou Liyang wrote:
> Hi, Rafael, Lv
>
> May I ask for your help.
>
> Recently, I am very confused about the generation of the MADT
> in ACPI table.
>
> 1: Why we put all the Apic Ids which flag==1 in front of the
> one which flag==0 in MADT?
>
> Just like that:
>
> -----orginal-----------------MADT-------
> Apic Id    Enable Flag    Apic Id    Enable Flag
> 0x00    1        0x00    1
> 0x02    1        0x02    1
> 0x04    0        0x10    1
> 0x06    0        0x12    1
> 0x10    1        0x04    0
> 0x12    1        0x06    0
> 0x14    0        0x14    0
> 0x16    0        0x16    0
>
> If the flag is the same, It will not change the order.
>
> -----orginal-----------------MADT---------
> Apic Id    Enable Flag    Apic Id    Enable Flag
> 0x00    0        0x00    0
> 0x02    0        0x02    0
> 0x04    0        0x04    0
> 0x06    0        0x06    0
> 0x10    0        0x10    0
> 0x12    0        0x12    0
> 0x14    0        0x14    0
> 0x16    0        0x16    0

Sorry, a little bit confused, local APIC entries are listed in
MADT by firmware, and MADT is a static table which means the OS
will not update the orders.

>
>
> 2: If the order rule can be changed ?
> If it can be done, What should I do?

What's the issue you are facing? any problem here?

Thanks
Hanjun

  parent reply	other threads:[~2017-02-15  2:38 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-13 13:31 Two questions about the MADT in ACPI table Dou Liyang
2017-02-13 22:18 ` Rafael J. Wysocki
2017-02-15  2:53   ` Dou Liyang
2017-02-15  3:18     ` Dou Liyang
2017-02-15  6:36       ` Hanjun Guo
2017-02-15  8:01         ` Dou Liyang
2017-02-15  3:54     ` Dou Liyang
2017-02-15  2:38 ` Hanjun Guo [this message]
2017-02-15  3:46   ` Dou Liyang
2017-02-15  6:42     ` Hanjun Guo
2017-02-15  7:07       ` Dou Liyang

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=46ea45ad-e2de-27f6-e71a-6908703a48cf@linaro.org \
    --to=hanjun.guo@linaro.org \
    --cc=douly.fnst@cn.fujitsu.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=lv.zheng@intel.com \
    --cc=rafael@kernel.org \
    --cc=rjw@rjwysocki.net \
    /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