From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by smtp.lore.kernel.org (Postfix) with ESMTP id 9F02EC433EF for ; Tue, 29 Mar 2022 19:13:08 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id F216F8D0002; Tue, 29 Mar 2022 15:13:07 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id ED14E8D0001; Tue, 29 Mar 2022 15:13:07 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id D4B6E8D0002; Tue, 29 Mar 2022 15:13:07 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from forelay.hostedemail.com (smtprelay0195.hostedemail.com [216.40.44.195]) by kanga.kvack.org (Postfix) with ESMTP id C1BF78D0001 for ; Tue, 29 Mar 2022 15:13:07 -0400 (EDT) Received: from smtpin31.hostedemail.com (10.5.19.251.rfc1918.com [10.5.19.251]) by forelay05.hostedemail.com (Postfix) with ESMTP id 7C1A01828ECBF for ; Tue, 29 Mar 2022 19:13:07 +0000 (UTC) X-FDA: 79298371614.31.D37836C Received: from mail-pf1-f178.google.com (mail-pf1-f178.google.com [209.85.210.178]) by imf17.hostedemail.com (Postfix) with ESMTP id F273E4001B for ; Tue, 29 Mar 2022 19:13:06 +0000 (UTC) Received: by mail-pf1-f178.google.com with SMTP id f3so15507035pfe.2 for ; Tue, 29 Mar 2022 12:13:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20210112; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to; bh=1sRXKTYViBqnNTxehrfiPd1DYbEATFyG4C7S2pQ8qtk=; b=pc8wAJj+CGPClFtc4+6SxMMF/hTDKxwPn6EK6m+9FfRx27Qyy31qCAugysYpXwlHiK a0kUGxK6Xfyusctttk3qEf0tK6tcNRZVC0ueQWru0qGnf/xQLnN9yB4UEhBh55GBLxLt cFjVzP27q2Jbjet5ZlPU3AzKv8YUQVETYTNGVpsh9BLXbZGgX7Laxe7Wbsh1pkzmNQd5 RT1DHO3tEEfJFNloe7cH+mP9GhmOEje2wvBrJ7X8qHIVfsdTFM8N3zeTBWAQPouP/7Qc E+5bWo7OtgVpxMuq7z9X5OGWkMU+uUppgPyk83J8z1ADfUaMuhzNtfpxuM8aS7z8GBcU BCkA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=1sRXKTYViBqnNTxehrfiPd1DYbEATFyG4C7S2pQ8qtk=; b=SAUFreX0qbnTKi3Uooo4RukVMtnyc4iPCgI6Q7ihIexc07krTKKJ/1Y+hCJnxU0mcC TIaO/M5mpVD8V0l+m73HKRwHBz+GQw9B64vbcg1JhT9Uun92FGz6aogeP+1IZsy14qYY 9J3ehGbbA50dgVYupwz2/pSbNep9skcJ/xKIrQB1IgiItiOlqemWDZMBdA2JHNBPMRbT Xx9pd3QeROE4KIkNi92FT1vF9yzMiBisp1IeCT6bnmBMGrh5yUr+mlpYQsWqbgkdwEej 477GBKgHqwNZAPfSctiyA00vwTKki7mbEbqmbzwzI2ptKhFAATevdNx7uyIEe9o2Uiy3 NEpg== X-Gm-Message-State: AOAM5309A50MpWPxHOfAUpTi0iHWF1J+mHB0iKHm/te9z3wamFoKympm EXk4KRpzqJL0tLP1fyyoXWYg3w== X-Google-Smtp-Source: ABdhPJyYp/V6OUPnq1zyxa80O7VCUFqnzL/BqLshFvCAlq+hazZ3NircvxGibV5N8Gx554xqH7ZZkA== X-Received: by 2002:a05:6a00:1c95:b0:4fa:81f5:b9d4 with SMTP id y21-20020a056a001c9500b004fa81f5b9d4mr7825994pfw.49.1648581185482; Tue, 29 Mar 2022 12:13:05 -0700 (PDT) Received: from google.com (157.214.185.35.bc.googleusercontent.com. [35.185.214.157]) by smtp.gmail.com with ESMTPSA id r11-20020a17090b050b00b001c741fd4890sm3627743pjz.9.2022.03.29.12.13.04 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 29 Mar 2022 12:13:04 -0700 (PDT) Date: Tue, 29 Mar 2022 19:13:00 +0000 From: Sean Christopherson To: Chao Peng Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org, linux-mm@kvack.org, linux-fsdevel@vger.kernel.org, linux-api@vger.kernel.org, qemu-devel@nongnu.org, Paolo Bonzini , Jonathan Corbet , Vitaly Kuznetsov , Wanpeng Li , Jim Mattson , Joerg Roedel , Thomas Gleixner , Ingo Molnar , Borislav Petkov , x86@kernel.org, "H . Peter Anvin" , Hugh Dickins , Jeff Layton , "J . Bruce Fields" , Andrew Morton , Mike Rapoport , Steven Price , "Maciej S . Szmigiero" , Vlastimil Babka , Vishal Annapurve , Yu Zhang , "Kirill A . Shutemov" , luto@kernel.org, jun.nakajima@intel.com, dave.hansen@intel.com, ak@linux.intel.com, david@redhat.com Subject: Re: [PATCH v5 12/13] KVM: Expose KVM_MEM_PRIVATE Message-ID: References: <20220310140911.50924-1-chao.p.peng@linux.intel.com> <20220310140911.50924-13-chao.p.peng@linux.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20220310140911.50924-13-chao.p.peng@linux.intel.com> X-Stat-Signature: 4yu533fttce6iak6ksob8qik47k3icm9 Authentication-Results: imf17.hostedemail.com; dkim=pass header.d=google.com header.s=20210112 header.b=pc8wAJj+; dmarc=pass (policy=reject) header.from=google.com; spf=pass (imf17.hostedemail.com: domain of seanjc@google.com designates 209.85.210.178 as permitted sender) smtp.mailfrom=seanjc@google.com X-Rspam-User: X-Rspamd-Server: rspam11 X-Rspamd-Queue-Id: F273E4001B X-HE-Tag: 1648581186-127553 X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: On Thu, Mar 10, 2022, Chao Peng wrote: > KVM_MEM_PRIVATE is not exposed by default but architecture code can turn > on it by implementing kvm_arch_private_memory_supported(). > > Signed-off-by: Yu Zhang > Signed-off-by: Chao Peng > --- > include/linux/kvm_host.h | 1 + > virt/kvm/kvm_main.c | 24 +++++++++++++++++++----- > 2 files changed, 20 insertions(+), 5 deletions(-) > > diff --git a/include/linux/kvm_host.h b/include/linux/kvm_host.h > index 186b9b981a65..0150e952a131 100644 > --- a/include/linux/kvm_host.h > +++ b/include/linux/kvm_host.h > @@ -1432,6 +1432,7 @@ bool kvm_arch_dy_has_pending_interrupt(struct kvm_vcpu *vcpu); > int kvm_arch_post_init_vm(struct kvm *kvm); > void kvm_arch_pre_destroy_vm(struct kvm *kvm); > int kvm_arch_create_vm_debugfs(struct kvm *kvm); > +bool kvm_arch_private_memory_supported(struct kvm *kvm); > > #ifndef __KVM_HAVE_ARCH_VM_ALLOC > /* > diff --git a/virt/kvm/kvm_main.c b/virt/kvm/kvm_main.c > index 52319f49d58a..df5311755a40 100644 > --- a/virt/kvm/kvm_main.c > +++ b/virt/kvm/kvm_main.c > @@ -1485,10 +1485,19 @@ static void kvm_replace_memslot(struct kvm *kvm, > } > } > > -static int check_memory_region_flags(const struct kvm_userspace_memory_region *mem) > +bool __weak kvm_arch_private_memory_supported(struct kvm *kvm) > +{ > + return false; > +} > + > +static int check_memory_region_flags(struct kvm *kvm, > + const struct kvm_userspace_memory_region *mem) > { > u32 valid_flags = KVM_MEM_LOG_DIRTY_PAGES; > > + if (kvm_arch_private_memory_supported(kvm)) > + valid_flags |= KVM_MEM_PRIVATE; > + > #ifdef __KVM_HAVE_READONLY_MEM > valid_flags |= KVM_MEM_READONLY; > #endif > @@ -1900,7 +1909,7 @@ int __kvm_set_memory_region(struct kvm *kvm, > int as_id, id; > int r; > > - r = check_memory_region_flags(mem); > + r = check_memory_region_flags(kvm, mem); > if (r) > return r; > > @@ -1913,10 +1922,12 @@ int __kvm_set_memory_region(struct kvm *kvm, > return -EINVAL; > if (mem->guest_phys_addr & (PAGE_SIZE - 1)) > return -EINVAL; > - /* We can read the guest memory with __xxx_user() later on. */ > if ((mem->userspace_addr & (PAGE_SIZE - 1)) || > - (mem->userspace_addr != untagged_addr(mem->userspace_addr)) || > - !access_ok((void __user *)(unsigned long)mem->userspace_addr, > + (mem->userspace_addr != untagged_addr(mem->userspace_addr))) > + return -EINVAL; > + /* We can read the guest memory with __xxx_user() later on. */ > + if (!(mem->flags & KVM_MEM_PRIVATE) && > + !access_ok((void __user *)(unsigned long)mem->userspace_addr, This should sanity check private_offset for private memslots. At a bare minimum, wrapping should be disallowed. > mem->memory_size)) > return -EINVAL; > if (as_id >= KVM_ADDRESS_SPACE_NUM || id >= KVM_MEM_SLOTS_NUM) > @@ -1957,6 +1968,9 @@ int __kvm_set_memory_region(struct kvm *kvm, > if ((kvm->nr_memslot_pages + npages) < kvm->nr_memslot_pages) > return -EINVAL; > } else { /* Modify an existing slot. */ > + /* Private memslots are immutable, they can only be deleted. */ > + if (mem->flags & KVM_MEM_PRIVATE) > + return -EINVAL; These sanity checks belong in "KVM: Register private memslot to memory backing store", e.g. that patch is "broken" without the immutability restriction. It's somewhat moot because the code is unreachable, but it makes reviewing confusing/difficult. But rather than move the sanity checks back, I think I'd prefer to pull all of patch 10 here. I think it also makes sense to drop "KVM: Use memfile_pfn_ops to obtain pfn for private pages" and add the pointer in "struct kvm_memory_slot" in patch "KVM: Extend the memslot to support fd-based private memory", with the use of the ops folded into "KVM: Handle page fault for private memory". Adding code to KVM and KVM-x86 in a single patch is ok, and overall makes things easier to review because the new helpers have a user right away, especially since there will be #ifdeffery. I.e. end up with something like: mm: Introduce memfile_notifier mm/shmem: Restrict MFD_INACCESSIBLE memory against RLIMIT_MEMLOCK KVM: Extend the memslot to support fd-based private memory KVM: Use kvm_userspace_memory_region_ext KVM: Add KVM_EXIT_MEMORY_ERROR exit KVM: Handle page fault for private memory KVM: Register private memslot to memory backing store KVM: Zap existing KVM mappings when pages changed in the private fd KVM: Enable and expose KVM_MEM_PRIVATE > if ((mem->userspace_addr != old->userspace_addr) || > (npages != old->npages) || > ((mem->flags ^ old->flags) & KVM_MEM_READONLY)) > -- > 2.17.1 >