Re: [PATCH V1 3/6] xen/virtio: Add option to restrict memory access under Xen
From: Borislav Petkov <bp@alien8.de>
Date: 2022-04-25 22:23:21
Also in:
lkml, xen-devel
On Mon, Apr 25, 2022 at 11:38:36PM +0300, Oleksandr wrote:
quoted hunk ↗ jump to hunk
diff --git a/include/linux/cc_platform.h b/include/linux/cc_platform.h index efd8205..d06bc7a 100644 --- a/include/linux/cc_platform.h +++ b/include/linux/cc_platform.h@@ -72,6 +72,19 @@ enum cc_attr {* Examples include TDX guest & SEV. */ CC_ATTR_GUEST_UNROLL_STRING_IO, + + /** + * @CC_ATTR_GUEST_MEM_ACCESS_RESTRICTED: Restricted memory access to + * Guest memory is active + * + * The platform/OS is running as a guest/virtual machine and uses + * the restricted access to its memory. This attribute is set if either + * Guest memory encryption or restricted memory access using Xen grant + * mappings is active. + * + * Examples include Xen guest and SEV.
Wait, whaaat?
The cc_platform* stuff is for *confidential computing* guests to check
different platform aspects.
From quickly skimming over this, this looks like a misuse to me.
Why can't you query this from the hypervisor just like you do your other
querying about what is supported, etc? Hypercalls, CPUID, whatever...
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel