public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	the arch/x86 maintainers <x86@kernel.org>
Subject: Re: [GIT pull] x86/urgent for v5.9-rc2
Date: Mon, 31 Aug 2020 09:12:47 +0200	[thread overview]
Message-ID: <87mu2bi900.fsf@nanos.tec.linutronix.de> (raw)
In-Reply-To: <CAHk-=wj16dFx2Mx1oO2oxhJjAmsaPOqLcGvEGb86-z+v5iu5tw@mail.gmail.com>

On Sun, Aug 30 2020 at 12:13, Linus Torvalds wrote:
> On Sun, Aug 30, 2020 at 11:04 AM Thomas Gleixner <tglx@linutronix.de> wrote:
>>
>>    The historical inconsistent for_each_cpu() behaviour of
>>    ignoring the cpumask and unconditionally claiming that CPU0 is in the
>>    mask struck again. Sigh.
>
> I guess we could remove the UP optimizations these days. It's not like
> they matter like they used to.

Indeed.

> Or leave the optimizations in the sense that they wouldn't do the
> crazy bit searching, but they could look at bit 0 of the mask they're
> passed..

Yes, that's trivial enough and the compiler should turn the whole thing
into a simple conditional checking bit 0 and remove the rest of the loop
gunk.

Thanks,

        tglx

  reply	other threads:[~2020-08-31  7:12 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-30 18:03 [GIT pull] irq/urgent for v5.9-rc2 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
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 [this message]
2020-08-30 19:15   ` pr-tracker-bot
2020-08-30 19:15 ` [GIT pull] irq/urgent " pr-tracker-bot
  -- strict thread matches above, loose matches on Subject: below --
2020-08-23  8:25 [GIT pull] core/urgent " Thomas Gleixner
2020-08-23  8:25 ` [GIT pull] x86/urgent " Thomas Gleixner
2020-08-23 18:29   ` Linus Torvalds
2020-08-23 22:00     ` Thomas Gleixner
2020-08-23 22:29       ` Linus Torvalds
2020-08-23 22:26     ` Andy Lutomirski
2020-08-23 22:35       ` Linus Torvalds
2020-08-23 23:12         ` Andy Lutomirski
2020-08-23 18:39   ` 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=87mu2bi900.fsf@nanos.tec.linutronix.de \
    --to=tglx@linutronix.de \
    --cc=linux-kernel@vger.kernel.org \
    --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