From: Sergiy Kibrik <Sergiy_Kibrik@epam.com>
To: xen-devel@lists.xenproject.org
Cc: "Sergiy Kibrik" <Sergiy_Kibrik@epam.com>,
"Jan Beulich" <jbeulich@suse.com>,
"Andrew Cooper" <andrew.cooper3@citrix.com>,
"Roger Pau Monné" <roger.pau@citrix.com>,
"Stefano Stabellini" <sstabellini@kernel.org>
Subject: [XEN PATCH v2 0/5] x86: make Intel/AMD vPMU & MCE support configurable
Date: Thu, 2 May 2024 12:10:36 +0300 [thread overview]
Message-ID: <cover.1714640459.git.Sergiy_Kibrik@epam.com> (raw)
Here's a second attempt to separate support of Intel & AMD CPUs in Xen build.
The code to drive both platforms used to be built unconditionally, until recent
introduction of CONFIG_{AMD,INTEL} Kconfig options.
This series extends coverage of these options on vpmu and mcheck subsystems,
which allows not to build Intel or AMD vpmu/mcheck support if CPU vendor's support
was explicitly disabled.
Since v1 series one patch had been merged independently, and one more got to be
squashed, so series became shorter. Specific changes since v1 are provided per-patch.
v1 series here:
https://lore.kernel.org/xen-devel/cover.1713860310.git.Sergiy_Kibrik@epam.com/
-Sergiy
Sergiy Kibrik (5):
x86/vpmu: separate amd/intel vPMU code
x86/intel: move vmce_has_lmce() routine to header
x86/MCE: guard access to Intel/AMD-specific MCA MSRs
x86/MCE: guard {intel/amd}_mcheck_init() calls
x86/MCE: optional build of AMD/Intel MCE code
xen/arch/x86/cpu/Makefile | 4 +++-
xen/arch/x86/cpu/mcheck/Makefile | 8 ++++----
xen/arch/x86/cpu/mcheck/mce.c | 6 ++++--
xen/arch/x86/cpu/mcheck/mce.h | 13 +++++++++++++
xen/arch/x86/cpu/mcheck/mce_intel.c | 4 ----
xen/arch/x86/cpu/mcheck/non-fatal.c | 6 ++++++
xen/arch/x86/cpu/mcheck/vmce.c | 17 ++++++++++-------
xen/arch/x86/cpu/vpmu.c | 6 ++++--
xen/arch/x86/include/asm/mce.h | 1 -
xen/arch/x86/msr.c | 2 ++
10 files changed, 46 insertions(+), 21 deletions(-)
--
2.25.1
next reply other threads:[~2024-05-02 9:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-02 9:10 Sergiy Kibrik [this message]
2024-05-02 9:12 ` [XEN PATCH v2 1/5] x86/vpmu: separate amd/intel vPMU code Sergiy Kibrik
2024-05-06 11:09 ` Jan Beulich
2024-05-02 9:14 ` [XEN PATCH v2 2/5] x86/intel: move vmce_has_lmce() routine to header Sergiy Kibrik
2024-05-06 11:18 ` Jan Beulich
2024-05-13 8:23 ` Sergiy Kibrik
2024-05-02 9:16 ` [XEN PATCH v2 3/5] x86/MCE: guard access to Intel/AMD-specific MCA MSRs Sergiy Kibrik
2024-05-06 11:20 ` Jan Beulich
2024-05-02 9:18 ` [XEN PATCH v2 4/5] x86/MCE: guard {intel/amd}_mcheck_init() calls Sergiy Kibrik
2024-05-06 11:22 ` Jan Beulich
2024-05-02 9:21 ` [XEN PATCH v2 5/5] x86/MCE: optional build of AMD/Intel MCE code Sergiy Kibrik
2024-05-06 11:32 ` Jan Beulich
2024-05-13 9:11 ` Sergiy Kibrik
2024-05-14 7:05 ` 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=cover.1714640459.git.Sergiy_Kibrik@epam.com \
--to=sergiy_kibrik@epam.com \
--cc=andrew.cooper3@citrix.com \
--cc=jbeulich@suse.com \
--cc=roger.pau@citrix.com \
--cc=sstabellini@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 read-only IMAP folder(s) and NNTP newsgroup(s).