linux-kernel - Re: [PATCH] x86/mm: Print the encryption features correctly when a paravisor is present

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <00ff2f75-e780-4e2d-bcc9-f441f5ef879c@intel.com>
Date:   Thu, 19 Oct 2023 08:54:23 -0700
From:   Dave Hansen <dave.hansen@...el.com>
To:     Dexuan Cui <decui@...rosoft.com>, kys@...rosoft.com,
        haiyangz@...rosoft.com, wei.liu@...nel.org, tglx@...utronix.de,
        mingo@...hat.com, bp@...en8.de, dave.hansen@...ux.intel.com,
        x86@...nel.org, hpa@...or.com, luto@...nel.org,
        peterz@...radead.org, stefan.bader@...onical.com,
        tim.gardner@...onical.com, roxana.nicolescu@...onical.com,
        cascardo@...onical.com, mikelley@...rosoft.com, jgross@...e.com,
        sathyanarayanan.kuppuswamy@...ux.intel.com,
        kirill.shutemov@...ux.intel.com, sashal@...nel.org,
        matija.glavinic-pecotic.ext@...ia.com, linux-hyperv@...r.kernel.org
Cc:     linux-kernel@...r.kernel.org
Subject: Re: [PATCH] x86/mm: Print the encryption features correctly when a
 paravisor is present

> --- a/arch/x86/hyperv/ivm.c
> +++ b/arch/x86/hyperv/ivm.c
> @@ -450,6 +450,16 @@ static bool hv_is_private_mmio(u64 addr)
>  	return false;
>  }
>  
> +static void hv_print_mem_enc_feature_info(void)
> +{
> +	enum hv_isolation_type type = hv_get_isolation_type();
> +
> +	if (type == HV_ISOLATION_TYPE_SNP)
> +		pr_info("Memory Encryption Features active: AMD SEV\n");
> +	else if (type == HV_ISOLATION_TYPE_TDX)
> +		pr_info("Memory Encryption Features active: Intel TDX\n");
> +}

If we draw this to its logical conclusion, every paravisor will need a
pr_info() for every hardware CoCo implementation.  That M*N pr_info()s.
That seems nuts.