From: "Huang, Kai" <kai.huang@intel.com>
To: "kirill.shutemov@linux.intel.com"
<kirill.shutemov@linux.intel.com>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"mingo@redhat.com" <mingo@redhat.com>,
"Hansen, Dave" <dave.hansen@intel.com>,
"bp@alien8.de" <bp@alien8.de>
Cc: "Cui, Dexuan" <decui@microsoft.com>, "Christopherson,,
Sean" <seanjc@google.com>, "x86@kernel.org" <x86@kernel.org>,
"Edgecombe, Rick P" <rick.p.edgecombe@intel.com>,
"sathyanarayanan.kuppuswamy@linux.intel.com"
<sathyanarayanan.kuppuswamy@linux.intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"thomas.lendacky@amd.com" <thomas.lendacky@amd.com>,
"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: [PATCH 1/2] x86/mm: Allow guest.enc_status_change_prepare() to fail
Date: Fri, 26 May 2023 02:17:12 +0000 [thread overview]
Message-ID: <7e243a32436c1ef68f0fb191c098ba9b3fad30d1.camel@intel.com> (raw)
In-Reply-To: <20230525225847.28592-2-kirill.shutemov@linux.intel.com>
On Fri, 2023-05-26 at 01:58 +0300, Kirill A. Shutemov wrote:
> TDX code is going to provide guest.enc_status_change_prepare() that is
> able to fail.
>
> Add a way to return an error from the callback.
>
> While there, fix enc_status_change_finish_noop(). It is defined as
> always-fail now which doesn't make sense for noop.
>
> Signed-off-by: Kirill A. Shutemov <kirill.shutemov@linux.intel.com>
> Cc: stable@vger.kernel.org
> ---
> arch/x86/include/asm/x86_init.h | 2 +-
> arch/x86/kernel/x86_init.c | 4 ++--
> arch/x86/mm/mem_encrypt_amd.c | 4 +++-
> arch/x86/mm/pat/set_memory.c | 3 ++-
> 4 files changed, 8 insertions(+), 5 deletions(-)
>
> diff --git a/arch/x86/include/asm/x86_init.h b/arch/x86/include/asm/x86_init.h
> index 88085f369ff6..1ca9701917c5 100644
> --- a/arch/x86/include/asm/x86_init.h
> +++ b/arch/x86/include/asm/x86_init.h
> @@ -150,7 +150,7 @@ struct x86_init_acpi {
> * @enc_cache_flush_required Returns true if a cache flush is needed before changing page encryption status
> */
> struct x86_guest {
> - void (*enc_status_change_prepare)(unsigned long vaddr, int npages, bool enc);
> + bool (*enc_status_change_prepare)(unsigned long vaddr, int npages, bool enc);
>
[...]
> @@ -2151,7 +2151,8 @@ static int __set_memory_enc_pgtable(unsigned long addr, int numpages, bool enc)
> cpa_flush(&cpa, x86_platform.guest.enc_cache_flush_required());
>
> /* Notify hypervisor that we are about to set/clr encryption attribute. */
> - x86_platform.guest.enc_status_change_prepare(addr, numpages, enc);
> + if (!x86_platform.guest.enc_status_change_prepare(addr, numpages, enc))
> + return -EIO;
The name "enc_status_change_prepare()" sounds like an action, but not some
true/false condition check. I think it's more reasonable to make it return
'int', and returning 0 means successful?
next prev parent reply other threads:[~2023-05-26 2:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-25 22:58 [PATCH 0/2] x86/tdx: Fix one more load_unaligned_zeropad() issue Kirill A. Shutemov
2023-05-25 22:58 ` [PATCH 1/2] x86/mm: Allow guest.enc_status_change_prepare() to fail Kirill A. Shutemov
2023-05-25 23:28 ` Sathyanarayanan Kuppuswamy
2023-05-26 2:17 ` Huang, Kai [this message]
2023-05-26 11:49 ` kirill.shutemov
2023-05-25 22:58 ` [PATCH 2/2] x86/tdx: Fix race between set_memory_encrypted() and load_unaligned_zeropad() Kirill A. Shutemov
2023-05-25 23:40 ` Sathyanarayanan Kuppuswamy
2023-05-26 11:54 ` Kirill A. Shutemov
2023-05-26 2:35 ` [PATCH 0/2] x86/tdx: Fix one more load_unaligned_zeropad() issue Dexuan Cui
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=7e243a32436c1ef68f0fb191c098ba9b3fad30d1.camel@intel.com \
--to=kai.huang@intel.com \
--cc=bp@alien8.de \
--cc=dave.hansen@intel.com \
--cc=decui@microsoft.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rick.p.edgecombe@intel.com \
--cc=sathyanarayanan.kuppuswamy@linux.intel.com \
--cc=seanjc@google.com \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=thomas.lendacky@amd.com \
--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