From: Pawan Gupta <pawan.kumar.gupta@linux.intel.com>
To: Amit Shah <amit@kernel.org>
Cc: linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
x86@kernel.org, linux-doc@vger.kernel.org, amit.shah@amd.com,
thomas.lendacky@amd.com, bp@alien8.de, tglx@linutronix.de,
peterz@infradead.org, jpoimboe@kernel.org, corbet@lwn.net,
mingo@redhat.com, dave.hansen@linux.intel.com, hpa@zytor.com,
seanjc@google.com, pbonzini@redhat.com,
daniel.sneddon@linux.intel.com, kai.huang@intel.com,
sandipan.das@amd.com, boris.ostrovsky@oracle.com,
Babu.Moger@amd.com, david.kaplan@amd.com
Subject: Re: [PATCH 1/2] x86: cpu/bugs: add support for AMD ERAPS feature
Date: Thu, 31 Oct 2024 16:03:58 -0700 [thread overview]
Message-ID: <20241031225900.k3epw7xej757kz4d@desk> (raw)
In-Reply-To: <20241031153925.36216-2-amit@kernel.org>
On Thu, Oct 31, 2024 at 04:39:24PM +0100, Amit Shah wrote:
> From: Amit Shah <amit.shah@amd.com>
>
> Remove explicit RET stuffing / filling on VMEXITs and context
> switches on AMD CPUs with the ERAPS feature (Turin+).
>
> With the Enhanced Return Address Prediction Security feature, any
> hardware TLB flush results in flushing of the RSB (aka RAP in AMD spec).
> This guarantees an RSB flush across context switches.
Is it that the mov to CR3 triggers the RSB flush?
> Feature documented in AMD PPR 57238.
I couldn't find ERAPS feature description here, I could only manage to find
the bit position:
24 ERAPS. Read-only. Reset: 1. Indicates support for enhanced return
address predictor security.
Could you please point me to the document/section where this is described?
next prev parent reply other threads:[~2024-10-31 23:04 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-31 15:39 [PATCH 0/2] Add support for the " Amit Shah
2024-10-31 15:39 ` [PATCH 1/2] x86: cpu/bugs: add support for AMD " Amit Shah
2024-10-31 23:03 ` Pawan Gupta [this message]
2024-11-04 8:57 ` Shah, Amit
2024-11-04 14:52 ` Andrew Cooper
2024-11-04 15:00 ` Shah, Amit
2024-10-31 23:11 ` Dave Hansen
2024-11-04 8:58 ` Shah, Amit
2024-11-04 16:11 ` Dave Hansen
2024-11-04 16:13 ` Shah, Amit
2024-11-04 16:26 ` Dave Hansen
2024-11-04 17:22 ` Shah, Amit
2024-11-04 17:45 ` Dave Hansen
2024-11-05 0:04 ` Andrew Cooper
2024-11-05 10:39 ` Shah, Amit
2024-11-05 14:54 ` Kaplan, David
2024-11-05 16:19 ` Dave Hansen
2024-11-05 16:25 ` Shah, Amit
2024-11-04 5:40 ` [tip: x86/cpu] x86/bugs: Add " tip-bot2 for Amit Shah
2024-10-31 15:39 ` [PATCH 2/2] x86: kvm: svm: add support for ERAPS and FLUSH_RAP_ON_VMRUN Amit Shah
2024-10-31 23:13 ` Pawan Gupta
2024-11-01 4:14 ` kernel test robot
2024-11-01 9:26 ` Amit Shah
2024-11-04 5:18 ` Borislav Petkov
2024-11-04 11:16 ` Shah, Amit
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=20241031225900.k3epw7xej757kz4d@desk \
--to=pawan.kumar.gupta@linux.intel.com \
--cc=Babu.Moger@amd.com \
--cc=amit.shah@amd.com \
--cc=amit@kernel.org \
--cc=boris.ostrovsky@oracle.com \
--cc=bp@alien8.de \
--cc=corbet@lwn.net \
--cc=daniel.sneddon@linux.intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=david.kaplan@amd.com \
--cc=hpa@zytor.com \
--cc=jpoimboe@kernel.org \
--cc=kai.huang@intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peterz@infradead.org \
--cc=sandipan.das@amd.com \
--cc=seanjc@google.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
all inboxes | Powered by JetHome®