From: Borislav Petkov <bp@alien8.de>
To: Wei Yang <richard.weiyang@gmail.com>
Cc: kirill@shutemov.name, tglx@linutronix.de, mingo@redhat.com,
hpa@zytor.com, tj@kernel.org, rientjes@google.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH V3 1/3] x86/numa_emulation: refine the calculation of max_emu_nid and dfl_phys_nid
Date: Tue, 18 Jul 2017 13:03:39 +0200 [thread overview]
Message-ID: <20170718105953.GA9149@nazgul.tnic> (raw)
In-Reply-To: <20170708013059.29708-2-richard.weiyang@gmail.com>
On Sat, Jul 08, 2017 at 09:30:57AM +0800, Wei Yang wrote:
> max_emu_nid and dfl_phys_nid is calculated from emu_nid_to_phys[], which is
> calculated in split_nodes_xxx_interleave(). From the logic in these
$ git grep split_nodes_xxx_interleave
$
> functions, it is assured the emu_nid_to_phys[] has meaningful value if it
> return successfully and ensures dfl_phys_nid will get a valid value.
>
> This patch removes the error branch to check invalid dfl_phys_nid and
So the check doesn't hurt anyone.
On the contrary - it is an "assertion" of sorts in otherwise complex
code and actually documents the fact that by then emu_nid_to_phys[]
needs to be setup properly.
And it is especially useful if someone decides to change that code in
the future, for whatever reason, and gets to hit that check - it'll even
be helpful in that case.
So I'd vote for keeping that check and not doing anything.
While we're at it, never say "this patch" in a commit message - that is
tautologically obvious.
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
--
next prev parent reply other threads:[~2017-07-18 11:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-08 1:30 [PATCH V3 0/3] Refine numa_emulation Wei Yang
2017-07-08 1:30 ` [PATCH V3 1/3] x86/numa_emulation: refine the calculation of max_emu_nid and dfl_phys_nid Wei Yang
2017-07-18 10:46 ` [tip:x86/debug] x86/numa_emulation: Refine " tip-bot for Wei Yang
2017-07-18 11:03 ` Borislav Petkov [this message]
2017-07-26 3:19 ` [PATCH V3 1/3] x86/numa_emulation: refine " Wei Yang
2017-07-08 1:30 ` [PATCH V3 2/3] x86/numa_emulation: assign physnode_mask directly from numa_nodes_parsed Wei Yang
2017-07-18 10:46 ` [tip:x86/debug] x86/numa_emulation: Assign " tip-bot for Wei Yang
2017-07-08 1:30 ` [PATCH V3 3/3] x86/numa_emulation: restructures numa_nodes_parsed from emulated nodes Wei Yang
2017-07-18 10:47 ` [tip:x86/debug] x86/numa_emulation: Recalculate " tip-bot for 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=20170718105953.GA9149@nazgul.tnic \
--to=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=kirill@shutemov.name \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=richard.weiyang@gmail.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®