From: Yasuaki Ishimatsu <isimatu.yasuaki@jp.fujitsu.com>
To: Toshi Kani <toshi.kani@hp.com>
Cc: akpm@linux-foundation.org, mingo@kernel.org, hpa@zytor.com,
tglx@linutronix.de, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, x86@kernel.org
Subject: Re: [PATCH] mm, x86: Skip NUMA_NO_NODE while parsing SLIT
Date: Thu, 5 Dec 2013 19:25:36 +0900 [thread overview]
Message-ID: <52A054A0.6060108@jp.fujitsu.com> (raw)
In-Reply-To: <1386191348-4696-1-git-send-email-toshi.kani@hp.com>
(2013/12/05 6:09), Toshi Kani wrote:
> When ACPI SLIT table has an I/O locality (i.e. a locality unique
> to an I/O device), numa_set_distance() emits the warning message
> below.
>
> NUMA: Warning: node ids are out of bound, from=-1 to=-1 distance=10
>
> acpi_numa_slit_init() calls numa_set_distance() with pxm_to_node(),
> which assumes that all localities have been parsed with SRAT previously.
> SRAT does not list I/O localities, where as SLIT lists all localities
> including I/Os. Hence, pxm_to_node() returns NUMA_NO_NODE (-1) for
> an I/O locality. I/O localities are not supported and are ignored
> today, but emitting such warning message leads unnecessary confusion.
In this case, the warning message should not be shown. But if SLIT table
is really broken, the message should be shown. Your patch seems to not care
for second case.
Thanks,
Yasuaki Ishimatsu
>
> Change acpi_numa_slit_init() to avoid calling numa_set_distance()
> with NUMA_NO_NODE.
>
> Signed-off-by: Toshi Kani <toshi.kani@hp.com>
> ---
> arch/x86/mm/srat.c | 10 ++++++++--
> 1 file changed, 8 insertions(+), 2 deletions(-)
>
> diff --git a/arch/x86/mm/srat.c b/arch/x86/mm/srat.c
> index 266ca91..29a2ced 100644
> --- a/arch/x86/mm/srat.c
> +++ b/arch/x86/mm/srat.c
> @@ -47,10 +47,16 @@ void __init acpi_numa_slit_init(struct acpi_table_slit *slit)
> {
> int i, j;
>
> - for (i = 0; i < slit->locality_count; i++)
> - for (j = 0; j < slit->locality_count; j++)
> + for (i = 0; i < slit->locality_count; i++) {
> + if (pxm_to_node(i) == NUMA_NO_NODE)
> + continue;
> + for (j = 0; j < slit->locality_count; j++) {
> + if (pxm_to_node(j) == NUMA_NO_NODE)
> + continue;
> numa_set_distance(pxm_to_node(i), pxm_to_node(j),
> slit->entry[slit->locality_count * i + j]);
> + }
> + }
> }
>
> /* Callback for Proximity Domain -> x2APIC mapping */
>
> --
> To unsubscribe, send a message with 'unsubscribe linux-mm' in
> the body to majordomo@kvack.org. For more info on Linux MM,
> see: http://www.linux-mm.org/ .
> Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
>
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2013-12-05 10:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-04 21:09 Toshi Kani
2013-12-05 10:25 ` Yasuaki Ishimatsu [this message]
2013-12-05 15:11 ` Toshi Kani
2013-12-06 7:23 ` Yasuaki Ishimatsu
2013-12-06 14:52 ` Toshi Kani
2013-12-05 23:21 ` David Rientjes
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=52A054A0.6060108@jp.fujitsu.com \
--to=isimatu.yasuaki@jp.fujitsu.com \
--cc=akpm@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@kernel.org \
--cc=tglx@linutronix.de \
--cc=toshi.kani@hp.com \
--cc=x86@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