From: Dave Hansen <dave.hansen@intel.com>
To: "Michael Kelley (LINUX)" <mikelley@microsoft.com>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"mingo@redhat.com" <mingo@redhat.com>,
"bp@alien8.de" <bp@alien8.de>
Cc: Dexuan Cui <decui@microsoft.com>,
"rick.p.edgecombe@intel.com" <rick.p.edgecombe@intel.com>,
"sathyanarayanan.kuppuswamy@linux.intel.com"
<sathyanarayanan.kuppuswamy@linux.intel.com>,
"seanjc@google.com" <seanjc@google.com>,
"thomas.lendacky@amd.com" <thomas.lendacky@amd.com>,
"x86@kernel.org" <x86@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCHv3 0/3] x86/tdx: Fix one more load_unaligned_zeropad() issue
Date: Thu, 6 Jul 2023 10:45:25 -0700 [thread overview]
Message-ID: <c32e45ed-da25-a7c7-2613-5c94ea89cc27@intel.com> (raw)
In-Reply-To: <BYAPR21MB168846628450D6089242D3EAD72CA@BYAPR21MB1688.namprd21.prod.outlook.com>
On 7/6/23 09:48, Michael Kelley (LINUX) wrote:
> When a page is transitioning, the caller can and should ensure
> that it is not being accessed during the transition. But we have
> the load_unaligned_zeropad() wildcard. So do the following for
> the transition sequence in __set_memory_enc_pgtable():
>
> 1. Remove aliasing mappings
> 2. Remove the PRESENT bit from the PTEs of all transitioning pages
> 3. Flush the TLB globally
> 4. Flush the data cache if needed
> 5. Set/clear the encryption attribute as appropriate
> 6. Notify the hypervisor of the page status change
> 7. Add back the PRESENT bit
>
> With this approach, load_unaligned_zeropad() just takes the
> normal page-fault-based fixup path if it touches a page that is
> transitioning.
Yes, this does seem much simpler. It funnels everything through the
page fault handler and also doesn't require because careful about the
ordering of the private<=>shared conversions.
next prev parent reply other threads:[~2023-07-06 17:45 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-06 9:56 Kirill A. Shutemov
2023-06-06 9:56 ` [PATCHv3 1/3] x86/mm: Allow guest.enc_status_change_prepare() to fail Kirill A. Shutemov
2023-06-06 9:56 ` [PATCHv3 2/3] x86/tdx: Fix race between set_memory_encrypted() and load_unaligned_zeropad() Kirill A. Shutemov
2023-06-06 18:14 ` Dave Hansen
2023-06-06 18:37 ` Kirill A. Shutemov
2023-06-06 23:29 ` Dave Hansen
2023-06-07 11:16 ` Kirill A. Shutemov
2023-06-06 9:56 ` [PATCHv3 3/3] x86/mm: Fix enc_status_change_finish_noop() Kirill A. Shutemov
2023-07-06 16:48 ` [PATCHv3 0/3] x86/tdx: Fix one more load_unaligned_zeropad() issue Michael Kelley (LINUX)
2023-07-06 17:45 ` Dave Hansen [this message]
2023-07-07 14:06 ` Kirill A. Shutemov
2023-07-08 23:53 ` Michael Kelley (LINUX)
2023-07-09 6:09 ` Kirill A. Shutemov
2023-07-10 13:59 ` Tom Lendacky
2023-07-10 14:17 ` Michael Kelley (LINUX)
2023-07-13 14:43 ` Michael Kelley (LINUX)
2023-07-24 23:19 ` Kirill A. Shutemov
2023-07-25 15:51 ` Michael Kelley (LINUX)
2023-07-25 23:12 ` Kirill A. Shutemov
2023-07-26 3:15 ` Michael Kelley (LINUX)
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=c32e45ed-da25-a7c7-2613-5c94ea89cc27@intel.com \
--to=dave.hansen@intel.com \
--cc=bp@alien8.de \
--cc=decui@microsoft.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mikelley@microsoft.com \
--cc=mingo@redhat.com \
--cc=rick.p.edgecombe@intel.com \
--cc=sathyanarayanan.kuppuswamy@linux.intel.com \
--cc=seanjc@google.com \
--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
all inboxes | Powered by JetHome®