From: "Jan Beulich" <JBeulich@suse.com>
To: "xen-devel" <xen-devel@lists.xenproject.org>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
Brian Woods <brian.woods@amd.com>, Wei Liu <wei.liu2@citrix.com>,
Roger Pau Monne <roger.pau@citrix.com>
Subject: [Xen-devel] [PATCH v2 2/2] x86/AMD: limit C1E disable family range
Date: Fri, 05 Apr 2019 08:27:04 -0600 [thread overview]
Message-ID: <5CA765B80200007800224E6D@prv1-mh.provo.novell.com> (raw)
Message-ID: <20190405142704.cn0KqwFjA1BcOoepC1Qr1WAJE9t6udV-s0aEnOY0dgM@z> (raw)
In-Reply-To: <5CA75E460200007800224E23@prv1-mh.provo.novell.com>
Just like for other family values of 0x17 (see "x86/AMD: correct certain
Fam17 checks"), commit 3157bb4e13 ("Add MSR support for various feature
AMD processor families") made the original check for Fam11 here include
families all the way up to Fam17. The involved MSR (0xC0010055),
however, is fully reserved starting from Fam16, and the two bits of
interest are reserved for Fam12 and onwards (albeit I admit I wasn't
able to find any Fam13 doc). Restore the upper bound to be Fam11.
Signed-off-by: Jan Beulich <jbeulich@suse.com>
---
v2: New.
--- a/xen/arch/x86/cpu/amd.c
+++ b/xen/arch/x86/cpu/amd.c
@@ -628,7 +628,7 @@ static void init_amd(struct cpuinfo_x86
switch(c->x86)
{
- case 0xf ... 0x17:
+ case 0xf ... 0x11:
disable_c1e(NULL);
if (acpi_smi_cmd && (acpi_enable_value | acpi_disable_value))
amd_acpi_c1e_quirk = true;
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2019-04-05 14:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-05 13:55 [PATCH v2 0/2] x86/AMD: correct certain Fam17 checks Jan Beulich
2019-04-05 13:55 ` [Xen-devel] " Jan Beulich
2019-04-05 14:26 ` [PATCH v2 1/2] " Jan Beulich
2019-04-05 14:26 ` [Xen-devel] " Jan Beulich
2019-06-17 16:00 ` Andrew Cooper
2019-06-17 16:12 ` Jan Beulich
2019-04-05 14:27 ` Jan Beulich [this message]
2019-04-05 14:27 ` [Xen-devel] [PATCH v2 2/2] x86/AMD: limit C1E disable family range Jan Beulich
[not found] ` <5CA765B802000000001041CD@prv1-mh.provo.novell.com>
[not found] ` <5CA765B80200007800232AA3@prv1-mh.provo.novell.com>
2019-05-27 9:33 ` Ping: " Jan Beulich
2019-05-27 9:33 ` [Xen-devel] " Jan Beulich
2019-06-17 16:00 ` [Xen-devel] " Andrew Cooper
[not found] ` <5CA75E4602000000001041BD@prv1-mh.provo.novell.com>
[not found] ` <5CA75E460200007800232A93@prv1-mh.provo.novell.com>
2019-06-14 11:44 ` [Xen-devel] Ping#2: [PATCH v2 0/2] x86/AMD: correct certain Fam17 checks Jan Beulich
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=5CA765B80200007800224E6D@prv1-mh.provo.novell.com \
--to=jbeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=brian.woods@amd.com \
--cc=roger.pau@citrix.com \
--cc=wei.liu2@citrix.com \
--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).