From: Thomas Huth Date: Mon, 13 Oct 2025 11:11:52 +0000 (+0200) Subject: hw/xen: Avoid non-inclusive language in params.h X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=aba49488cb4fa1c7501a454457c20be73bcba651;p=thirdparty%2Fqemu.git hw/xen: Avoid non-inclusive language in params.h Copy the latest version of Xen's params.h to the QEMU repository: https://xenbits.xen.org/gitweb/?p=xen.git;a=commitdiff;h=0291089f6ea81690f37035a124d54c51fa7ba097#patch8 With this patch, we get rid of a non-inclusive word in the comment there. Signed-off-by: Thomas Huth Acked-by: Anthony PERARD Signed-off-by: Michael Tokarev --- diff --git a/include/hw/xen/interface/hvm/params.h b/include/hw/xen/interface/hvm/params.h index a22b4ed45d2..99c40b4287f 100644 --- a/include/hw/xen/interface/hvm/params.h +++ b/include/hw/xen/interface/hvm/params.h @@ -246,16 +246,11 @@ #define HVM_PARAM_VM_GENERATION_ID_ADDR 34 /* - * Set mode for altp2m: - * disabled: don't activate altp2m (default) + * Get mode for altp2m: + * disabled: altp2m not active (default) * mixed: allow access to all altp2m ops for both in-guest and external tools * external: allow access to external privileged tools only * limited: guest only has limited access (ie. control VMFUNC and #VE) - * - * Note that 'mixed' mode has not been evaluated for safety from a - * security perspective. Before using this mode in a - * security-critical environment, each subop should be evaluated for - * safety, with unsafe subops blacklisted in XSM. */ #define HVM_PARAM_ALTP2M 35 #define XEN_ALTP2M_disabled 0