From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Pu Wen <puwen@hygon.cn>
Cc: qemu-devel@nongnu.org, pbonzini@redhat.com, rth@twiddle.net,
ehabkost@redhat.com, mst@redhat.com, marcel.apfelbaum@gmail.com
Subject: Re: [Qemu-devel] [PATCH v3] i386: Add new Hygon 'Dhyana' CPU model
Date: Tue, 16 Apr 2019 13:12:41 +0100 [thread overview]
Message-ID: <20190416121241.GL31311@redhat.com> (raw)
In-Reply-To: <1555416373-28690-1-git-send-email-puwen@hygon.cn>
On Tue, Apr 16, 2019 at 08:06:13PM +0800, Pu Wen wrote:
> Add a new base CPU model called 'Dhyana' to model processors from Hygon
> Dhyana(family 18h), which derived from AMD EPYC(family 17h).
>
> The following features bits have been removed compare to AMD EPYC:
> aes, pclmulqdq, sha_ni
>
> The Hygon Dhyana support to KVM in Linux is already accepted upstream[1].
> So add Hygon Dhyana support to Qemu is necessary to create Hygon's own
> CPU model.
>
> Reference:
> [1] https://git.kernel.org/tip/fec98069fb72fb656304a3e52265e0c2fc9adf87
>
> Signed-off-by: Pu Wen <puwen@hygon.cn>
> ---
> v2->v3:
> - Remove the Dhyana machine types in the back-compat property tables
> since there is no Dhyana CPU model in older QEMU releases.
>
> v1->v2:
> - Remove CPU model 'Dhyana' and rename the CPU model 'Dhyana-IBPB' to
> 'Dhyana' because Dhyana CPUs already have the IBPB feature.
>
> target/i386/cpu.c | 50 ++++++++++++++++++++++++++++++++++++++++++++++++++
> target/i386/cpu.h | 2 ++
> 2 files changed, 52 insertions(+)
Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
WARNING: multiple messages have this Message-ID (diff)
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Pu Wen <puwen@hygon.cn>
Cc: ehabkost@redhat.com, mst@redhat.com, qemu-devel@nongnu.org,
pbonzini@redhat.com, rth@twiddle.net
Subject: Re: [Qemu-devel] [PATCH v3] i386: Add new Hygon 'Dhyana' CPU model
Date: Tue, 16 Apr 2019 13:12:41 +0100 [thread overview]
Message-ID: <20190416121241.GL31311@redhat.com> (raw)
Message-ID: <20190416121241.LGXGxHcNoq-y0VpWVVBMW4b-t3kQVEP1jcuTN2MB_KE@z> (raw)
In-Reply-To: <1555416373-28690-1-git-send-email-puwen@hygon.cn>
On Tue, Apr 16, 2019 at 08:06:13PM +0800, Pu Wen wrote:
> Add a new base CPU model called 'Dhyana' to model processors from Hygon
> Dhyana(family 18h), which derived from AMD EPYC(family 17h).
>
> The following features bits have been removed compare to AMD EPYC:
> aes, pclmulqdq, sha_ni
>
> The Hygon Dhyana support to KVM in Linux is already accepted upstream[1].
> So add Hygon Dhyana support to Qemu is necessary to create Hygon's own
> CPU model.
>
> Reference:
> [1] https://git.kernel.org/tip/fec98069fb72fb656304a3e52265e0c2fc9adf87
>
> Signed-off-by: Pu Wen <puwen@hygon.cn>
> ---
> v2->v3:
> - Remove the Dhyana machine types in the back-compat property tables
> since there is no Dhyana CPU model in older QEMU releases.
>
> v1->v2:
> - Remove CPU model 'Dhyana' and rename the CPU model 'Dhyana-IBPB' to
> 'Dhyana' because Dhyana CPUs already have the IBPB feature.
>
> target/i386/cpu.c | 50 ++++++++++++++++++++++++++++++++++++++++++++++++++
> target/i386/cpu.h | 2 ++
> 2 files changed, 52 insertions(+)
Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2019-04-16 12:13 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-16 12:06 [Qemu-devel] [PATCH v3] i386: Add new Hygon 'Dhyana' CPU model Pu Wen
2019-04-16 12:06 ` Pu Wen
2019-04-16 12:12 ` Daniel P. Berrangé [this message]
2019-04-16 12:12 ` Daniel P. Berrangé
2019-04-16 14:17 ` Pavel Hrdina
2019-04-16 14:17 ` Pavel Hrdina
2019-04-16 18:02 ` Eduardo Habkost
2019-04-16 18:02 ` Eduardo Habkost
2019-04-17 14:53 ` Pu Wen
2019-04-17 14:53 ` Pu Wen
2019-04-17 19:26 ` Pavel Hrdina
2019-04-17 19:26 ` Pavel Hrdina
2019-04-18 8:48 ` Daniel P. Berrangé
2019-04-18 8:48 ` Daniel P. Berrangé
2019-04-18 9:59 ` Pavel Hrdina
2019-04-18 9:59 ` Pavel Hrdina
2019-04-18 14:05 ` Eduardo Habkost
2019-04-18 14:05 ` Eduardo Habkost
2019-04-18 14:27 ` Pavel Hrdina
2019-04-18 14:27 ` Pavel Hrdina
2019-04-16 18:02 ` Eduardo Habkost
2019-04-16 18:02 ` Eduardo Habkost
2019-04-17 14:53 ` Pu Wen
2019-04-17 14:53 ` Pu Wen
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=20190416121241.GL31311@redhat.com \
--to=berrange@redhat.com \
--cc=ehabkost@redhat.com \
--cc=marcel.apfelbaum@gmail.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=puwen@hygon.cn \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.