From: Dave Hansen <dave.hansen@linux.intel.com>
To: Peter Zijlstra <peterz@infradead.org>,
Alison Schofield <alison.schofield@intel.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@kernel.org>,
Luck@alison-desk.jf.intel.com, Tony <tony.luck@intel.com>,
Tim Chen <tim.c.chen@linux.intel.com>,
"H. Peter Anvin" <hpa@linux.intel.com>,
Borislav Petkov <bp@alien8.de>,
David Rientjes <rientjes@google.com>,
Igor Mammedov <imammedo@redhat.com>,
Prarit Bhargava <prarit@redhat.com>,
brice.goglin@gmail.com, x86@kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] x86,sched: allow topologies where NUMA nodes share an LLC
Date: Thu, 22 Mar 2018 16:55:48 -0700 [thread overview]
Message-ID: <84b2c73d-e388-36dd-729e-a5baa4b29d07@linux.intel.com> (raw)
In-Reply-To: <20180322232030.GA4043@hirez.programming.kicks-ass.net>
On 03/22/2018 04:20 PM, Peter Zijlstra wrote:
>> + /*
>> + * Return value doesn't actually matter because we
>> + * are throwing away coregroups for scheduling anyway.
>> + * Return false to bypass topology broken bug messages
>> + * and fixups in sched_domain().
>> + */
>> + return false;
> IIRC that return value _does_ matter because the resulting mask still
> ends up user visible in sysfs.
>
> IIRC I went over with this dhansen a week or so ago, but I cannot now
> recall what we settled on as being the right return value and for what
> reason.
IIRC, a 'return true' true keeps the topology information and a 'return
false' throws it away. We chose 'false' here because without it some
other warnings showed up in another part of the code:
BUG: arch topology borken the MC domain not a subset of the NODE domain
I think the right thing to do is just remove the first sentence of the
comment.
next prev parent reply other threads:[~2018-03-22 23:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-22 20:49 Alison Schofield
2018-03-22 23:20 ` Peter Zijlstra
2018-03-22 23:55 ` Dave Hansen [this message]
2018-03-22 23:30 ` Luck, Tony
2018-03-26 22:19 ` Alison Schofield
2018-03-26 22:45 ` Luck, Tony
2018-03-23 0:42 ` Tim Chen
2018-03-24 0:17 ` Alison Schofield
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=84b2c73d-e388-36dd-729e-a5baa4b29d07@linux.intel.com \
--to=dave.hansen@linux.intel.com \
--cc=Luck@alison-desk.jf.intel.com \
--cc=alison.schofield@intel.com \
--cc=bp@alien8.de \
--cc=brice.goglin@gmail.com \
--cc=hpa@linux.intel.com \
--cc=imammedo@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=prarit@redhat.com \
--cc=rientjes@google.com \
--cc=tglx@linutronix.de \
--cc=tim.c.chen@linux.intel.com \
--cc=tony.luck@intel.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
Powered by JetHome