From: Wei Yang <richard.weiyang@gmail.com>
To: kirill@shutemov.name, bp@alien8.de, tglx@linutronix.de,
mingo@redhat.com, hpa@zytor.com, tj@kernel.org,
rientjes@google.com
Cc: linux-kernel@vger.kernel.org, Wei Yang <richard.weiyang@gmail.com>
Subject: [PATCH V2 0/3] Refine numa_emulation
Date: Tue, 2 May 2017 21:04:50 +0800 [thread overview]
Message-ID: <20170502130453.5933-1-richard.weiyang@gmail.com> (raw)
My previous patch "x86/mm/numa: Remove numa_nodemask_from_meminfo()" hits a
problem in numa_emulation. The reason is numa_nodes_parsed is not set
correctly after emulation.
This patch set tries to fix this and also with two code refine.
Detailed discussions are in this thread:
https://lkml.org/lkml/2017/3/13/1230
and test result is posted :
https://lkml.org/lkml/2017/4/10/641
V2:
* refresh the change log based on David comments
* use nodes_clear()
Wei Yang (3):
x86/numa_emulation: fix potential memory leak
x86/numa_emulation: assign physnode_mask directly from
numa_nodes_parsed
x86/numa_emulation: restructures numa_nodes_parsed from emulated nodes
arch/x86/mm/numa_emulation.c | 61 ++++++++++++++++++++++++--------------------
1 file changed, 33 insertions(+), 28 deletions(-)
--
2.11.0
next reply other threads:[~2017-05-02 13:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-02 13:04 Wei Yang [this message]
2017-05-02 13:04 ` [PATCH V2 1/3] x86/numa_emulation: fix potential memory leak Wei Yang
2017-06-26 15:31 ` Borislav Petkov
2017-06-26 23:11 ` Wei Yang
2017-06-27 18:10 ` Borislav Petkov
2017-06-27 23:37 ` Wei Yang
2017-05-02 13:04 ` [PATCH V2 2/3] x86/numa_emulation: assign physnode_mask directly from numa_nodes_parsed Wei Yang
2017-06-26 18:40 ` Borislav Petkov
2017-06-26 23:12 ` Wei Yang
2017-05-02 13:04 ` [PATCH V2 3/3] x86/numa_emulation: restructures numa_nodes_parsed from emulated nodes Wei Yang
2017-06-06 3:15 ` [PATCH V2 0/3] Refine numa_emulation Wei Yang
2017-06-25 0:26 ` 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=20170502130453.5933-1-richard.weiyang@gmail.com \
--to=richard.weiyang@gmail.com \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=kirill@shutemov.name \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rientjes@google.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
all inboxes | Powered by JetHome®