From: Jan Beulich <jbeulich@suse.com>
To: Kevin Lampis <kevin.lampis@citrix.com>
Cc: andrew.cooper3@citrix.com, roger.pau@citrix.com,
xen-devel@lists.xenproject.org
Subject: Re: [PATCH v v3 1/7] x86: relax some CPU checks for non-64 bit CPUs
Date: Mon, 23 Mar 2026 10:54:21 +0100 [thread overview]
Message-ID: <9c69f190-72e1-4ca2-bebe-4b92031fd26f@suse.com> (raw)
In-Reply-To: <20260313163630.1073019-2-kevin.lampis@citrix.com>
On 13.03.2026 17:36, Kevin Lampis wrote:
> These checks were guarding against non-64 bit CPU models but they are
> not supported by Xen anymore so the checks are no longer needed.
>
> The switch statement was removed from mcheck_init()
> to support Intel family 18/19.
>
> Signed-off-by: Kevin Lampis <kevin.lampis@citrix.com>
Reviewed-by: Jan Beulich <jbeulich@suse.com>
next prev parent reply other threads:[~2026-03-23 9:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-13 16:36 [PATCH v v3 0/7] Remove x86 prefixed names from cpuinfo Kevin Lampis
2026-03-13 16:36 ` [PATCH v v3 1/7] x86: relax some CPU checks for non-64 bit CPUs Kevin Lampis
2026-03-23 9:54 ` Jan Beulich [this message]
2026-03-13 16:36 ` [PATCH v v3 2/7] x86: Remove x86 prefixed names from mcheck code Kevin Lampis
2026-03-23 9:59 ` Jan Beulich
2026-03-13 16:36 ` [PATCH v v3 3/7] x86: Remove x86 prefixed names from acpi code Kevin Lampis
2026-03-23 10:02 ` Jan Beulich
2026-03-13 16:36 ` [PATCH v v3 4/7] x86: Remove Intel 0x65, 0x6e, 0x5d from VMX code Kevin Lampis
2026-03-13 16:36 ` [PATCH v v3 5/7] x86: Remove x86 prefixed names from hvm code Kevin Lampis
2026-03-23 10:06 ` Jan Beulich
2026-03-13 16:36 ` [PATCH v v3 6/7] x86: Remove x86 prefixed names from x86/cpu/ files Kevin Lampis
2026-03-19 9:24 ` Jan Beulich
2026-03-19 11:34 ` Kevin Lampis
2026-03-19 13:51 ` Jan Beulich
2026-03-13 16:36 ` [PATCH v v3 7/7] x86: Remove x86 prefixed names from cpuinfo Kevin Lampis
2026-03-23 10: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=9c69f190-72e1-4ca2-bebe-4b92031fd26f@suse.com \
--to=jbeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=kevin.lampis@citrix.com \
--cc=roger.pau@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 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.