Received: by 2002:a05:6a10:22f:0:0:0:0 with SMTP id 15csp1786744pxk; Tue, 1 Sep 2020 07:48:50 -0700 (PDT) X-Google-Smtp-Source: ABdhPJytOPmFoyufrvhSx2dBed874eBBSYrkfdIxHyCzxwSAFm3Dxtd5WIZc1VC5JxhdKVDxEnvp X-Received: by 2002:a17:906:9353:: with SMTP id p19mr1720216ejw.403.1598971729826; Tue, 01 Sep 2020 07:48:49 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1598971729; cv=none; d=google.com; s=arc-20160816; b=VI4JzYj11aQHyx4YUgSg0Wt4+Q6KAC2oTcuD7X/gdOjQa+fbDHkA5anReQrsU7piax 6PZQ/26o7WvR79PKlM0Z6g3HKzjj5dXcgSSe/fh1jyJdt1QMZsq+FISXurLLEchnl6/N AlZEIJHfk9NgdU3bSQFnXKsERrnSI/KDjVv8GeX6E4ARMi3vi7e67jy3rQDNDMz0Zu73 vdcliBfH6Veaq2e/PBuDZwsSJUGGw6VNs2UEuKJEwPwvYY4g+AHyawJhihjQ2rS2DNnn Uv326TrJB2AqOHmfA0LW5BHEwbKnpcDUMjKHN7Xj9YWaXyNqpu/UhzXXO9sA1U20Ergk S83g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:message-id:date:references :in-reply-to:subject:cc:to:from:dkim-signature; bh=/DfDs0YbN/7MKpdNCaVZk0bDSA0PDgnc0VVkoK+qFXE=; b=IHT6t/tb8S31hhibDBqwac0JtFwyXLKdi3NB9jX7gvkUekLt7lemhNLVLeg4yhllQV TJlHa00KgMOOReMfLoklxuWErQmhYe0YAJ2YfZ7GLo3iWeFPPRjPhVrE1BbWahZoNxW6 QmzXU2hmkueZssc5Rlln779qfaXRF/7Yy5PbNihLlKZnU9av0HxPCZb2Taw3KhKU0P7d 4lh/IeDDuHMTBBDv0kuP9UwmgS/p9tpJy9jVBplHEOB2PbwRf0zr+FvVdfuvAWTamkRP GK39Ytidf9v0MWYe6xZ8WV+njlW6DYbBNetrhTCTvY4uD8WS+lGc4GUg+naXk4mkVqqK h/Cw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=Mpk0pMSB; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id g17si667465edw.332.2020.09.01.07.48.26; Tue, 01 Sep 2020 07:48:49 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=Mpk0pMSB; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728299AbgIAOrz (ORCPT + 99 others); Tue, 1 Sep 2020 10:47:55 -0400 Received: from us-smtp-1.mimecast.com ([205.139.110.61]:34688 "EHLO us-smtp-delivery-1.mimecast.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1727061AbgIAOPP (ORCPT ); Tue, 1 Sep 2020 10:15:15 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1598969713; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=/DfDs0YbN/7MKpdNCaVZk0bDSA0PDgnc0VVkoK+qFXE=; b=Mpk0pMSBBW9E7XBmahZvf7f4eoY+hKEHjpwKW4jmT2VAwioWMYhK7XrZaXNu4gwDTVEbVu +IIFz12Om7TVEx04zlmhi2HeZPOP9Ms2iIN3zJATEsp7LUuYdJ4V0FA/pICrPR/1wLmitS T2BFjs6SJ/JTvvpTZuJUTlHRFwbO8nQ= Received: from mail-wr1-f72.google.com (mail-wr1-f72.google.com [209.85.221.72]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-576-pfoCygoqN6mLzQJ-6v3NFA-1; Tue, 01 Sep 2020 10:15:11 -0400 X-MC-Unique: pfoCygoqN6mLzQJ-6v3NFA-1 Received: by mail-wr1-f72.google.com with SMTP id j2so641061wrr.14 for ; Tue, 01 Sep 2020 07:15:11 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:in-reply-to:references:date :message-id:mime-version; bh=/DfDs0YbN/7MKpdNCaVZk0bDSA0PDgnc0VVkoK+qFXE=; b=L8z48FTm2VbAkGBFk7FxoDljlh2N1hWH5xms6GJTdeX1mAYaZ0mRt9X0dJJMKeIZ2Z Mleqs0rLLY/D4Lwnrm28Rn+E3PnwmIREr7k+KnDkREvXwnwK4ODUD5NxdJRuXyVWapyw Te5cPV3ARMlpY88T1dCvNyxsSSUFQNmN69szTJbbcdjPJr1HLpbwBgVVpQqO+CetjNdC 7+Brghzp9tp02Yfc3M+Zgp0EzocveVBRkTmx9rfPyYXcTzRvo4KYTNPsUOUpO2OBA3AM 9KrlFcStLW+/slYxl6CLraTpD+hwABxZ0QhwGcZUIMpdS+gFm8XpRfTveiqj0fBNd2B3 N0PA== X-Gm-Message-State: AOAM532yF4OQrEh5uC5r5LdExlZ3JnNu9YvocLrbmtBRjghj+AtDLI+L Suzm8oUsI4fF+swsL8Mdc0k8pOOEfWaxSKPWC/DzHA/N0yeaOLphFBxcyYzoOG2nGlqsDy5/npL eIWH5UALzilEgSomHlySppUh0 X-Received: by 2002:a7b:cf1a:: with SMTP id l26mr1951779wmg.164.1598969709769; Tue, 01 Sep 2020 07:15:09 -0700 (PDT) X-Received: by 2002:a7b:cf1a:: with SMTP id l26mr1951735wmg.164.1598969709469; Tue, 01 Sep 2020 07:15:09 -0700 (PDT) Received: from vitty.brq.redhat.com (g-server-2.ign.cz. [91.219.240.2]) by smtp.gmail.com with ESMTPSA id w21sm2046602wmk.34.2020.09.01.07.15.07 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 01 Sep 2020 07:15:08 -0700 (PDT) From: Vitaly Kuznetsov To: Sean Christopherson Cc: kvm@vger.kernel.org, Paolo Bonzini , Wanpeng Li , Jim Mattson , Peter Xu , Michael Tsirkin , Julia Suvorova , Andy Lutomirski , Andrew Jones , linux-kernel@vger.kernel.org Subject: Re: [PATCH v2 1/3] KVM: x86: move kvm_vcpu_gfn_to_memslot() out of try_async_pf() In-Reply-To: <20200814014014.GA4845@linux.intel.com> References: <20200807141232.402895-1-vkuznets@redhat.com> <20200807141232.402895-2-vkuznets@redhat.com> <20200814014014.GA4845@linux.intel.com> Date: Tue, 01 Sep 2020 16:15:07 +0200 Message-ID: <87k0xdwplg.fsf@vitty.brq.redhat.com> MIME-Version: 1.0 Content-Type: text/plain Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Sean Christopherson writes: > On Fri, Aug 07, 2020 at 04:12:30PM +0200, Vitaly Kuznetsov wrote: >> No functional change intended. Slot flags will need to be analyzed >> prior to try_async_pf() when KVM_MEM_PCI_HOLE is implemented. > (Sorry it took me so long to reply. No, I wasn't hoping for Paolo's magical "queued, thanks", I just tried to not read my email while on vacation). > Why? Wouldn't it be just as easy, and arguably more appropriate, to add > KVM_PFN_ERR_PCI_HOLE and update handle_abornmal_pfn() accordinaly? > Yes, we can do that, but what I don't quite like here is that try_async_pf() does much more than 'trying async PF'. In particular, it extracts 'pfn' and this is far from being obvious. Maybe we can rename try_async_pf() somewhat smartly (e.g. 'try_handle_pf()')? Your suggestion will make perfect sense to me then. >> Signed-off-by: Vitaly Kuznetsov >> --- >> arch/x86/kvm/mmu/mmu.c | 14 ++++++++------ >> arch/x86/kvm/mmu/paging_tmpl.h | 7 +++++-- >> 2 files changed, 13 insertions(+), 8 deletions(-) >> >> diff --git a/arch/x86/kvm/mmu/mmu.c b/arch/x86/kvm/mmu/mmu.c >> index 862bf418214e..fef6956393f7 100644 >> --- a/arch/x86/kvm/mmu/mmu.c >> +++ b/arch/x86/kvm/mmu/mmu.c >> @@ -4042,11 +4042,10 @@ static bool kvm_arch_setup_async_pf(struct kvm_vcpu *vcpu, gpa_t cr2_or_gpa, >> kvm_vcpu_gfn_to_hva(vcpu, gfn), &arch); >> } >> >> -static bool try_async_pf(struct kvm_vcpu *vcpu, bool prefault, gfn_t gfn, >> - gpa_t cr2_or_gpa, kvm_pfn_t *pfn, bool write, >> - bool *writable) >> +static bool try_async_pf(struct kvm_vcpu *vcpu, struct kvm_memory_slot *slot, >> + bool prefault, gfn_t gfn, gpa_t cr2_or_gpa, >> + kvm_pfn_t *pfn, bool write, bool *writable) >> { >> - struct kvm_memory_slot *slot = kvm_vcpu_gfn_to_memslot(vcpu, gfn); >> bool async; >> >> /* Don't expose private memslots to L2. */ >> @@ -4082,7 +4081,7 @@ static int direct_page_fault(struct kvm_vcpu *vcpu, gpa_t gpa, u32 error_code, >> bool exec = error_code & PFERR_FETCH_MASK; >> bool lpage_disallowed = exec && is_nx_huge_page_enabled(); >> bool map_writable; >> - >> + struct kvm_memory_slot *slot; >> gfn_t gfn = gpa >> PAGE_SHIFT; >> unsigned long mmu_seq; >> kvm_pfn_t pfn; >> @@ -4104,7 +4103,10 @@ static int direct_page_fault(struct kvm_vcpu *vcpu, gpa_t gpa, u32 error_code, >> mmu_seq = vcpu->kvm->mmu_notifier_seq; >> smp_rmb(); >> >> - if (try_async_pf(vcpu, prefault, gfn, gpa, &pfn, write, &map_writable)) >> + slot = kvm_vcpu_gfn_to_memslot(vcpu, gfn); >> + >> + if (try_async_pf(vcpu, slot, prefault, gfn, gpa, &pfn, write, >> + &map_writable)) >> return RET_PF_RETRY; >> >> if (handle_abnormal_pfn(vcpu, is_tdp ? 0 : gpa, gfn, pfn, ACC_ALL, &r)) >> diff --git a/arch/x86/kvm/mmu/paging_tmpl.h b/arch/x86/kvm/mmu/paging_tmpl.h >> index 0172a949f6a7..5c6a895f67c3 100644 >> --- a/arch/x86/kvm/mmu/paging_tmpl.h >> +++ b/arch/x86/kvm/mmu/paging_tmpl.h >> @@ -779,6 +779,7 @@ static int FNAME(page_fault)(struct kvm_vcpu *vcpu, gpa_t addr, u32 error_code, >> int write_fault = error_code & PFERR_WRITE_MASK; >> int user_fault = error_code & PFERR_USER_MASK; >> struct guest_walker walker; >> + struct kvm_memory_slot *slot; >> int r; >> kvm_pfn_t pfn; >> unsigned long mmu_seq; >> @@ -833,8 +834,10 @@ static int FNAME(page_fault)(struct kvm_vcpu *vcpu, gpa_t addr, u32 error_code, >> mmu_seq = vcpu->kvm->mmu_notifier_seq; >> smp_rmb(); >> >> - if (try_async_pf(vcpu, prefault, walker.gfn, addr, &pfn, write_fault, >> - &map_writable)) >> + slot = kvm_vcpu_gfn_to_memslot(vcpu, walker.gfn); >> + >> + if (try_async_pf(vcpu, slot, prefault, walker.gfn, addr, &pfn, >> + write_fault, &map_writable)) >> return RET_PF_RETRY; >> >> if (handle_abnormal_pfn(vcpu, addr, walker.gfn, pfn, walker.pte_access, &r)) >> -- >> 2.25.4 >> > -- Vitaly