From: Brijesh Singh <brijesh.singh@amd.com>
To: Dave Hansen <dave.hansen@intel.com>,
x86@kernel.org, linux-kernel@vger.kernel.org,
kvm@vger.kernel.org, linux-efi@vger.kernel.org,
platform-driver-x86@vger.kernel.org, linux-coco@lists.linux.dev,
linux-mm@kvack.org, linux-crypto@vger.kernel.org
Cc: brijesh.singh@amd.com, Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Joerg Roedel <jroedel@suse.de>,
Tom Lendacky <thomas.lendacky@amd.com>,
"H. Peter Anvin" <hpa@zytor.com>,
Ard Biesheuvel <ardb@kernel.org>,
Paolo Bonzini <pbonzini@redhat.com>,
Sean Christopherson <seanjc@google.com>,
Vitaly Kuznetsov <vkuznets@redhat.com>,
Wanpeng Li <wanpengli@tencent.com>,
Jim Mattson <jmattson@google.com>,
Andy Lutomirski <luto@kernel.org>,
Dave Hansen <dave.hansen@linux.intel.com>,
Sergio Lopez <slp@redhat.com>, Peter Gonda <pgonda@google.com>,
Peter Zijlstra <peterz@infradead.org>,
Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>,
David Rientjes <rientjes@google.com>,
Dov Murik <dovmurik@linux.ibm.com>,
Tobin Feldman-Fitzthum <tobin@ibm.com>,
Borislav Petkov <bp@alien8.de>,
Michael Roth <michael.roth@amd.com>,
Vlastimil Babka <vbabka@suse.cz>,
tony.luck@intel.com, npmccallum@redhat.com,
brijesh.ksingh@gmail.com
Subject: Re: [PATCH Part2 RFC v4 10/40] x86/fault: Add support to handle the RMP fault for user address
Date: Mon, 12 Jul 2021 10:43:50 -0500 [thread overview]
Message-ID: <2b4accb6-b68e-02d3-6fed-975f90558099@amd.com> (raw)
In-Reply-To: <3c6b6fc4-05b2-8d18-2eb8-1bd1a965c632@intel.com>
Hi Dave,
On 7/8/21 11:16 AM, Dave Hansen wrote:
>
> "SIGBUG"?
Its typo, it should be SIGBUS
>> +
>> + if (unlikely(!cpu_feature_enabled(X86_FEATURE_SEV_SNP)))
>> + return RMP_FAULT_KILL;
>
> Shouldn't this be a WARN_ON_ONCE()? How can we get RMP faults without
> SEV-SNP?
Yes, we should *not* get RMP fault if SEV-SNP is not enabled. I can use
the WARN_ON_ONCE().
>
>> + /* Get the native page level */
>> + pte = lookup_address_in_mm(current->mm, address, &level);
>> + if (unlikely(!pte))
>> + return RMP_FAULT_KILL;
>
> What would this mean? There was an RMP fault on a non-present page?
> How could that happen? What if there was a race between an unmapping
> event and the RMP fault delivery?
We should not have RMP fault for non-present pages. But you have a good
point that there maybe a race between the unmap event and RMP fault.
Instead of terminating the process we should simply retry.
>
>> + pfn = pte_pfn(*pte);
>> + if (level > PG_LEVEL_4K) {
>> + mask = pages_per_hpage(level) - pages_per_hpage(level - 1);
>> + pfn |= (address >> PAGE_SHIFT) & mask;
>> + }
>
> This looks inherently racy. What happens if there are two parallel RMP
> faults on the same 2M page. One of them splits the page tables, the
> other gets a fault for an already-split page table.
> > Is that handled here somehow?
Yes, in this particular case we simply retry and hardware should
re-evaluate the page level and take the corrective action.
>
>> + /* Get the page level from the RMP entry. */
>> + e = snp_lookup_page_in_rmptable(pfn_to_page(pfn), &rmp_level);
>> + if (!e)
>> + return RMP_FAULT_KILL;
>
> The snp_lookup_page_in_rmptable() failure cases looks WARN-worthly.
> Either you're doing a lookup for something not *IN* the RMP table, or
> you don't support SEV-SNP, in which case you shouldn't be in this code
> in the first place.
Noted.
>
>> + /*
>> + * Check if the RMP violation is due to the guest private page access.
>> + * We can not resolve this RMP fault, ask to kill the guest.
>> + */
>> + if (rmpentry_assigned(e))
>> + return RMP_FAULT_KILL;
>
> No "We's", please. Speak in imperative voice.
Noted.
>
>> + /*
>> + * The backing page level is higher than the RMP page level, request
>> + * to split the page.
>> + */
>> + if (level > rmp_level)
>> + return RMP_FAULT_PAGE_SPLIT;
>
> This can theoretically trigger on a hugetlbfs page. Right?
>
Yes, theoretically.
In the current implementation, the VMM is enlightened to not use the
hugetlbfs for backing page when creating the SEV-SNP guests.
> I thought I asked about this before... more below...
>
>> + return RMP_FAULT_RETRY;
>> +}
>> +
>> /*
>> * Handle faults in the user portion of the address space. Nothing in here
>> * should check X86_PF_USER without a specific justification: for almost
>> @@ -1298,6 +1350,7 @@ void do_user_addr_fault(struct pt_regs *regs,
>> struct task_struct *tsk;
>> struct mm_struct *mm;
>> vm_fault_t fault;
>> + int ret;
>> unsigned int flags = FAULT_FLAG_DEFAULT;
>>
>> tsk = current;
>> @@ -1378,6 +1431,22 @@ void
> (struct pt_regs *regs,
>> if (error_code & X86_PF_INSTR)
>> flags |= FAULT_FLAG_INSTRUCTION;
>>
>> + /*
>> + * If its an RMP violation, try resolving it.
>> + */
>> + if (error_code & X86_PF_RMP) {
>> + ret = handle_user_rmp_page_fault(error_code, address);
>> + if (ret == RMP_FAULT_PAGE_SPLIT) {
>> + flags |= FAULT_FLAG_PAGE_SPLIT;
>> + } else if (ret == RMP_FAULT_KILL) {
>> + fault |= VM_FAULT_SIGBUS;
>> + do_sigbus(regs, error_code, address, fault);
>> + return;
>> + } else {
>> + return;
>> + }
>> + }
>
> Why not just have handle_user_rmp_page_fault() return a VM_FAULT_* code
> directly?
>
I don't have any strong reason against it. In next rev, I can update to
use the VM_FAULT_* code and call the do_sigbus() etc.
> I also suspect you can just set VM_FAULT_SIGBUS and let the do_sigbus()
> call later on in the function do its work.
>>
>> +static int handle_split_page_fault(struct vm_fault *vmf)
>> +{
>> + if (!IS_ENABLED(CONFIG_AMD_MEM_ENCRYPT))
>> + return VM_FAULT_SIGBUS;
>> +
>> + __split_huge_pmd(vmf->vma, vmf->pmd, vmf->address, false, NULL);
>> + return 0;
>> +}
>
> What will this do when you hand it a hugetlbfs page?
>
VMM is updated to not use the hugetlbfs when creating SEV-SNP guests.
So, we should not run into it.
-Brijesh
next prev parent reply other threads:[~2021-07-12 15:43 UTC|newest]
Thread overview: 178+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-07 18:35 [PATCH Part2 RFC v4 00/40] Add AMD Secure Nested Paging (SEV-SNP) Hypervisor Support Brijesh Singh
2021-07-07 18:35 ` [PATCH Part2 RFC v4 01/40] KVM: SVM: Add support to handle AP reset MSR protocol Brijesh Singh
2021-07-14 20:17 ` Sean Christopherson
2021-07-15 7:39 ` Joerg Roedel
2021-07-15 13:42 ` Tom Lendacky
2021-07-15 15:45 ` Sean Christopherson
2021-07-15 17:05 ` Tom Lendacky
2021-07-07 18:35 ` [PATCH Part2 RFC v4 02/40] KVM: SVM: Provide the Hypervisor Feature support VMGEXIT Brijesh Singh
2021-07-14 20:37 ` Sean Christopherson
2021-07-14 21:00 ` Brijesh Singh
2021-07-07 18:35 ` [PATCH Part2 RFC v4 03/40] x86/cpufeatures: Add SEV-SNP CPU feature Brijesh Singh
2021-07-07 18:35 ` [PATCH Part2 RFC v4 04/40] x86/sev: Add the host SEV-SNP initialization support Brijesh Singh
2021-07-14 21:07 ` Sean Christopherson
2021-07-14 22:02 ` Brijesh Singh
2021-07-14 22:06 ` Sean Christopherson
2021-07-14 22:11 ` Brijesh Singh
2022-06-02 11:47 ` Jarkko Sakkinen
2022-06-06 11:42 ` Dr. David Alan Gilbert
2021-07-07 18:35 ` [PATCH Part2 RFC v4 05/40] x86/sev: Add RMP entry lookup helpers Brijesh Singh
2021-07-15 18:37 ` Sean Christopherson
2021-07-15 19:28 ` Brijesh Singh
2021-07-16 17:22 ` Brijesh Singh
2021-07-20 22:06 ` Sean Christopherson
2021-07-20 23:10 ` Brijesh Singh
2021-07-07 18:35 ` [PATCH Part2 RFC v4 06/40] x86/sev: Add helper functions for RMPUPDATE and PSMASH instruction Brijesh Singh
2021-07-12 18:44 ` Peter Gonda
2021-07-12 19:00 ` Dave Hansen
2021-07-15 18:56 ` Sean Christopherson
2021-07-15 19:08 ` Dave Hansen
2021-07-15 19:18 ` Sean Christopherson
2021-07-07 18:35 ` [PATCH Part2 RFC v4 07/40] x86/sev: Split the physmap when adding the page in RMP table Brijesh Singh
2021-07-14 22:25 ` Sean Christopherson
2021-07-15 17:05 ` Brijesh Singh
2021-07-15 17:51 ` Sean Christopherson
2021-07-15 18:14 ` Brijesh Singh
2021-07-15 18:39 ` Sean Christopherson
2021-07-15 19:38 ` Brijesh Singh
2021-07-15 22:01 ` Sean Christopherson
2021-07-15 22:11 ` Brijesh Singh
2021-07-30 11:31 ` Vlastimil Babka
2021-07-30 16:10 ` Brijesh Singh
2021-07-07 18:35 ` [PATCH Part2 RFC v4 08/40] x86/traps: Define RMP violation #PF error code Brijesh Singh
2021-07-15 19:02 ` Sean Christopherson
2021-07-15 19:16 ` Dave Hansen
2021-07-07 18:35 ` [PATCH Part2 RFC v4 09/40] x86/fault: Add support to dump RMP entry on fault Brijesh Singh
2021-07-07 19:21 ` Dave Hansen
2021-07-08 15:02 ` Brijesh Singh
2021-07-08 15:30 ` Dave Hansen
2021-07-08 16:48 ` Brijesh Singh
2021-07-08 16:58 ` Dave Hansen
2021-07-08 17:11 ` Brijesh Singh
2021-07-08 17:15 ` Dave Hansen
2021-07-07 18:35 ` [PATCH Part2 RFC v4 10/40] x86/fault: Add support to handle the RMP fault for user address Brijesh Singh
2021-07-08 16:16 ` Dave Hansen
2021-07-12 15:43 ` Brijesh Singh [this message]
2021-07-12 16:00 ` Dave Hansen
2021-07-12 16:11 ` Brijesh Singh
2021-07-12 16:15 ` Dave Hansen
2021-07-12 16:24 ` Brijesh Singh
2021-07-12 16:29 ` Dave Hansen
2021-07-12 16:49 ` Brijesh Singh
2021-07-15 21:53 ` Sean Christopherson
2021-07-30 16:00 ` Vlastimil Babka
2021-07-30 16:31 ` Dave Hansen
2021-07-07 18:35 ` [PATCH Part2 RFC v4 11/40] crypto:ccp: Define the SEV-SNP commands Brijesh Singh
2021-07-07 18:35 ` [PATCH Part2 RFC v4 12/40] crypto: ccp: Add support to initialize the AMD-SP for SEV-SNP Brijesh Singh
2021-07-07 18:35 ` [PATCH Part2 RFC v4 13/40] crypto: ccp: Shutdown SNP firmware on kexec Brijesh Singh
2021-07-07 18:35 ` [PATCH Part2 RFC v4 14/40] crypto:ccp: Provide APIs to issue SEV-SNP commands Brijesh Singh
2021-07-08 18:56 ` Dr. David Alan Gilbert
2021-07-07 18:35 ` [PATCH Part2 RFC v4 15/40] crypto: ccp: Handle the legacy TMR allocation when SNP is enabled Brijesh Singh
2021-07-14 13:22 ` Marc Orr
2021-07-14 16:45 ` Brijesh Singh
2021-07-14 18:14 ` Marc Orr
2021-07-15 23:48 ` Sean Christopherson
2021-07-16 12:55 ` Brijesh Singh
2021-07-16 15:35 ` Sean Christopherson
2021-07-16 15:47 ` Brijesh Singh
2021-07-07 18:35 ` [PATCH Part2 RFC v4 16/40] crypto: ccp: Handle the legacy SEV command " Brijesh Singh
2021-07-07 18:35 ` [PATCH Part2 RFC v4 17/40] crypto: ccp: Add the SNP_PLATFORM_STATUS command Brijesh Singh
2021-07-07 18:35 ` [PATCH Part2 RFC v4 18/40] crypto: ccp: Add the SNP_{SET,GET}_EXT_CONFIG command Brijesh Singh
2021-07-07 18:35 ` [PATCH Part2 RFC v4 19/40] crypto: ccp: provide APIs to query extended attestation report Brijesh Singh
2021-07-07 18:35 ` [PATCH Part2 RFC v4 20/40] KVM: SVM: Make AVIC backing, VMSA and VMCB memory allocation SNP safe Brijesh Singh
2021-07-14 13:35 ` Marc Orr
2021-07-14 16:47 ` Brijesh Singh
2021-07-20 18:02 ` Sean Christopherson
2021-08-03 14:38 ` Brijesh Singh
2021-07-07 18:35 ` [PATCH Part2 RFC v4 21/40] KVM: SVM: Add initial SEV-SNP support Brijesh Singh
2021-07-16 18:00 ` Sean Christopherson
2021-07-16 18:46 ` Brijesh Singh
2021-07-16 19:31 ` Sean Christopherson
2021-07-16 21:03 ` Brijesh Singh
2021-07-07 18:35 ` [PATCH Part2 RFC v4 22/40] KVM: SVM: Add KVM_SNP_INIT command Brijesh Singh
2021-07-16 19:33 ` Sean Christopherson
2021-07-16 21:25 ` Brijesh Singh
2021-07-19 20:24 ` Sean Christopherson
2021-07-07 18:35 ` [PATCH Part2 RFC v4 23/40] KVM: SVM: Add KVM_SEV_SNP_LAUNCH_START command Brijesh Singh
2021-07-12 18:45 ` Peter Gonda
2021-07-16 19:43 ` Sean Christopherson
2021-07-16 21:42 ` Brijesh Singh
2021-07-07 18:36 ` [PATCH Part2 RFC v4 24/40] KVM: SVM: Add KVM_SEV_SNP_LAUNCH_UPDATE command Brijesh Singh
2021-07-16 20:01 ` Sean Christopherson
2021-07-16 22:00 ` Brijesh Singh
2021-07-19 20:51 ` Sean Christopherson
2021-07-19 21:34 ` Brijesh Singh
2021-07-19 21:36 ` Brijesh Singh
2021-07-07 18:36 ` [PATCH Part2 RFC v4 25/40] KVM: SVM: Reclaim the guest pages when SEV-SNP VM terminates Brijesh Singh
2021-07-16 20:09 ` Sean Christopherson
2021-07-16 22:16 ` Brijesh Singh
2021-07-17 0:46 ` Sean Christopherson
2021-07-19 12:55 ` Brijesh Singh
2021-07-19 17:18 ` Sean Christopherson
2021-07-19 18:34 ` Brijesh Singh
2021-07-19 19:03 ` Sean Christopherson
2021-07-19 19:14 ` Sean Christopherson
2021-07-19 19:37 ` Brijesh Singh
2021-07-20 16:40 ` Sean Christopherson
2021-07-20 18:23 ` Brijesh Singh
2021-07-07 18:36 ` [PATCH Part2 RFC v4 26/40] KVM: SVM: Add KVM_SEV_SNP_LAUNCH_FINISH command Brijesh Singh
2021-07-16 20:18 ` Sean Christopherson
2021-07-16 22:48 ` Brijesh Singh
2021-07-19 16:54 ` Sean Christopherson
2021-07-19 18:29 ` Brijesh Singh
2021-07-19 19:14 ` Sean Christopherson
2021-07-19 19:49 ` Brijesh Singh
2021-07-19 20:13 ` Sean Christopherson
2021-07-21 17:53 ` Marc Orr
2021-07-07 18:36 ` [PATCH Part2 RFC v4 27/40] KVM: X86: Add kvm_x86_ops to get the max page level for the TDP Brijesh Singh
2021-07-16 19:19 ` Sean Christopherson
2021-07-16 20:41 ` Brijesh Singh
2021-07-20 19:38 ` Sean Christopherson
2021-07-20 20:06 ` Brijesh Singh
2021-07-07 18:36 ` [PATCH Part2 RFC v4 28/40] KVM: X86: Introduce kvm_mmu_map_tdp_page() for use by SEV Brijesh Singh
2021-07-16 18:15 ` Sean Christopherson
2021-07-07 18:36 ` [PATCH Part2 RFC v4 29/40] KVM: X86: Introduce kvm_mmu_get_tdp_walk() for SEV-SNP use Brijesh Singh
2021-07-07 18:36 ` [PATCH Part2 RFC v4 30/40] KVM: X86: Define new RMP check related #NPF error bits Brijesh Singh
2021-07-16 20:22 ` Sean Christopherson
2021-07-17 0:34 ` Brijesh Singh
2021-07-07 18:36 ` [PATCH Part2 RFC v4 31/40] KVM: X86: update page-fault trace to log the 64-bit error code Brijesh Singh
2021-07-16 20:25 ` Sean Christopherson
2021-07-17 0:35 ` Brijesh Singh
2021-07-07 18:36 ` [PATCH Part2 RFC v4 32/40] KVM: SVM: Add support to handle GHCB GPA register VMGEXIT Brijesh Singh
2021-07-16 20:45 ` Sean Christopherson
2021-07-17 0:44 ` Brijesh Singh
2021-07-19 20:04 ` Sean Christopherson
2021-07-07 18:36 ` [PATCH Part2 RFC v4 33/40] KVM: SVM: Add support to handle MSR based Page State Change VMGEXIT Brijesh Singh
2021-07-16 21:00 ` Sean Christopherson
2021-07-19 14:19 ` Brijesh Singh
2021-07-19 18:55 ` Sean Christopherson
2021-07-19 19:15 ` Brijesh Singh
2021-08-13 16:32 ` Borislav Petkov
2021-07-07 18:36 ` [PATCH Part2 RFC v4 34/40] KVM: SVM: Add support to handle " Brijesh Singh
2021-07-16 21:14 ` Sean Christopherson
2021-07-19 14:24 ` Brijesh Singh
2021-07-07 18:36 ` [PATCH Part2 RFC v4 35/40] KVM: Add arch hooks to track the host write to guest memory Brijesh Singh
2021-07-19 23:30 ` Sean Christopherson
2021-07-20 15:15 ` Brijesh Singh
2021-07-07 18:36 ` [PATCH Part2 RFC v4 36/40] KVM: X86: Export the kvm_zap_gfn_range() for the SNP use Brijesh Singh
2021-07-07 18:36 ` [PATCH Part2 RFC v4 37/40] KVM: SVM: Add support to handle the RMP nested page fault Brijesh Singh
2021-07-20 0:10 ` Sean Christopherson
2021-07-20 17:55 ` Brijesh Singh
2021-07-20 22:31 ` Sean Christopherson
2021-07-20 23:53 ` Brijesh Singh
2021-07-21 20:15 ` Sean Christopherson
2021-07-07 18:36 ` [PATCH Part2 RFC v4 38/40] KVM: SVM: Provide support for SNP_GUEST_REQUEST NAE event Brijesh Singh
2021-07-19 22:50 ` Sean Christopherson
2021-07-20 14:37 ` Brijesh Singh
2021-07-20 16:28 ` Sean Christopherson
2021-07-20 18:21 ` Brijesh Singh
2021-07-20 22:09 ` Sean Christopherson
2021-07-07 18:36 ` [PATCH Part2 RFC v4 39/40] KVM: SVM: Use a VMSA physical address variable for populating VMCB Brijesh Singh
2021-07-21 0:20 ` Sean Christopherson
2021-07-21 16:26 ` Tom Lendacky
2021-07-07 18:36 ` [PATCH Part2 RFC v4 40/40] KVM: SVM: Support SEV-SNP AP Creation NAE event Brijesh Singh
2021-07-21 0:01 ` Sean Christopherson
2021-07-21 17:47 ` Tom Lendacky
2021-07-21 19:52 ` Sean Christopherson
2021-08-20 14:44 ` Tom Lendacky
2021-07-08 15:40 ` [PATCH Part2 RFC v4 00/40] Add AMD Secure Nested Paging (SEV-SNP) Hypervisor Support Dave Hansen
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=2b4accb6-b68e-02d3-6fed-975f90558099@amd.com \
--to=brijesh.singh@amd.com \
--cc=ardb@kernel.org \
--cc=bp@alien8.de \
--cc=brijesh.ksingh@gmail.com \
--cc=dave.hansen@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=dovmurik@linux.ibm.com \
--cc=hpa@zytor.com \
--cc=jmattson@google.com \
--cc=jroedel@suse.de \
--cc=kvm@vger.kernel.org \
--cc=linux-coco@lists.linux.dev \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=luto@kernel.org \
--cc=michael.roth@amd.com \
--cc=mingo@redhat.com \
--cc=npmccallum@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peterz@infradead.org \
--cc=pgonda@google.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=rientjes@google.com \
--cc=seanjc@google.com \
--cc=slp@redhat.com \
--cc=srinivas.pandruvada@linux.intel.com \
--cc=tglx@linutronix.de \
--cc=thomas.lendacky@amd.com \
--cc=tobin@ibm.com \
--cc=tony.luck@intel.com \
--cc=vbabka@suse.cz \
--cc=vkuznets@redhat.com \
--cc=wanpengli@tencent.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;
as well as URLs for NNTP newsgroup(s).