From: peterz@infradead.org
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Marco Elver <elver@google.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"the arch/x86 maintainers" <x86@kernel.org>
Subject: Re: [GIT pull] sched/urgent for v5.9-rc2
Date: Mon, 31 Aug 2020 09:24:27 +0200 [thread overview]
Message-ID: <20200831072427.GM1362448@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <CAHk-=wi6ufj=O-PDu=HVYw0QXpK52GPWKJfBaU4Djr0h6OFpKg@mail.gmail.com>
On Sun, Aug 30, 2020 at 11:54:19AM -0700, Linus Torvalds wrote:
> On Sun, Aug 30, 2020 at 11:04 AM Thomas Gleixner <tglx@linutronix.de> wrote:
> >
> > - Make is_idle_task() __always_inline to prevent the compiler from putting
> > it out of line into the wrong section because it's used inside noinstr
> > sections.
>
> What completely broken compiler uninlined that single-instruction function?
>
> I've obviously pulled this, but it sounds like there should be a
> compiler bug-report for this insane behavior.
>
> Or is Marco building the kernel without optimizations or something
> like that? That has not been a supported model, for various good
> reasons..
I think that was Clang with KCSAN on, KCSAN obviously makes this
function a little bigger with the instrumentation for the load(s). But
yes...
next prev parent reply other threads:[~2020-08-31 7:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-30 18:03 [GIT pull] irq/urgent " Thomas Gleixner
2020-08-30 18:03 ` [GIT pull] locking/urgent " Thomas Gleixner
2020-08-30 19:15 ` pr-tracker-bot
2020-08-30 18:03 ` [GIT pull] sched/urgent " Thomas Gleixner
2020-08-30 18:54 ` Linus Torvalds
2020-08-31 6:41 ` Marco Elver
2020-08-31 7:24 ` peterz [this message]
2020-08-31 7:38 ` Marco Elver
2020-08-30 19:15 ` pr-tracker-bot
2020-08-30 18:03 ` [GIT pull] x86/urgent " Thomas Gleixner
2020-08-30 19:13 ` Linus Torvalds
2020-08-31 7:12 ` Thomas Gleixner
2020-08-30 19:15 ` pr-tracker-bot
2020-08-30 19:15 ` [GIT pull] irq/urgent " pr-tracker-bot
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=20200831072427.GM1362448@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=elver@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--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
all inboxes | Powered by JetHome®