From: Eduardo Habkost <ehabkost@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Ani Sinha <ani.sinha@nutanix.com>,
qemu-devel@nongnu.org, rth@twiddle.net
Subject: Re: [PATCH] i386: pass CLZERO to guests with EPYC CPU model on AMD ZEN platform
Date: Wed, 18 Dec 2019 12:11:44 -0300 [thread overview]
Message-ID: <20191218151144.GN498046@habkost.net> (raw)
In-Reply-To: <2883fd0e-191a-c5a4-be1c-04442c8de1c9@redhat.com>
On Wed, Dec 18, 2019 at 12:53:45PM +0100, Paolo Bonzini wrote:
> On 18/12/19 10:05, Ani Sinha wrote:
> > CLZERO CPUID should be passed on to the guests that use EPYC or EPYC-IBPB CPU
> > model when the AMD ZEN based host supports it. This change makes it recognize
> > this CPUID for guests which use EPYC or EPYC-IBPB CPU model.
Can you clarify what's the intended use case here? Why the
"if host supports it" conditional?
If you need host-dependent CPU configuration, "-cpu host" (or the
libvirt "host-model" mode) is the most appropriate solution.
> >
> > Signed-off-by: Ani Sinha <ani.sinha@nutanix.com>
> > ---
> > target/i386/cpu.c | 2 ++
> > 1 file changed, 2 insertions(+)
> >
> > diff --git a/target/i386/cpu.c b/target/i386/cpu.c
> > index 69f518a..55f0691 100644
> > --- a/target/i386/cpu.c
> > +++ b/target/i386/cpu.c
> > @@ -3813,6 +3813,8 @@ static X86CPUDefinition builtin_x86_defs[] = {
> > CPUID_EXT3_MISALIGNSSE | CPUID_EXT3_SSE4A | CPUID_EXT3_ABM |
> > CPUID_EXT3_CR8LEG | CPUID_EXT3_SVM | CPUID_EXT3_LAHF_LM |
> > CPUID_EXT3_TOPOEXT,
> > + .features[FEAT_8000_0008_EBX] =
> > + CPUID_8000_0008_EBX_CLZERO,
> > .features[FEAT_7_0_EBX] =
> > CPUID_7_0_EBX_FSGSBASE | CPUID_7_0_EBX_BMI1 | CPUID_7_0_EBX_AVX2 |
> > CPUID_7_0_EBX_SMEP | CPUID_7_0_EBX_BMI2 | CPUID_7_0_EBX_RDSEED |
> >
>
> This needs to be done only for newer machine type (or is it CPU model
> versions now? need Eduardo to respond).
If we want to add it, it has to be done as a new CPU model version.
But I don't know yet if we want to add it. Do all EPYC CPUs have
CLZERO available? If not, it's probably not advisable to add it
to EPYC (even if it's just on EPYC-v3).
--
Eduardo
next prev parent reply other threads:[~2019-12-18 15:13 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-18 9:05 [PATCH] i386: pass CLZERO to guests with EPYC CPU model on AMD ZEN platform Ani Sinha
2019-12-18 11:53 ` Paolo Bonzini
2019-12-18 15:11 ` Eduardo Habkost [this message]
2020-01-20 10:56 ` Ani Sinha
2020-02-05 22:37 ` Eduardo Habkost
2020-02-06 0:00 ` Moger, Babu
2020-02-06 5:46 ` Ani Sinha
2020-02-06 5:53 ` Ani Sinha
2020-02-06 15:30 ` Babu Moger
2020-02-06 16:03 ` Eduardo Habkost
2020-02-06 15:52 ` Eduardo Habkost
2020-02-06 15:55 ` Babu Moger
2019-12-22 7:32 ` Ani Sinha
2019-12-22 8:15 ` Paolo Bonzini
2019-12-23 8:14 ` Ani Sinha
2019-12-23 8:50 ` Ani Sinha
[not found] <yes>
2019-12-04 9:36 ` Ani Sinha
2019-12-16 9:31 ` Ani Sinha
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=20191218151144.GN498046@habkost.net \
--to=ehabkost@redhat.com \
--cc=ani.sinha@nutanix.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 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.