From: Eduardo Habkost <ehabkost@redhat.com>
To: "Moger, Babu" <Babu.Moger@amd.com>
Cc: "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>,
"mtosatti@redhat.com" <mtosatti@redhat.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"kash@tripleback.net" <kash@tripleback.net>,
"geoff@hostfission.com" <geoff@hostfission.com>
Subject: Re: [Qemu-devel] [PATCH v13 2/5] i386: Introduce auto_topoext bit to manage topoext
Date: Mon, 11 Jun 2018 17:46:23 -0300 [thread overview]
Message-ID: <20180611204623.GV7451@localhost.localdomain> (raw)
In-Reply-To: <DM5PR12MB24718C2709BB60179BAD2F9495780@DM5PR12MB2471.namprd12.prod.outlook.com>
On Mon, Jun 11, 2018 at 08:25:32PM +0000, Moger, Babu wrote:
> Hi Eduardo,
> Planning to make couple of changes after testing and review. Let me know if I missed something.
> Will wait for your feedback before the next revision.
>
> > -----Original Message-----
> > From: kvm-owner@vger.kernel.org [mailto:kvm-owner@vger.kernel.org]
> > On Behalf Of Babu Moger
> > Sent: Friday, June 8, 2018 5:56 PM
> > To: mst@redhat.com; marcel.apfelbaum@gmail.com; pbonzini@redhat.com;
> > rth@twiddle.net; ehabkost@redhat.com; mtosatti@redhat.com
> > Cc: qemu-devel@nongnu.org; kvm@vger.kernel.org; Moger, Babu
> > <Babu.Moger@amd.com>; kash@tripleback.net; geoff@hostfission.com
> > Subject: [PATCH v13 2/5] i386: Introduce auto_topoext bit to manage
> > topoext
> >
> > Introduce the auto_topoext bit to to control topoext feature.
> >
> > Also add new field auto_topoext(in X86CPUDefinition). This will
> > be used to enable topoext on newer CPU models where topoext can
> > be supported.
> >
> > Signed-off-by: Babu Moger <babu.moger@amd.com>
> > ---
> > include/hw/i386/pc.h | 4 ++++
> > target/i386/cpu.c | 12 ++++++++++++
> > target/i386/cpu.h | 5 +++++
> > 3 files changed, 21 insertions(+)
> >
> > diff --git a/include/hw/i386/pc.h b/include/hw/i386/pc.h
> > index 04d1f8c..cc30ec3 100644
> > --- a/include/hw/i386/pc.h
> > +++ b/include/hw/i386/pc.h
> > @@ -303,6 +303,10 @@ bool e820_get_entry(int, uint32_t, uint64_t *,
> > uint64_t *);
> > .driver = TYPE_X86_CPU,\
> > .property = "legacy-cache",\
> > .value = "on",\
> > + },{\
> > + .driver = TYPE_X86_CPU,\
> > + .property = "auto-topoext",\
> > + .value = "off",\
> > },
>
> We don't need this. We are already setting this false in x86_cpu_properties.
> But we need to set it "on" for EPYC on PC_COMPAT_3_0 whenever we define it.
> That will be a separate patch. Correct?
PC_COMPAT_3_0 will exist only on QEMU 3.1. If you want to define
something as the default behavior in pc-3.0, just define it as
the default in the device code, which is exactly what you are
already doing in x86_cpu_load_def() below.
In other words, just set auto_topoext=true on the CPU model table
for EPYC, and it should be enough.
On PC_COMPAT_2_12, both would work:
{ TYPE_X86_CPU, "auto-topoext", "off" }
or
{ "EPYC" "-" TYPE_X86_CPU, "auto-topoext", "off" }.
I prefer the latter, but both would work.
>
> >
> > #define PC_COMPAT_2_11 \
> > diff --git a/target/i386/cpu.c b/target/i386/cpu.c
> > index 86fb1a4..d3411ed 100644
> > --- a/target/i386/cpu.c
> > +++ b/target/i386/cpu.c
> > @@ -1283,6 +1283,8 @@ struct X86CPUDefinition {
> > FeatureWordArray features;
> > const char *model_id;
> > CPUCaches *cache_info;
> > + /* Set it if topoext can be enabled in CPU models */
> > + int auto_topoext;
> > };
> >
> > static CPUCaches epyc_cache_info = {
> > @@ -3517,6 +3519,9 @@ static void x86_cpu_load_def(X86CPU *cpu,
> > X86CPUDefinition *def, Error **errp)
> > /* legacy-cache defaults to 'off' if CPU model provides cache info */
> > cpu->legacy_cache = !def->cache_info;
> >
> > + /* Set auto_topoext if both machine property and CPU model supports it
> > */
> > + cpu->auto_topoext = cpu->auto_topoext & def->auto_topoext;
>
> This could be more appropriate like this.
>
> cpu->auto_topoext = cpu->auto_topoext && def->auto_topoext;
cpu->auto_topoext is supposed to be already false, here. Why not
just:
cpu->auto_topoext = def->auto_topoext;
?
>
> > +
> > /* Special cases not set in the X86CPUDefinition structs: */
> > /* TODO: in-kernel irqchip for hvf */
> > if (kvm_enabled()) {
> > @@ -5382,6 +5387,13 @@ static Property x86_cpu_properties[] = {
> > DEFINE_PROP_BOOL("legacy-cache", X86CPU, legacy_cache, true),
> >
> > /*
> > + * auto-topoext property will be used to enable topoext feature.
> > + * This will be disabled on all the older CPU models. Will be
> > + * enabled on newer CPU modeles which can support topology extention.
> > + */
> > + DEFINE_PROP_BOOL("auto-topoext", X86CPU, auto_topoext, false),
> > +
> > + /*
> > * From "Requirements for Implementing the Microsoft
> > * Hypervisor Interface":
> > * https://docs.microsoft.com/en-us/virtualization/hyper-v-on-
> > windows/reference/tlfs
> > diff --git a/target/i386/cpu.h b/target/i386/cpu.h
> > index 89c82be..8783d36 100644
> > --- a/target/i386/cpu.h
> > +++ b/target/i386/cpu.h
> > @@ -1409,6 +1409,11 @@ struct X86CPU {
> > */
> > bool legacy_cache;
> >
> > + /* Compatibility bits to enable topoext feature on all newer machines
> > + * Disabled on older machines. Enabled on newer CPU models
> > + */
> > + bool auto_topoext;
> > +
> > /* Compatibility bits for old machine types: */
> > bool enable_cpuid_0xb;
> >
> > --
> > 1.8.3.1
>
--
Eduardo
next prev parent reply other threads:[~2018-06-11 20:46 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-08 22:56 [Qemu-devel] [PATCH v13 0/5] i386: Enable TOPOEXT to support hyperthreading on AMD CPU Babu Moger
2018-06-08 22:56 ` [Qemu-devel] [PATCH v13 1/5] i386: Add support for CPUID_8000_001E for AMD Babu Moger
2018-06-11 20:54 ` Eduardo Habkost
2018-06-11 21:02 ` Moger, Babu
2020-06-02 17:52 ` Eduardo Habkost
2020-06-03 23:57 ` Babu Moger
2020-06-04 14:06 ` Babu Moger
2020-06-04 20:54 ` Eduardo Habkost
2020-06-05 16:21 ` Babu Moger
2018-06-08 22:56 ` [Qemu-devel] [PATCH v13 2/5] i386: Introduce auto_topoext bit to manage topoext Babu Moger
2018-06-11 20:25 ` Moger, Babu
2018-06-11 20:46 ` Eduardo Habkost [this message]
2018-06-11 20:59 ` Moger, Babu
2018-06-11 21:05 ` Eduardo Habkost
2018-06-11 21:20 ` Moger, Babu
2018-06-08 22:56 ` [Qemu-devel] [PATCH v13 3/5] i386: Enable TOPOEXT feature on AMD EPYC CPU Babu Moger
2018-06-11 20:50 ` Eduardo Habkost
2018-06-11 21:01 ` Moger, Babu
2018-06-11 21:10 ` Eduardo Habkost
2018-06-12 16:29 ` Moger, Babu
2018-06-12 17:40 ` Eduardo Habkost
2018-06-12 18:38 ` Moger, Babu
2018-06-12 19:05 ` Eduardo Habkost
2018-06-12 19:46 ` Babu Moger
2018-06-13 16:52 ` Moger, Babu
2018-06-13 17:18 ` Eduardo Habkost
2018-06-13 18:10 ` Moger, Babu
2018-06-13 18:12 ` Moger, Babu
2018-06-13 18:17 ` Eduardo Habkost
2018-06-13 18:21 ` Moger, Babu
2018-06-13 18:49 ` Eduardo Habkost
2018-06-14 0:58 ` Moger, Babu
2018-06-08 22:56 ` [Qemu-devel] [PATCH v13 4/5] i386: Verify and enable topoext feature if supported Babu Moger
2018-06-11 20:51 ` Eduardo Habkost
2018-06-11 21:01 ` Moger, Babu
2018-06-08 22:56 ` [Qemu-devel] [PATCH v13 5/5] i386: Remove generic SMT thread check 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=20180611204623.GV7451@localhost.localdomain \
--to=ehabkost@redhat.com \
--cc=Babu.Moger@amd.com \
--cc=geoff@hostfission.com \
--cc=kash@tripleback.net \
--cc=kvm@vger.kernel.org \
--cc=marcel.apfelbaum@gmail.com \
--cc=mst@redhat.com \
--cc=mtosatti@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).