From: Ingo Molnar <mingo@kernel.org>
To: Siddh Raman Pant <code@siddh.me>
Cc: x86 <x86@kernel.org>, Dave Hansen <dave.hansen@linux.intel.com>,
Andy Lutomirski <luto@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
"H. Peter Anvin" <hpa@zytor.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-kernel-mentees
<linux-kernel-mentees@lists.linuxfoundation.org>
Subject: Re: [PATCH] x86/numa: Use cpumask_available instead of hardcoded NULL check
Date: Wed, 3 Aug 2022 11:08:19 +0200 [thread overview]
Message-ID: <Yuo7A0KYoNnbgwWT@gmail.com> (raw)
In-Reply-To: <18262ed2459.44b0d74d434377.3690496800292832933@siddh.me>
* Siddh Raman Pant <code@siddh.me> wrote:
> > Does 'allmodconfig' reproduce the warning for you:
> >
> > $ make allmodconfig
> > $ make arch/x86/mm/numa.o
> >
> > ?
> >
> > If yes, then this could be due to gcc-12, as it doesn't reproduce with
> > gcc-11 for me:
> >
> > gcc version 11.2.0 (Ubuntu 11.2.0-19ubuntu1)
> >
> > Thanks,
> >
> > Ingo
> >
>
> There is no reason why allmodconfig would trigger the warning, [...]
Well, unless I'm misreading your changelog, all the warning needs to
trigger is CONFIG_CPUMASK_OFFSTACK=y.
> as it has CONFIG_CPUMASK_OFFSTACK=y, but the warning is because of the
> other case.
What 'other case'? I've re-read the discussion and don't see it, but maybe
I'm a bit daft this morning ...
> Did you try the config file I had linked to earlier?
Yes, and it didn't trigger the warning.
Thanks,
Ingo
next prev parent reply other threads:[~2022-08-03 9:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-31 16:09 [PATCH] x86/numa: Use cpumask_available instead of hardcoded NULL check Siddh Raman Pant
2022-08-02 11:07 ` Ingo Molnar
2022-08-02 16:29 ` Siddh Raman Pant
2022-08-03 8:48 ` Ingo Molnar
2022-08-03 8:58 ` Siddh Raman Pant
2022-08-03 9:08 ` Ingo Molnar [this message]
2022-08-03 9:21 ` Siddh Raman Pant
2022-08-03 9:42 ` Ingo Molnar
2022-08-03 9:46 ` Siddh Raman Pant
2022-08-03 15:41 ` [tip: x86/urgent] " tip-bot2 for Siddh Raman Pant
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=Yuo7A0KYoNnbgwWT@gmail.com \
--to=mingo@kernel.org \
--cc=bp@alien8.de \
--cc=code@siddh.me \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--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;
as well as URLs for NNTP newsgroup(s).