All of lore.kernel.org
 help / color / mirror / Atom feed
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: Fri, 6 Dec 2013 16:23:47 +0900	[thread overview]
Message-ID: <52A17B83.8060601@jp.fujitsu.com> (raw)
In-Reply-To: <1386256309.1791.253.camel@misato.fc.hp.com>

(2013/12/06 0:11), Toshi Kani wrote:
> On Thu, 2013-12-05 at 19:25 +0900, Yasuaki Ishimatsu wrote:
>> (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.
>
> In the second case, I assume you are worrying about the case of SLIT
> table with bad locality numbers.  Since SLIT is a matrix of the number
> of localities, it is only possible by making the table bigger than
> necessary.  Such excessive localities are safe to ignore (as they are
> ignored today) and regular users have nothing to concern about them.
> The warning message in this case may be helpful for platform vendors to
> test their firmware, but they have plenty of other methods to verify
> their SLIT table.

I understood it. So,

Reviewed-by : Yasuaki Ishimatsu

Thanks,
Yasuaki Ishimatsu


> Thanks,
> -Toshi
>
>
>
> --
> 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>

WARNING: multiple messages have this Message-ID (diff)
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: Fri, 6 Dec 2013 16:23:47 +0900	[thread overview]
Message-ID: <52A17B83.8060601@jp.fujitsu.com> (raw)
In-Reply-To: <1386256309.1791.253.camel@misato.fc.hp.com>

(2013/12/06 0:11), Toshi Kani wrote:
> On Thu, 2013-12-05 at 19:25 +0900, Yasuaki Ishimatsu wrote:
>> (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.
>
> In the second case, I assume you are worrying about the case of SLIT
> table with bad locality numbers.  Since SLIT is a matrix of the number
> of localities, it is only possible by making the table bigger than
> necessary.  Such excessive localities are safe to ignore (as they are
> ignored today) and regular users have nothing to concern about them.
> The warning message in this case may be helpful for platform vendors to
> test their firmware, but they have plenty of other methods to verify
> their SLIT table.

I understood it. So,

Reviewed-by : Yasuaki Ishimatsu

Thanks,
Yasuaki Ishimatsu


> Thanks,
> -Toshi
>
>
>
> --
> 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>
>



  reply	other threads:[~2013-12-06  7:24 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-04 21:09 [PATCH] mm, x86: Skip NUMA_NO_NODE while parsing SLIT Toshi Kani
2013-12-04 21:09 ` Toshi Kani
2013-12-05 10:25 ` Yasuaki Ishimatsu
2013-12-05 10:25   ` Yasuaki Ishimatsu
2013-12-05 15:11   ` Toshi Kani
2013-12-05 15:11     ` Toshi Kani
2013-12-06  7:23     ` Yasuaki Ishimatsu [this message]
2013-12-06  7:23       ` Yasuaki Ishimatsu
2013-12-06 14:52       ` Toshi Kani
2013-12-06 14:52         ` Toshi Kani
2013-12-05 23:21   ` David Rientjes
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=52A17B83.8060601@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 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.