From: Babu Moger <babu.moger@amd.com>
To: <pbonzini@redhat.com>
Cc: <qemu-devel@nongnu.org>, <kvm@vger.kernel.org>
Subject: [PATCH v3 0/7] target/i386: Add support for perfmon-v2, RAS bits and EPYC-Turin CPU model
Date: Thu, 24 Oct 2024 17:18:18 -0500 [thread overview]
Message-ID: <cover.1729807947.git.babu.moger@amd.com> (raw)
This series adds the support for following features in qemu.
1. RAS feature bits (SUCCOR, McaOverflowRecov)
2. perfmon-v2
3. Update EPYC-Genoa to support perfmon-v2 and RAS bits
4. Support for bits related to SRSO (sbpb, ibpb-brtype, srso-user-kernel-no)
5. Added support for feature bits CPUID_Fn80000021_EAX/CPUID_Fn80000021_EBX
to address CPUID enforcement requirement in Turin platforms.
6. Add support for EPYC-Turin.
Link: https://www.amd.com/content/dam/amd/en/documents/epyc-technical-docs/programmer-references/57238.zip
Link: https://www.amd.com/content/dam/amd/en/documents/corporate/cr/speculative-return-stack-overflow-whitepaper.pdf
---
v3: Added SBPB, IBPB_BRTYPE, SRSO_USER_KERNEL_NO, ERAPS and RAPSIZE bits
to EPYC-Turin.
v2: Fixed couple of typos.
Added Reviewed-by tag from Zhao.
Rebased on top of 6d00c6f98256 ("Merge tag 'for-upstream' of https://repo.or.cz/qemu/kevin into staging")
v2: https://lore.kernel.org/kvm/cover.1723068946.git.babu.moger@amd.com/
v1: https://lore.kernel.org/qemu-devel/cover.1718218999.git.babu.moger@amd.com/
Babu Moger (6):
target/i386: Fix minor typo in NO_NESTED_DATA_BP feature bit
target/i386: Add RAS feature bits on EPYC CPU models
target/i386: Enable perfmon-v2 and RAS feature bits on EPYC-Genoa
target/i386: Expose bits related to SRSO vulnerability
target/i386: Expose new feature bits in CPUID 8000_0021_EAX/EBX
target/i386: Add support for EPYC-Turin model
Sandipan Das (1):
target/i386: Add PerfMonV2 feature bit
target/i386/cpu.c | 222 +++++++++++++++++++++++++++++++++++++++++++++-
target/i386/cpu.h | 27 +++++-
2 files changed, 242 insertions(+), 7 deletions(-)
--
2.34.1
next reply other threads:[~2024-10-24 22:23 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-24 22:18 Babu Moger [this message]
2024-10-24 22:18 ` [PATCH v3 1/7] target/i386: Fix minor typo in NO_NESTED_DATA_BP feature bit Babu Moger
2024-10-28 3:41 ` Zhao Liu
2024-10-24 22:18 ` [PATCH v3 2/7] target/i386: Add RAS feature bits on EPYC CPU models Babu Moger
2024-10-28 6:59 ` Zhao Liu
2024-10-30 18:53 ` John Allen
2024-10-24 22:18 ` [PATCH v3 3/7] target/i386: Add PerfMonV2 feature bit Babu Moger
2024-10-24 22:18 ` [PATCH v3 4/7] target/i386: Enable perfmon-v2 and RAS feature bits on EPYC-Genoa Babu Moger
2024-10-24 22:18 ` [PATCH v3 5/7] target/i386: Expose bits related to SRSO vulnerability Babu Moger
2024-10-28 8:56 ` Zhao Liu
2024-10-28 14:28 ` Moger, Babu
2024-10-24 22:18 ` [PATCH v3 6/7] target/i386: Expose new feature bits in CPUID 8000_0021_EAX/EBX Babu Moger
2024-10-24 22:18 ` [PATCH v3 7/7] target/i386: Add support for EPYC-Turin model Babu Moger
2024-10-28 8:37 ` [PATCH v3 0/7] target/i386: Add support for perfmon-v2, RAS bits and EPYC-Turin CPU model Paolo Bonzini
2024-10-28 14:23 ` Moger, Babu
2024-10-28 14:25 ` Paolo Bonzini
2024-10-28 18:27 ` Moger, Babu
2024-10-28 18:46 ` Paolo Bonzini
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=cover.1729807947.git.babu.moger@amd.com \
--to=babu.moger@amd.com \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).