linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Juergen Gross <jgross@suse.com>
To: linux-kernel@vger.kernel.org, xen-devel@lists.xenproject.org
Cc: boris.ostrovsky@oracle.com, Juergen Gross <jgross@suse.com>
Subject: [PATCH v2 05/11] x86/xen: use capabilities instead of fake cpuid values for acc
Date: Thu, 13 Apr 2017 12:11:10 +0200	[thread overview]
Message-ID: <20170413101116.723-6-jgross@suse.com> (raw)
In-Reply-To: <20170413101116.723-1-jgross@suse.com>

When running as pv domain xen_cpuid() is being used instead of
native_cpuid(). In xen_cpuid() the acc feature (thermal monitoring)
is indicated as not being present by special casing the related
cpuid leaf.

Instead of delivering fake cpuid values clear the cpu capability bit
for acc instead.

Signed-off-by: Juergen Gross <jgross@suse.com>
---
 arch/x86/xen/enlighten_pv.c | 4 +---
 1 file changed, 1 insertion(+), 3 deletions(-)

diff --git a/arch/x86/xen/enlighten_pv.c b/arch/x86/xen/enlighten_pv.c
index 37e174d9009b..53fe97bd720f 100644
--- a/arch/x86/xen/enlighten_pv.c
+++ b/arch/x86/xen/enlighten_pv.c
@@ -294,9 +294,6 @@ static void __init xen_init_cpuid_mask(void)
 	unsigned int ax, bx, cx, dx;
 	unsigned int xsave_mask;
 
-	cpuid_leaf1_edx_mask =
-		~(1 << X86_FEATURE_ACC);   /* thermal monitoring */
-
 	if (!xen_initial_domain())
 		cpuid_leaf1_edx_mask &=
 			~((1 << X86_FEATURE_ACPI));  /* disable ACPI */
@@ -325,6 +322,7 @@ static void __init xen_init_capabilities(void)
 	setup_clear_cpu_cap(X86_FEATURE_DCA);
 	setup_clear_cpu_cap(X86_FEATURE_APERFMPERF);
 	setup_clear_cpu_cap(X86_FEATURE_MTRR);
+	setup_clear_cpu_cap(X86_FEATURE_ACC);
 }
 
 static void xen_set_debugreg(int reg, unsigned long val)
-- 
2.12.0

  parent reply	other threads:[~2017-04-13 10:12 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-13 10:11 [PATCH v2 00/11] x86: xen cpuid() cleanup Juergen Gross
2017-04-13 10:11 ` [PATCH v2 01/11] xen: set cpu capabilities from xen_start_kernel() Juergen Gross
2017-04-13 10:11 ` [PATCH v2 02/11] x86/xen: don't indicate DCA support in pv domains Juergen Gross
2017-04-13 10:11 ` [PATCH v2 03/11] x86/xen: use capabilities instead of fake cpuid values for aperf Juergen Gross
2017-04-13 10:11 ` [PATCH v2 04/11] x86/xen: use capabilities instead of fake cpuid values for mtrr Juergen Gross
2017-04-13 10:11 ` Juergen Gross [this message]
2017-04-13 10:11 ` [PATCH v2 06/11] x86/xen: use capabilities instead of fake cpuid values for acpi Juergen Gross
2017-04-13 10:11 ` [PATCH v2 07/11] x86/xen: use capabilities instead of fake cpuid values for mwait Juergen Gross
2017-04-13 10:11 ` [PATCH v2 08/11] x86/xen: use capabilities instead of fake cpuid values for x2apic Juergen Gross
2017-04-13 10:11 ` [PATCH v2 09/11] x86/xen: use capabilities instead of fake cpuid values for xsave Juergen Gross
2017-04-13 10:35   ` [Xen-devel] " Andrew Cooper
2017-04-13 10:11 ` [PATCH v2 10/11] vmware: set cpu capabilities during platform initialization Juergen Gross
2017-04-13 10:29   ` Alok Kataria
2017-04-13 10:11 ` [PATCH v2 11/11] x86/cpu: remove hypervisor specific set_cpu_features Juergen Gross
2017-04-13 13:39 ` [PATCH v2 00/11] x86: xen cpuid() cleanup Boris Ostrovsky

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=20170413101116.723-6-jgross@suse.com \
    --to=jgross@suse.com \
    --cc=boris.ostrovsky@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=xen-devel@lists.xenproject.org \
    /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).