linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wei Yang <richard.weiyang@gmail.com>
To: Borislav Petkov <bp@alien8.de>
Cc: Wei Yang <richard.weiyang@gmail.com>,
	tglx@linutronix.de, mingo@redhat.com, hpa@zytor.com,
	tj@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] x86/mm/numa: remove the numa_nodemask_from_meminfo()
Date: Tue, 14 Mar 2017 10:50:12 +0800	[thread overview]
Message-ID: <20170314025012.GA99092@WeideMacBook-Pro.local> (raw)
In-Reply-To: <20170313133045.oq5agzhrz43pgw5o@pd.tnic>

[-- Attachment #1: Type: text/plain, Size: 1864 bytes --]

On Mon, Mar 13, 2017 at 02:30:46PM +0100, Borislav Petkov wrote:
>On Mon, Feb 06, 2017 at 11:35:29PM +0800, Wei Yang wrote:
>> numa_nodemask_from_meminfo() is called to set bit according to
>> numa_meminfo. While the only two places for this call is used to set proper
>> bit to a copy of numa_nodes_parsed from numa_meminfo. With current code
>> path, those numa node information in numa_meminfo is a subset of
>> numa_nodes_parsed. So it is not necessary to set the bits again.
>> 
>> The following is a code path analysis to prove the numa node information in
>> numa_meminfo is a subset of numa_nodes_parsed.
>> 
>>     x86_numa_init()
>>         numa_init()
>>             Case 1
>>             acpi_numa_init()
>>                 acpi_parse_memory_affinity()
>>                     numa_add_memblk()
>>                     node_set(numa_nodes_parsed)
>>                 acpi_parse_slit()
>>                     numa_nodemask_from_meminfo()
>> 
>>             Case 2
>>             amd_numa_init()
>>                 numa_add_memblk()
>>                 node_set(numa_nodes_parsed)
>> 
>>             Case 3
>>             dummy_numa_init()
>>                 node_set(numa_nodes_parsed)
>>                 numa_add_memblk()
>> 
>>             numa_register_memblks()
>>                 numa_nodemask_from_meminfo()
>
>What about of_numa_parse_memory_nodes() ?
>

Hi, Borislav

Glad to see your comment.

Here is the only place who will invoke of_numa_parse_memory_nodes()

    arm64_numa_init()
        of_numa_init()
	    of_numa_parse_memory_nodes()

So this is an arm64 specific function.

In this patch, these numa_nodemask_from_meminfo only affects x86.

>-- 
>Regards/Gruss,
>    Boris.
>
>Good mailing practices for 400: avoid top-posting and trim the reply.

-- 
Wei Yang
Help you, Help me

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2017-03-14  2:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-06 15:35 [PATCH 1/2] x86/mm/numa: trivial fix on typo and error message Wei Yang
2017-02-06 15:35 ` [PATCH 2/2] x86/mm/numa: remove the numa_nodemask_from_meminfo() Wei Yang
2017-02-17 14:18   ` Wei Yang
2017-03-13 13:30   ` Borislav Petkov
2017-03-14  2:50     ` Wei Yang [this message]
2017-02-28  7:02 ` [PATCH 1/2] x86/mm/numa: trivial fix on typo and error message Wei Yang
2017-03-09  2:52 ` Wei Yang
2017-03-13 13:00 ` Borislav Petkov
2017-03-14  2:51   ` Wei Yang

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=20170314025012.GA99092@WeideMacBook-Pro.local \
    --to=richard.weiyang@gmail.com \
    --cc=bp@alien8.de \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=tj@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;
as well as URLs for NNTP newsgroup(s).