From: Tom Lendacky <thomas.lendacky@amd.com>
To: <linux-kernel@vger.kernel.org>, <x86@kernel.org>,
<linux-coco@lists.linux.dev>, <svsm-devel@coconut-svsm.dev>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
"H. Peter Anvin" <hpa@zytor.com>,
Andy Lutomirski <luto@kernel.org>,
"Peter Zijlstra" <peterz@infradead.org>,
Dan Williams <dan.j.williams@intel.com>,
Michael Roth <michael.roth@amd.com>,
Ashish Kalra <ashish.kalra@amd.com>
Subject: [PATCH v5 07/13] x86/sev: Provide guest VMPL level to userspace
Date: Wed, 5 Jun 2024 10:18:50 -0500 [thread overview]
Message-ID: <fff846da0d8d561f9fdaf297dcf8cd907545a25b.1717600736.git.thomas.lendacky@amd.com> (raw)
In-Reply-To: <cover.1717600736.git.thomas.lendacky@amd.com>
Requesting an attestation report from userspace involves providing the
VMPL level for the report. Currently any value from 0-3 is valid because
Linux enforces running at VMPL0.
When an SVSM is present, though, Linux will not be running at VMPL0 and
only VMPL values starting at the VMPL level Linux is running at to 3 are
valid. In order to allow userspace to determine the minimum VMPL value
that can be supplied to an attestation report, create a sysfs entry that
can be used to retrieve the current VMPL level of Linux.
Signed-off-by: Tom Lendacky <thomas.lendacky@amd.com>
---
.../ABI/testing/sysfs-devices-system-cpu | 12 +++++
arch/x86/kernel/sev.c | 44 +++++++++++++++++++
2 files changed, 56 insertions(+)
diff --git a/Documentation/ABI/testing/sysfs-devices-system-cpu b/Documentation/ABI/testing/sysfs-devices-system-cpu
index e7e160954e79..8fd7ed9aee4e 100644
--- a/Documentation/ABI/testing/sysfs-devices-system-cpu
+++ b/Documentation/ABI/testing/sysfs-devices-system-cpu
@@ -605,6 +605,18 @@ Description: Umwait control
Note that a value of zero means there is no limit.
Low order two bits must be zero.
+What: /sys/devices/system/cpu/sev
+ /sys/devices/system/cpu/sev/vmpl
+Date: May 2024
+Contact: Linux kernel mailing list <linux-kernel@vger.kernel.org>
+Description: Secure Encrypted Virtualization (SEV) information
+
+ This directory is only present when running as an SEV-SNP guest.
+
+ vmpl: Reports the Virtual Machine Privilege Level (VMPL) at which
+ the SEV-SNP guest is running.
+
+
What: /sys/devices/system/cpu/svm
Date: August 2019
Contact: Linux kernel mailing list <linux-kernel@vger.kernel.org>
diff --git a/arch/x86/kernel/sev.c b/arch/x86/kernel/sev.c
index 5ba1c481b867..d09844db2361 100644
--- a/arch/x86/kernel/sev.c
+++ b/arch/x86/kernel/sev.c
@@ -2501,3 +2501,47 @@ void __init snp_remap_svsm_ca(void)
/* Update the CAA to a proper kernel address */
boot_svsm_caa = &boot_svsm_ca_page;
}
+
+static ssize_t vmpl_show(struct kobject *kobj,
+ struct kobj_attribute *attr, char *buf)
+{
+ return sysfs_emit(buf, "%d\n", snp_vmpl);
+}
+
+static struct kobj_attribute vmpl_attr = __ATTR_RO(vmpl);
+
+static struct attribute *vmpl_attrs[] = {
+ &vmpl_attr.attr,
+ NULL
+};
+
+static struct attribute_group sev_attr_group = {
+ .attrs = vmpl_attrs,
+};
+
+static int __init sev_sysfs_init(void)
+{
+ struct kobject *sev_kobj;
+ struct device *dev_root;
+ int ret;
+
+ if (!cc_platform_has(CC_ATTR_GUEST_SEV_SNP))
+ return -ENODEV;
+
+ dev_root = bus_get_dev_root(&cpu_subsys);
+ if (!dev_root)
+ return -ENODEV;
+
+ sev_kobj = kobject_create_and_add("sev", &dev_root->kobj);
+ put_device(dev_root);
+
+ if (!sev_kobj)
+ return -ENOMEM;
+
+ ret = sysfs_create_group(sev_kobj, &sev_attr_group);
+ if (ret)
+ kobject_put(sev_kobj);
+
+ return ret;
+}
+arch_initcall(sev_sysfs_init);
--
2.43.2
next prev parent reply other threads:[~2024-06-05 15:20 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-05 15:18 [PATCH v5 00/13] Provide SEV-SNP support for running under an SVSM Tom Lendacky
2024-06-05 15:18 ` [PATCH v5 01/13] x86/irqflags: Provide native versions of the local_irq_save()/restore() Tom Lendacky
2024-06-05 15:18 ` [PATCH v5 02/13] x86/sev: Check for the presence of an SVSM in the SNP Secrets page Tom Lendacky
2024-06-05 19:38 ` Borislav Petkov
2024-06-05 21:17 ` Tom Lendacky
2024-06-05 15:18 ` [PATCH v5 03/13] x86/sev: Use kernel provided SVSM Calling Areas Tom Lendacky
2024-06-06 12:36 ` Borislav Petkov
2024-06-05 15:18 ` [PATCH v5 04/13] x86/sev: Perform PVALIDATE using the SVSM when not at VMPL0 Tom Lendacky
2024-06-06 14:38 ` Borislav Petkov
2024-06-17 17:50 ` Tom Lendacky
2024-06-05 15:18 ` [PATCH v5 05/13] x86/sev: Use the SVSM to create a vCPU when not in VMPL0 Tom Lendacky
2024-06-05 15:18 ` [PATCH v5 06/13] x86/sev: Provide SVSM discovery support Tom Lendacky
2024-06-05 15:18 ` Tom Lendacky [this message]
2024-06-05 15:18 ` [PATCH v5 08/13] virt: sev-guest: Choose the VMPCK key based on executing VMPL Tom Lendacky
2024-06-05 15:18 ` [PATCH v5 09/13] configfs-tsm: Allow the privlevel_floor attribute to be updated Tom Lendacky
2024-06-14 20:47 ` Dan Williams
2024-06-05 15:18 ` [PATCH v5 10/13] fs/configfs: Add a callback to determine attribute visibility Tom Lendacky
2024-07-11 20:07 ` Christophe JAILLET
2024-06-05 15:18 ` [PATCH v5 11/13] x86/sev: Take advantage of configfs visibility support in TSM Tom Lendacky
2024-06-05 15:18 ` [PATCH v5 12/13] x86/sev: Extend the config-fs attestation support for an SVSM Tom Lendacky
2024-06-06 19:15 ` Tom Lendacky
2024-06-05 15:18 ` [PATCH v5 13/13] x86/sev: Allow non-VMPL0 execution when an SVSM is present Tom Lendacky
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=fff846da0d8d561f9fdaf297dcf8cd907545a25b.1717600736.git.thomas.lendacky@amd.com \
--to=thomas.lendacky@amd.com \
--cc=ashish.kalra@amd.com \
--cc=bp@alien8.de \
--cc=dan.j.williams@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-coco@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=michael.roth@amd.com \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=svsm-devel@coconut-svsm.dev \
--cc=tglx@linutronix.de \
--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
all inboxes | Powered by JetHome®