Received: by 2002:a05:6902:102b:0:0:0:0 with SMTP id x11csp4071ybt; Tue, 16 Jun 2020 14:52:01 -0700 (PDT) X-Google-Smtp-Source: ABdhPJy4S+3YUA7Tque32FI0Ade+B3EPmcys+tZysRsrWwGWtV+e42pQvxvbdEnVfv75s3uTM+vS X-Received: by 2002:a05:6402:1b01:: with SMTP id by1mr4439848edb.20.1592344321607; Tue, 16 Jun 2020 14:52:01 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1592344321; cv=none; d=google.com; s=arc-20160816; b=YUGa6KmcpW2+5lX0R+WFTIoCAO1LJph8A+zYr6BtMlehbVO/GucV2jf8xMcZ6CToQl 4b5apPBWgLWBr8L3j5LxOI2qPhJHwYKTl9XONPpOglxYrJCPefDMuFj49kBE7vYN5uPD mQHCMbj3FlqiX2bIVAvPDnZd5Y+lAEo5OwDgl1hybfpb0vgFQ9xc70fI9U1WGjoyp3YH eq5NU6NhU0FydHiMdK4d4Pmihu8jpq66q0B7BVeiyG/+NdClZbXeDkfRPrvXRxUJ3rnR he0xlAcwpKPSxfVNObgv1x1FVHT9L+a8/2dLmMHqgET+mya3aD8cPrwlyOxwh4RAQDt+ axGQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :references:in-reply-to:message-id:date:subject:cc:to:from :dkim-signature; bh=HJopFOxb2oxM6WdAq1omP3wKyWlk0t81tbJtj1deElA=; b=yeM4hFD7b4f/gl/anZJJUdGcMxOqpG+ko6peNycxXFd3/6Jp3HgUf1I0X1VQFkH/lN oVc2O08NAvT2FE+O+mVKwh02RU1oxfN9PJLhKLMxMebiqCi+Lg14RBbWa9T05qhWtvdm VTH1v5dpba8CT9KuazuxptQzQsA1/0psEWq7CiANVNgqpoXHrsa5fNOHrOB9Ct8Tdgnt t6uh701Giis8H+eLb6a9+vh9oZ8v4bbnOmWQsNaIHAEKFj1+KzkrnbclbUST/GpaV0yY dWW99LaTS3OhyKx/M1kY0JHJL4v9L1lbLS1Y/D0BGw/9qI9LtXTjziLRgrfcAWyxrMA5 uxTg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=b+GLksqh; 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 ar22si11916195ejc.434.2020.06.16.14.51.38; Tue, 16 Jun 2020 14:52:01 -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=b+GLksqh; 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 S1726384AbgFPVtR (ORCPT + 99 others); Tue, 16 Jun 2020 17:49:17 -0400 Received: from us-smtp-delivery-1.mimecast.com ([205.139.110.120]:35105 "EHLO us-smtp-1.mimecast.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1726253AbgFPVtO (ORCPT ); Tue, 16 Jun 2020 17:49:14 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1592344152; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=HJopFOxb2oxM6WdAq1omP3wKyWlk0t81tbJtj1deElA=; b=b+GLksqhNcP1Z0F1sXEEof3580ZAxXSvb6Kv+sO/39CtSRHfeceJ1E5jvrEDZ8RQO5lRcj s6tafEp38X4m2HelIGRqxwliuleqxp9NsyjA42S5UR6cg67SZiuMh2T5SyNZ2rjV0v+0WR Pk7ZY7aVK3aeJxRC10AlZMoE6cOIyHk= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-274-9HvqEOY8M165iHPSCcEe1A-1; Tue, 16 Jun 2020 17:49:11 -0400 X-MC-Unique: 9HvqEOY8M165iHPSCcEe1A-1 Received: from smtp.corp.redhat.com (int-mx08.intmail.prod.int.phx2.redhat.com [10.5.11.23]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id D315B18585C8; Tue, 16 Jun 2020 21:49:09 +0000 (UTC) Received: from horse.redhat.com (ovpn-114-132.rdu2.redhat.com [10.10.114.132]) by smtp.corp.redhat.com (Postfix) with ESMTP id 510E419C71; Tue, 16 Jun 2020 21:49:03 +0000 (UTC) Received: by horse.redhat.com (Postfix, from userid 10451) id C4B81225E4A; Tue, 16 Jun 2020 17:49:02 -0400 (EDT) From: Vivek Goyal To: kvm@vger.kernel.org, linux-kernel@vger.kernel.org Cc: virtio-fs@redhat.com, miklos@szeredi.hu, stefanha@redhat.com, dgilbert@redhat.com, vgoyal@redhat.com, vkuznets@redhat.com, pbonzini@redhat.com, wanpengli@tencent.com, sean.j.christopherson@intel.com Subject: [PATCH 1/3] kvm,x86: Force sync fault if previous attempts failed Date: Tue, 16 Jun 2020 17:48:45 -0400 Message-Id: <20200616214847.24482-2-vgoyal@redhat.com> In-Reply-To: <20200616214847.24482-1-vgoyal@redhat.com> References: <20200616214847.24482-1-vgoyal@redhat.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Scanned-By: MIMEDefang 2.84 on 10.5.11.23 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Page fault error handling behavior in kvm seems little inconsistent when page fault reports error. If we are doing fault synchronously then we capture error (-EFAULT) returned by __gfn_to_pfn_memslot() and exit to user space and qemu reports error, "error: kvm run failed Bad address". But if we are doing async page fault, then async_pf_execute() will simply ignore the error reported by get_user_pages_remote(). It is assumed that page fault was successful and either a page ready event is injected in guest or guest is brought out of artificial halt state and run again. In both the cases when guest retries the instruction, it takes exit again as page fault was not successful in previous attempt. And then this infinite loop continues forever. This patch tries to make this behavior consistent. That is instead of getting into infinite loop of retrying page fault, exit to user space and stop VM if page fault error happens. This can be improved by injecting errors in guest when it is allowed. Later patches can inject error when a process in guest triggered page fault and in that case guest process will receive SIGBUS. Currently we don't have a way to inject errors when guest is in kernel mode. Once we have race free method to do so, we should be able to inject errors and guest can do fixup_exception() if caller set it up so (virtio-fs). When async pf encounters error then save that pfn and when next time guest retries, do a sync fault instead of async fault. So that if error is encountered, we exit to qemu and avoid infinite loop. As of now only one error pfn is stored and that means it could be overwritten before next a retry from guest happens. But this is just a hint and if we miss it, some other time we will catch it. If this becomes an issue, we could maintain an array of error gfn later to help ease the issue. Signed-off-by: Vivek Goyal --- arch/x86/include/asm/kvm_host.h | 1 + arch/x86/kvm/mmu.h | 2 +- arch/x86/kvm/mmu/mmu.c | 2 +- arch/x86/kvm/x86.c | 19 +++++++++++++++++-- include/linux/kvm_host.h | 1 + virt/kvm/async_pf.c | 8 ++++++-- 6 files changed, 27 insertions(+), 6 deletions(-) diff --git a/arch/x86/include/asm/kvm_host.h b/arch/x86/include/asm/kvm_host.h index 938497a6ebd7..348a73106556 100644 --- a/arch/x86/include/asm/kvm_host.h +++ b/arch/x86/include/asm/kvm_host.h @@ -778,6 +778,7 @@ struct kvm_vcpu_arch { unsigned long nested_apf_token; bool delivery_as_pf_vmexit; bool pageready_pending; + gfn_t error_gfn; } apf; /* OSVW MSRs (AMD only) */ diff --git a/arch/x86/kvm/mmu.h b/arch/x86/kvm/mmu.h index 0ad06bfe2c2c..6fa085ff07a3 100644 --- a/arch/x86/kvm/mmu.h +++ b/arch/x86/kvm/mmu.h @@ -60,7 +60,7 @@ void kvm_init_mmu(struct kvm_vcpu *vcpu, bool reset_roots); void kvm_init_shadow_mmu(struct kvm_vcpu *vcpu, u32 cr0, u32 cr4, u32 efer); void kvm_init_shadow_ept_mmu(struct kvm_vcpu *vcpu, bool execonly, bool accessed_dirty, gpa_t new_eptp); -bool kvm_can_do_async_pf(struct kvm_vcpu *vcpu); +bool kvm_can_do_async_pf(struct kvm_vcpu *vcpu, gfn_t gfn); int kvm_handle_page_fault(struct kvm_vcpu *vcpu, u64 error_code, u64 fault_address, char *insn, int insn_len); diff --git a/arch/x86/kvm/mmu/mmu.c b/arch/x86/kvm/mmu/mmu.c index 15984dfde427..e207900ab303 100644 --- a/arch/x86/kvm/mmu/mmu.c +++ b/arch/x86/kvm/mmu/mmu.c @@ -4078,7 +4078,7 @@ static bool try_async_pf(struct kvm_vcpu *vcpu, bool prefault, gfn_t gfn, if (!async) return false; /* *pfn has correct page already */ - if (!prefault && kvm_can_do_async_pf(vcpu)) { + if (!prefault && kvm_can_do_async_pf(vcpu, cr2_or_gpa >> PAGE_SHIFT)) { trace_kvm_try_async_get_page(cr2_or_gpa, gfn); if (kvm_find_async_pf_gfn(vcpu, gfn)) { trace_kvm_async_pf_doublefault(cr2_or_gpa, gfn); diff --git a/arch/x86/kvm/x86.c b/arch/x86/kvm/x86.c index 697d1b273a2f..4c5205434b9c 100644 --- a/arch/x86/kvm/x86.c +++ b/arch/x86/kvm/x86.c @@ -10513,7 +10513,7 @@ static bool kvm_can_deliver_async_pf(struct kvm_vcpu *vcpu) return true; } -bool kvm_can_do_async_pf(struct kvm_vcpu *vcpu) +bool kvm_can_do_async_pf(struct kvm_vcpu *vcpu, gfn_t gfn) { if (unlikely(!lapic_in_kernel(vcpu) || kvm_event_needs_reinjection(vcpu) || @@ -10527,7 +10527,13 @@ bool kvm_can_do_async_pf(struct kvm_vcpu *vcpu) * If interrupts are off we cannot even use an artificial * halt state. */ - return kvm_arch_interrupt_allowed(vcpu); + if (!kvm_arch_interrupt_allowed(vcpu)) + return false; + + if (vcpu->arch.apf.error_gfn == gfn) + return false; + + return true; } bool kvm_arch_async_page_not_present(struct kvm_vcpu *vcpu, @@ -10583,6 +10589,15 @@ void kvm_arch_async_page_present(struct kvm_vcpu *vcpu, kvm_apic_set_irq(vcpu, &irq, NULL); } + if (work->error_code) { + /* + * Page fault failed and we don't have a way to report + * errors back to guest yet. So save this pfn and force + * sync page fault next time. + */ + vcpu->arch.apf.error_gfn = work->cr2_or_gpa >> PAGE_SHIFT; + } + vcpu->arch.apf.halted = false; vcpu->arch.mp_state = KVM_MP_STATE_RUNNABLE; } diff --git a/include/linux/kvm_host.h b/include/linux/kvm_host.h index 216cdb6581e2..b8558334b184 100644 --- a/include/linux/kvm_host.h +++ b/include/linux/kvm_host.h @@ -207,6 +207,7 @@ struct kvm_async_pf { struct kvm_arch_async_pf arch; bool wakeup_all; bool notpresent_injected; + int error_code; }; void kvm_clear_async_pf_completion_queue(struct kvm_vcpu *vcpu); diff --git a/virt/kvm/async_pf.c b/virt/kvm/async_pf.c index a36828fbf40a..6b30374a4de1 100644 --- a/virt/kvm/async_pf.c +++ b/virt/kvm/async_pf.c @@ -52,6 +52,7 @@ static void async_pf_execute(struct work_struct *work) gpa_t cr2_or_gpa = apf->cr2_or_gpa; int locked = 1; bool first; + long ret; might_sleep(); @@ -61,11 +62,14 @@ static void async_pf_execute(struct work_struct *work) * access remotely. */ down_read(&mm->mmap_sem); - get_user_pages_remote(NULL, mm, addr, 1, FOLL_WRITE, NULL, NULL, - &locked); + ret = get_user_pages_remote(NULL, mm, addr, 1, FOLL_WRITE, NULL, NULL, + &locked); if (locked) up_read(&mm->mmap_sem); + if (ret < 0) + apf->error_code = ret; + if (IS_ENABLED(CONFIG_KVM_ASYNC_PF_SYNC)) kvm_arch_async_page_present(vcpu, apf); -- 2.25.4