From: Dave Hansen <dave.hansen@intel.com>
To: Dexuan Cui <decui@microsoft.com>,
kys@microsoft.com, haiyangz@microsoft.com, wei.liu@kernel.org,
tglx@linutronix.de, mingo@redhat.com, bp@alien8.de,
dave.hansen@linux.intel.com, x86@kernel.org, hpa@zytor.com,
luto@kernel.org, peterz@infradead.org,
stefan.bader@canonical.com, tim.gardner@canonical.com,
roxana.nicolescu@canonical.com, cascardo@canonical.com,
mikelley@microsoft.com, jgross@suse.com,
sathyanarayanan.kuppuswamy@linux.intel.com,
kirill.shutemov@linux.intel.com, sashal@kernel.org,
matija.glavinic-pecotic.ext@nokia.com,
linux-hyperv@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86/mm: Print the encryption features correctly when a paravisor is present
Date: Thu, 19 Oct 2023 08:54:23 -0700 [thread overview]
Message-ID: <00ff2f75-e780-4e2d-bcc9-f441f5ef879c@intel.com> (raw)
In-Reply-To: <20231019062030.3206-1-decui@microsoft.com>
> --- 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.
next prev parent reply other threads:[~2023-10-19 15:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-19 6:20 [PATCH] x86/mm: Print the encryption features correctly when a paravisor is present Dexuan Cui
2023-10-19 15:54 ` Dave Hansen [this message]
2023-10-20 6:01 ` Dexuan Cui
2023-10-20 18:39 ` Dave Hansen
2023-10-20 20:00 ` Dexuan Cui
2023-10-20 20:13 ` Dave Hansen
2023-10-20 20:20 ` Dexuan Cui
2023-10-20 20:21 ` Borislav Petkov
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=00ff2f75-e780-4e2d-bcc9-f441f5ef879c@intel.com \
--to=dave.hansen@intel.com \
--cc=bp@alien8.de \
--cc=cascardo@canonical.com \
--cc=dave.hansen@linux.intel.com \
--cc=decui@microsoft.com \
--cc=haiyangz@microsoft.com \
--cc=hpa@zytor.com \
--cc=jgross@suse.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=kys@microsoft.com \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=matija.glavinic-pecotic.ext@nokia.com \
--cc=mikelley@microsoft.com \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=roxana.nicolescu@canonical.com \
--cc=sashal@kernel.org \
--cc=sathyanarayanan.kuppuswamy@linux.intel.com \
--cc=stefan.bader@canonical.com \
--cc=tglx@linutronix.de \
--cc=tim.gardner@canonical.com \
--cc=wei.liu@kernel.org \
--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