From: Liang Yan <LYan@suse.com>
To: "Moger, Babu" <Babu.Moger@amd.com>,
"mst@redhat.com" <mst@redhat.com>,
"marcel.apfelbaum@gmail.com" <marcel.apfelbaum@gmail.com>,
"pbonzini@redhat.com" <pbonzini@redhat.com>,
"rth@twiddle.net" <rth@twiddle.net>,
"ehabkost@redhat.com" <ehabkost@redhat.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [PATCH v2 0/2] Add support for 2nd generation AMD EPYC processors
Date: Tue, 7 Jan 2020 18:47:57 +0000 [thread overview]
Message-ID: <0a6fe793-d5b1-bb9e-b9b3-fb8fefb26cb6@suse.com> (raw)
In-Reply-To: <157314957337.23828.3860599077487615762.stgit@naples-babu.amd.com>
Kindly Ping.
Just wondering if there are any plans for it.
Best,
Liang
On 11/7/19 1:00 PM, Moger, Babu wrote:
> The following series adds the support for 2nd generation AMD EPYC Processors
> on qemu guests. The model display name for 2nd generation will be EPYC-Rome.
>
> Also fixes few missed cpu feature bits in 1st generation EPYC models.
>
> The Reference documents are available at
> https://developer.amd.com/wp-content/resources/55803_0.54-PUB.pdf
> https://www.amd.com/system/files/TechDocs/24594.pdf
>
> ---
> v2: Used the versioned CPU models instead of machine-type-based CPU
> compatibility (commented by Eduardo).
>
> Babu Moger (2):
> i386: Add missing cpu feature bits in EPYC model
> i386: Add 2nd Generation AMD EPYC processors
>
>
> target/i386/cpu.c | 119 +++++++++++++++++++++++++++++++++++++++++++++++++++--
> target/i386/cpu.h | 2 +
> 2 files changed, 116 insertions(+), 5 deletions(-)
>
> --
>
next prev parent reply other threads:[~2020-01-07 19:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-07 18:00 [PATCH v2 0/2] Add support for 2nd generation AMD EPYC processors Moger, Babu
2019-11-07 18:00 ` [PATCH v2 1/2] i386: Add missing cpu feature bits in EPYC model Moger, Babu
2019-11-07 18:01 ` [PATCH v2 2/2] i386: Add 2nd Generation AMD EPYC processors Moger, Babu
2020-01-07 18:47 ` Liang Yan [this message]
2020-01-08 16:27 ` [PATCH v2 0/2] Add support for 2nd generation " Babu Moger
2020-01-24 20:35 ` Babu Moger
2020-03-05 21:12 ` Eduardo Habkost
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=0a6fe793-d5b1-bb9e-b9b3-fb8fefb26cb6@suse.com \
--to=lyan@suse.com \
--cc=Babu.Moger@amd.com \
--cc=ehabkost@redhat.com \
--cc=marcel.apfelbaum@gmail.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
/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).