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, 24 Aug 2020 00:00:59 +0200	[thread overview]
Message-ID: <87ft8dqaxw.fsf@nanos.tec.linutronix.de> (raw)
In-Reply-To: <CAHk-=wiQQRS1f0qMwVVWKd6YHJ9K3bUK4BR2zoeGeCWRpTM3aw@mail.gmail.com>

On Sun, Aug 23 2020 at 11:29, Linus Torvalds wrote:
> On Sun, Aug 23, 2020 at 1:26 AM Thomas Gleixner <tglx@linutronix.de> wrote:
>>
>> Remove the RDPID optimization, which is not even
>> backed by numbers from the paranoid entry path instead.
>
> Ugh, that's sad. I'd expect the LSL to be quite a bit slower than the
> RDPID on raw hardware, since LSL has to go out to the GDT.

We asked for numbers several times but so far we got none and some quick
checks I did myself are in the noise.

> And I don't think we need the GDT for anything else normally, so it's
> not even going to be cached.

Who cares, really?

It's pretty irrelevant because the main source of horrors are in having
to run through _ALL_ registered NMI handlers. Why would you worry about
the extra cache miss? It gets worse when the NMI handler needs to access
the NMI cause register and that happens more often than you would expect
in the cases where it matters, e.g. high frequency PERF NMIs, due to the
well designed hardware mechanism.

OTOH, enforcing the writes on every VMENTER/EXIT is insanely expensive
compared to the maybe RDPID advantage.

While my general reasoning is that virtualization causes more problems
than it solves, in this particular case insisting on a few bare metal
cycles in paranoid entry would be beyond hypocritical.

> Oh well.

My summary would be less politically correct, so I just join the choir:

   Oh well ...

Thanks,

        tglx


  reply	other threads:[~2020-08-23 22:01 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-23  8:25 [GIT pull] core/urgent for v5.9-rc2 Thomas Gleixner
2020-08-23  8:25 ` [GIT pull] efi/urgent " Thomas Gleixner
2020-08-23 18:39   ` pr-tracker-bot
2020-08-23  8:25 ` [GIT pull] perf/urgent " Thomas Gleixner
2020-08-23 18:16   ` Linus Torvalds
2020-08-23 21:25     ` Thomas Gleixner
2020-08-23 18:39   ` pr-tracker-bot
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 [this message]
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
2020-08-23 18:39 ` [GIT pull] core/urgent " pr-tracker-bot
  -- strict thread matches above, loose matches on Subject: below --
2020-08-30 18:03 [GIT pull] irq/urgent " Thomas Gleixner
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

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=87ft8dqaxw.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