From: Leif Lindholm <leif.lindholm@linaro.org>
To: Ming Huang <ming.huang@linaro.org>
Cc: linaro-uefi@lists.linaro.org, edk2-devel@lists.01.org,
graeme.gregory@linaro.org, ard.biesheuvel@linaro.org,
michael.d.kinney@intel.com, lersek@redhat.com,
wanghuiqiang@huawei.com, huangming23@huawei.com,
zhangjinsong2@huawei.com, huangdaode@hisilicon.com,
john.garry@huawei.com, xinliang.liu@linaro.org,
zhangfeng56@huawei.com
Subject: Re: [PATCH edk2-non-osi v1 6/7] Hisilicon/D06: Fix numa node wrong issue
Date: Mon, 11 Feb 2019 14:48:54 +0000 [thread overview]
Message-ID: <20190211144854.6kw2ryyauzpcz6po@bivouac.eciton.net> (raw)
In-Reply-To: <20190201142507.30454-7-ming.huang@linaro.org>
*bangs head on desk*
That question I just asked as a reply to
("Silicon/Hisilicon/D06: Set TA as Node 0 for TA boot")
was meant to be a comment on this patch.
So - was this change one that was meant to happen together with
edk2-platforms "Silicon/Hisilicon/D06: Set TA as Node 0 for TA boot"?
What is the user visible behaviour that this change addresses?
/
Leif
On Fri, Feb 01, 2019 at 10:25:06PM +0800, Ming Huang wrote:
> Numa informations are acquired from HOB that build from memory
> initialization module. Correct numa informations to match booting
> from TA(Totem A or super cpu cluster A).
>
> Contributed-under: TianoCore Contribution Agreement 1.1
> Signed-off-by: Ming Huang <ming.huang@linaro.org>
> ---
> Platform/Hisilicon/D06/MemoryInitPei/MemoryInit.efi | Bin 297696 -> 358656 bytes
> 1 file changed, 0 insertions(+), 0 deletions(-)
>
> diff --git a/Platform/Hisilicon/D06/MemoryInitPei/MemoryInit.efi b/Platform/Hisilicon/D06/MemoryInitPei/MemoryInit.efi
> index 5fba353..fea1475 100644
> Binary files a/Platform/Hisilicon/D06/MemoryInitPei/MemoryInit.efi and b/Platform/Hisilicon/D06/MemoryInitPei/MemoryInit.efi differ
> --
> 2.9.5
>
next prev parent reply other threads:[~2019-02-11 14:48 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-01 14:25 [PATCH edk2-non-osi v1 0/7] Upload D0x binary modules Ming Huang
2019-02-01 14:25 ` [PATCH edk2-non-osi v1 1/7] Hisilicon/D06: Optimize SAS driver for reducing boot time Ming Huang
2019-02-12 15:20 ` Leif Lindholm
2019-02-12 15:34 ` Ming Huang
2019-02-01 14:25 ` [PATCH edk2-non-osi v1 2/7] Hisilicon/D0x: Rename StartupAp() function Ming Huang
2019-02-11 21:36 ` Leif Lindholm
2019-02-12 8:05 ` Ming Huang
2019-02-12 10:44 ` Leif Lindholm
2019-02-12 12:07 ` Ming Huang
2019-02-12 12:17 ` Leif Lindholm
2019-02-12 12:20 ` Ming Huang
2019-02-01 14:25 ` [PATCH edk2-non-osi v1 3/7] Hisilicon/D06: Update Mbigen and gic RAS register Ming Huang
2019-02-11 21:38 ` Leif Lindholm
2019-02-12 11:42 ` Ming Huang
2019-02-12 12:06 ` Leif Lindholm
2019-02-01 14:25 ` [PATCH edk2-non-osi v1 4/7] Hisilicon/D06: Support PCIe local RAS Ming Huang
2019-02-12 15:20 ` Leif Lindholm
2019-02-01 14:25 ` [PATCH edk2-non-osi v1 5/7] Hisilicon/D06: Use new flash layout Ming Huang
2019-02-12 15:26 ` Leif Lindholm
2019-02-13 12:09 ` Ming Huang
2019-02-01 14:25 ` [PATCH edk2-non-osi v1 6/7] Hisilicon/D06: Fix numa node wrong issue Ming Huang
2019-02-11 14:48 ` Leif Lindholm [this message]
2019-02-12 12:17 ` Ming Huang
2019-02-01 14:25 ` [PATCH edk2-non-osi v1 7/7] Hisilicon/D06: Add Setup Item "Support DPC" Ming Huang
2019-02-12 15:27 ` Leif Lindholm
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-list 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=20190211144854.6kw2ryyauzpcz6po@bivouac.eciton.net \
--to=devel@edk2.groups.io \
/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