From: "Jörg Rödel" <joro@8bytes.org>
To: Thomas Gleixner <tglx@kernel.org>, Ingo Molnar <mingo@redhat.com>,
Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
x86@kernel.org
Cc: hpa@zytor.com, Tom Lendacky <thomas.lendacky@amd.com>,
joro@8bytes.org, linux-kernel@vger.kernel.org,
linux-coco@lists.linux.dev, Joerg Roedel <joerg.roedel@amd.com>
Subject: [PATCH 0/3 v2] x86/sev: Report MSR_AMD64_SEV in SYSFS
Date: Mon, 3 Aug 2026 14:58:24 +0200 [thread overview]
Message-ID: <20260803125827.718024-1-joro@8bytes.org> (raw)
From: Joerg Roedel <joerg.roedel@amd.com>
Hi,
Here is an updated version of my original patch to report
MSR_AMD64_SEV in SYSFS. The intention is to give user-space tooling a
way to access the MSR value without needing to expose all MSRs via
the msr.ko module.
The patches here are updated to address a Sashiko comment asking why
SEV_STATUS is only reported for SEV-SNP guests. The sev_status file is
now created for SEV and SEV-ES guests as well.
Please review.
Thanks,
Joerg
Joerg Roedel (3):
x86/coco: Add CC_ATTR_GUEST_SEV
x86/sev: Create /sys/devices/system/cpu/sev/ for all SEV guests
x86/coco/sev: Make SEV_STATUS available via SYSFS
.../ABI/testing/sysfs-devices-system-cpu | 9 +++--
arch/x86/coco/core.c | 3 ++
arch/x86/coco/sev/core.c | 33 ++++++++++++++++---
include/linux/cc_platform.h | 9 +++++
4 files changed, 47 insertions(+), 7 deletions(-)
--
2.53.0
next reply other threads:[~2026-08-03 12:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-03 12:58 Jörg Rödel [this message]
2026-08-03 12:58 ` [PATCH 1/3] x86/coco: Add CC_ATTR_GUEST_SEV Jörg Rödel
2026-08-03 12:58 ` [PATCH 2/3] x86/sev: Create /sys/devices/system/cpu/sev/ for all SEV guests Jörg Rödel
2026-08-03 12:58 ` [PATCH 3/3] x86/coco/sev: Make SEV_STATUS available via SYSFS Jörg Rödel
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=20260803125827.718024-1-joro@8bytes.org \
--to=joro@8bytes.org \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=joerg.roedel@amd.com \
--cc=linux-coco@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@kernel.org \
--cc=thomas.lendacky@amd.com \
--cc=x86@kernel.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