From: Eduardo Habkost <ehabkost@redhat.com>
To: Babu Moger <babu.moger@amd.com>
Cc: geoff@hostfission.com, kvm@vger.kernel.org, mst@redhat.com,
kash@tripleback.net, mtosatti@redhat.com, qemu-devel@nongnu.org,
pbonzini@redhat.com, rth@twiddle.net
Subject: Re: [PATCH v14 1/6] i386: Set TOPOEXT unconditionally for comapatibility
Date: Wed, 13 Jun 2018 23:21:39 -0300 [thread overview]
Message-ID: <20180614022139.GS7451@localhost.localdomain> (raw)
In-Reply-To: <1528939107-17193-2-git-send-email-babu.moger@amd.com>
On Wed, Jun 13, 2018 at 09:18:22PM -0400, Babu Moger wrote:
> Enabling TOPOEXT feature might cause compatibility issues if
> older kernels does not set this feature. Lets set this feature
> unconditionally.
>
> Signed-off-by: Babu Moger <babu.moger@amd.com>
> ---
> target/i386/kvm.c | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/target/i386/kvm.c b/target/i386/kvm.c
> index 445e0e0..6f2cca7 100644
> --- a/target/i386/kvm.c
> +++ b/target/i386/kvm.c
> @@ -372,6 +372,12 @@ uint32_t kvm_arch_get_supported_cpuid(KVMState *s, uint32_t function,
> if (host_tsx_blacklisted()) {
> ret &= ~(CPUID_7_0_EBX_RTM | CPUID_7_0_EBX_HLE);
> }
> + } else if (function == 0x80000001 && reg == R_ECX) {
> + /* Enabling topoext feature might cause compatibility issues if
> + * older kernel does not set this feature. Lets set this feature
> + * unconditionally.
> + */
Thanks. I will apply and rewrite the comment as:
/*
* It's safe to enable TOPOEXT even if it's not returned
* by GET_SUPPORTED_CPUID. Unconditionally enabling
* TOPOEXT here let us keep CPU models runnable on
* older kernels even when TOPOEXT is enabled.
*/
> + ret |= CPUID_EXT3_TOPOEXT;
> } else if (function == 0x80000001 && reg == R_EDX) {
> /* On Intel, kvm returns cpuid according to the Intel spec,
> * so add missing bits according to the AMD spec:
> --
> 1.8.3.1
>
--
Eduardo
WARNING: multiple messages have this Message-ID (diff)
From: Eduardo Habkost <ehabkost@redhat.com>
To: Babu Moger <babu.moger@amd.com>
Cc: mst@redhat.com, marcel.apfelbaum@gmail.com, pbonzini@redhat.com,
rth@twiddle.net, mtosatti@redhat.com, qemu-devel@nongnu.org,
kvm@vger.kernel.org, kash@tripleback.net, geoff@hostfission.com
Subject: Re: [Qemu-devel] [PATCH v14 1/6] i386: Set TOPOEXT unconditionally for comapatibility
Date: Wed, 13 Jun 2018 23:21:39 -0300 [thread overview]
Message-ID: <20180614022139.GS7451@localhost.localdomain> (raw)
In-Reply-To: <1528939107-17193-2-git-send-email-babu.moger@amd.com>
On Wed, Jun 13, 2018 at 09:18:22PM -0400, Babu Moger wrote:
> Enabling TOPOEXT feature might cause compatibility issues if
> older kernels does not set this feature. Lets set this feature
> unconditionally.
>
> Signed-off-by: Babu Moger <babu.moger@amd.com>
> ---
> target/i386/kvm.c | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/target/i386/kvm.c b/target/i386/kvm.c
> index 445e0e0..6f2cca7 100644
> --- a/target/i386/kvm.c
> +++ b/target/i386/kvm.c
> @@ -372,6 +372,12 @@ uint32_t kvm_arch_get_supported_cpuid(KVMState *s, uint32_t function,
> if (host_tsx_blacklisted()) {
> ret &= ~(CPUID_7_0_EBX_RTM | CPUID_7_0_EBX_HLE);
> }
> + } else if (function == 0x80000001 && reg == R_ECX) {
> + /* Enabling topoext feature might cause compatibility issues if
> + * older kernel does not set this feature. Lets set this feature
> + * unconditionally.
> + */
Thanks. I will apply and rewrite the comment as:
/*
* It's safe to enable TOPOEXT even if it's not returned
* by GET_SUPPORTED_CPUID. Unconditionally enabling
* TOPOEXT here let us keep CPU models runnable on
* older kernels even when TOPOEXT is enabled.
*/
> + ret |= CPUID_EXT3_TOPOEXT;
> } else if (function == 0x80000001 && reg == R_EDX) {
> /* On Intel, kvm returns cpuid according to the Intel spec,
> * so add missing bits according to the AMD spec:
> --
> 1.8.3.1
>
--
Eduardo
next prev parent reply other threads:[~2018-06-14 2:21 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-14 1:18 [PATCH v14 0/6] i386: Enable TOPOEXT to support hyperthreading on AMD CPU Babu Moger
2018-06-14 1:18 ` [Qemu-devel] " Babu Moger
2018-06-14 1:18 ` [PATCH v14 1/6] i386: Set TOPOEXT unconditionally for comapatibility Babu Moger
2018-06-14 1:18 ` [Qemu-devel] " Babu Moger
2018-06-14 2:21 ` Eduardo Habkost [this message]
2018-06-14 2:21 ` Eduardo Habkost
2018-06-14 13:24 ` Moger, Babu
2018-06-14 13:24 ` [Qemu-devel] " Moger, Babu
2018-06-14 1:18 ` [PATCH v14 2/6] i386: Enable TOPOEXT feature on AMD EPYC CPU Babu Moger
2018-06-14 1:18 ` [Qemu-devel] " Babu Moger
2018-06-14 18:40 ` Eduardo Habkost
2018-06-14 18:40 ` [Qemu-devel] " Eduardo Habkost
2018-06-14 20:41 ` Moger, Babu
2018-06-14 20:41 ` [Qemu-devel] " Moger, Babu
2018-06-14 23:16 ` Moger, Babu
2018-06-14 23:16 ` [Qemu-devel] " Moger, Babu
2018-06-14 1:18 ` [PATCH v14 3/6] i386: Disable TOPOEXT feature on pc-2.12 Babu Moger
2018-06-14 1:18 ` [Qemu-devel] " Babu Moger
2018-06-14 18:40 ` Eduardo Habkost
2018-06-14 18:40 ` [Qemu-devel] " Eduardo Habkost
2018-06-14 20:41 ` Moger, Babu
2018-06-14 20:41 ` [Qemu-devel] " Moger, Babu
2018-06-14 1:18 ` [PATCH v14 4/6] cpus: Add new function topology_supports_topoext Babu Moger
2018-06-14 1:18 ` [Qemu-devel] " Babu Moger
2018-06-14 18:42 ` Eduardo Habkost
2018-06-14 18:42 ` [Qemu-devel] " Eduardo Habkost
2018-06-14 1:18 ` [PATCH v14 5/6] i386: Disable TOPOEXT feature if it cannot be supported Babu Moger
2018-06-14 1:18 ` [Qemu-devel] " Babu Moger
2018-06-14 19:13 ` Eduardo Habkost
2018-06-14 19:13 ` [Qemu-devel] " Eduardo Habkost
2018-06-14 22:18 ` Moger, Babu
2018-06-14 22:18 ` [Qemu-devel] " Moger, Babu
2018-06-14 23:09 ` Moger, Babu
2018-06-14 23:09 ` [Qemu-devel] " Moger, Babu
2018-06-15 14:09 ` Moger, Babu
2018-06-15 14:09 ` [Qemu-devel] " Moger, Babu
2018-06-14 1:18 ` [PATCH v14 6/6] i386: Remove generic SMT thread check Babu Moger
2018-06-14 1:18 ` [Qemu-devel] " 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=20180614022139.GS7451@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=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 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.