All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Beulich <jbeulich@suse.com>
To: "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Cc: "Andrew Cooper" <andrew.cooper3@citrix.com>,
	"Wei Liu" <wl@xen.org>, "Roger Pau Monné" <roger.pau@citrix.com>
Subject: [PATCH] x86: extend coverage of HLE "bad page" workaround
Date: Tue, 26 May 2020 08:49:52 +0200	[thread overview]
Message-ID: <b238f66d-37a9-3080-4f2b-90225ea17102@suse.com> (raw)

Respective Core Gen10 processor lines are affected, too.

Signed-off-by: Jan Beulich <jbeulich@suse.com>

--- a/xen/arch/x86/mm.c
+++ b/xen/arch/x86/mm.c
@@ -6045,6 +6045,8 @@ const struct platform_bad_page *__init g
     case 0x000506e0: /* errata SKL167 / SKW159 */
     case 0x000806e0: /* erratum KBL??? */
     case 0x000906e0: /* errata KBL??? / KBW114 / CFW103 */
+    case 0x000a0650: /* erratum Core Gen10 U/H/S 101 */
+    case 0x000a0660: /* erratum Core Gen10 U/H/S 101 */
         *array_size = (cpuid_eax(0) >= 7 && !cpu_has_hypervisor &&
                        (cpuid_count_ebx(7, 0) & cpufeat_mask(X86_FEATURE_HLE)));
         return &hle_bad_page;


             reply	other threads:[~2020-05-26  6:50 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-26  6:49 Jan Beulich [this message]
2020-05-26 11:17 ` [PATCH] x86: extend coverage of HLE "bad page" workaround Andrew Cooper
2020-05-26 13:35   ` Jan Beulich
2020-05-26 15:01     ` Andrew Cooper
2020-05-26 16:40       ` Jan Beulich
2023-03-17 11:39         ` Roger Pau Monné
2023-03-20  9:24           ` Jan Beulich
2023-03-21 14:51             ` Andrew Cooper
2023-03-21 15:59               ` Roger Pau Monné
2023-03-21 16:14                 ` Andrew Cooper
2023-03-21 16:31               ` Jan Beulich
2023-03-21 14:42 ` Roger Pau Monné
2023-03-21 15:51   ` Jan Beulich
2023-03-21 15:58     ` Roger Pau Monné
2023-03-21 16:03       ` 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=b238f66d-37a9-3080-4f2b-90225ea17102@suse.com \
    --to=jbeulich@suse.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=roger.pau@citrix.com \
    --cc=wl@xen.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 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.