From: Peter Zijlstra <peterz@infradead.org>
To: hpa@zytor.com
Cc: Thomas Gleixner <tglx@linutronix.de>,
Paolo Bonzini <pbonzini@redhat.com>,
Borislav Petkov <bp@alien8.de>,
Sean Christopherson <sean.j.christopherson@intel.com>,
Andy Lutomirski <luto@kernel.org>, Ingo Molnar <mingo@redhat.com>,
x86@kernel.org, linux-kernel@vger.kernel.org,
Dave Hansen <dave.hansen@intel.com>,
Chang Seok Bae <chang.seok.bae@intel.com>,
Sasha Levin <sashal@kernel.org>,
kvm@vger.kernel.org, Tom Lendacky <thomas.lendacky@amd.com>
Subject: Re: [PATCH] x86/entry/64: Disallow RDPID in paranoid entry if KVM is enabled
Date: Fri, 21 Aug 2020 22:02:07 +0200 [thread overview]
Message-ID: <20200821200207.GW3982@worktop.programming.kicks-ass.net> (raw)
In-Reply-To: <5120CF63-12EB-4701-B303-C0A96201F5A2@zytor.com>
On Fri, Aug 21, 2020 at 12:55:53PM -0700, hpa@zytor.com wrote:
> It is hardly going to be a performance difference for paranoid entry,
> which is hopefully rare enough that it falls into the noise.
Try perf some day ;-)
But yeah, given the utter trainwreck that NMIs are anyway, this is all
not going to matter much.
next prev parent reply other threads:[~2020-08-21 20:02 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-21 2:50 [PATCH] x86/entry/64: Disallow RDPID in paranoid entry if KVM is enabled Sean Christopherson
2020-08-21 7:24 ` peterz
2020-08-21 7:44 ` Borislav Petkov
2020-08-21 7:47 ` Borislav Petkov
2020-08-21 8:09 ` Paolo Bonzini
2020-08-21 8:16 ` Borislav Petkov
2020-08-21 9:05 ` Paolo Bonzini
2020-08-21 9:22 ` Borislav Petkov
2020-08-21 9:44 ` Paolo Bonzini
2020-08-21 9:48 ` Borislav Petkov
2020-08-21 10:07 ` Paolo Bonzini
2020-08-22 16:42 ` Andy Lutomirski
2020-09-16 16:54 ` Paolo Bonzini
2020-08-21 9:28 ` Thomas Gleixner
2020-08-21 9:37 ` Paolo Bonzini
2020-08-21 19:55 ` hpa
2020-08-21 20:02 ` Peter Zijlstra [this message]
2020-08-21 8:56 ` kernel test robot
2020-08-21 10:28 ` kernel test robot
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=20200821200207.GW3982@worktop.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=bp@alien8.de \
--cc=chang.seok.bae@intel.com \
--cc=dave.hansen@intel.com \
--cc=hpa@zytor.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=sashal@kernel.org \
--cc=sean.j.christopherson@intel.com \
--cc=tglx@linutronix.de \
--cc=thomas.lendacky@amd.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