From: Babu Moger <babu.moger@amd.com>
To: <pbonzini@redhat.com>
Cc: <mtosatti@redhat.com>, <kvm@vger.kernel.org>, <mst@redhat.com>,
<marcel.apfelbaum@gmail.com>, <imammedo@redhat.com>,
<richard.henderson@linaro.org>, <yang.zhong@intel.com>,
<jing2.liu@intel.com>, <vkuznets@redhat.com>,
<qemu-devel@nongnu.org>, <michael.roth@amd.com>
Subject: [PATCH 0/5] Update AMD EPYC CPU Models
Date: Fri, 2 Dec 2022 13:47:05 -0600 [thread overview]
Message-ID: <167001034454.62456.7111414518087569436.stgit@bmoger-ubuntu> (raw)
This series adds following changes.
a. Allow versioned CPUs to specify new cache_info pointers.
b. Add EPYC-v4, EPYC-Rome-v3 and EPYC-Milan-v2 fixing the
cache_info.complex_indexing.
c. Introduce EPYC-Milan-v2 by adding few missing feature bits.
---
Babu Moger (3):
target/i386: Add a couple of feature bits in 8000_0008_EBX
target/i386: Add feature bits for CPUID_Fn80000021_EAX
target/i386: Add missing feature bits in EPYC-Milan model
Michael Roth (2):
target/i386: allow versioned CPUs to specify new cache_info
target/i386: Add new EPYC CPU versions with updated cache_info
target/i386/cpu.c | 252 +++++++++++++++++++++++++++++++++++++++++++++-
target/i386/cpu.h | 12 +++
2 files changed, 259 insertions(+), 5 deletions(-)
--
next reply other threads:[~2022-12-02 19:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-02 19:47 Babu Moger [this message]
2022-12-02 19:47 ` [PATCH 1/5] target/i386: allow versioned CPUs to specify new cache_info Babu Moger
2022-12-02 19:47 ` [PATCH 2/5] target/i386: Add new EPYC CPU versions with updated cache_info Babu Moger
2022-12-02 19:47 ` [PATCH 3/5] target/i386: Add a couple of feature bits in 8000_0008_EBX Babu Moger
2022-12-02 19:47 ` [PATCH 4/5] target/i386: Add feature bits for CPUID_Fn80000021_EAX Babu Moger
2022-12-02 19:47 ` [PATCH 5/5] target/i386: Add missing feature bits in EPYC-Milan model Babu Moger
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=167001034454.62456.7111414518087569436.stgit@bmoger-ubuntu \
--to=babu.moger@amd.com \
--cc=imammedo@redhat.com \
--cc=jing2.liu@intel.com \
--cc=kvm@vger.kernel.org \
--cc=marcel.apfelbaum@gmail.com \
--cc=michael.roth@amd.com \
--cc=mst@redhat.com \
--cc=mtosatti@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=vkuznets@redhat.com \
--cc=yang.zhong@intel.com \
/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).