From: Sean Christopherson <seanjc@google.com>
To: Peter Xu <peterx@redhat.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
Paolo Bonzini <pbonzini@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
David Hildenbrand <david@redhat.com>,
"Dr . David Alan Gilbert" <dgilbert@redhat.com>,
Andrea Arcangeli <aarcange@redhat.com>,
Linux MM Mailing List <linux-mm@kvack.org>
Subject: Re: [PATCH 4/4] kvm/x86: Allow to respond to generic signals during slow page faults
Date: Thu, 23 Jun 2022 14:46:08 +0000 [thread overview]
Message-ID: <YrR8sKap6KHT22Dx@google.com> (raw)
In-Reply-To: <20220622213656.81546-5-peterx@redhat.com>
On Wed, Jun 22, 2022, Peter Xu wrote:
> diff --git a/arch/x86/kvm/mmu/mmu.c b/arch/x86/kvm/mmu/mmu.c
> index e92f1ab63d6a..b39acb7cb16d 100644
> --- a/arch/x86/kvm/mmu/mmu.c
> +++ b/arch/x86/kvm/mmu/mmu.c
> @@ -3012,6 +3012,13 @@ static int kvm_handle_bad_page(struct kvm_vcpu *vcpu, gfn_t gfn, kvm_pfn_t pfn)
> static int handle_abnormal_pfn(struct kvm_vcpu *vcpu, struct kvm_page_fault *fault,
> unsigned int access)
> {
> + /* NOTE: not all error pfn is fatal; handle intr before the other ones */
> + if (unlikely(is_intr_pfn(fault->pfn))) {
> + vcpu->run->exit_reason = KVM_EXIT_INTR;
> + ++vcpu->stat.signal_exits;
> + return -EINTR;
> + }
> +
> /* The pfn is invalid, report the error! */
> if (unlikely(is_error_pfn(fault->pfn)))
> return kvm_handle_bad_page(vcpu, fault->gfn, fault->pfn);
> @@ -4017,6 +4024,8 @@ static int kvm_faultin_pfn(struct kvm_vcpu *vcpu, struct kvm_page_fault *fault)
> }
> }
>
> + /* Allow to respond to generic signals in slow page faults */
"slow" is being overloaded here. The previous call __gfn_to_pfn_memslot() will
end up in hva_to_pfn_slow(), but because of passing a non-null async it won't wait.
This code really should have a more extensive comment irrespective of the interruptible
stuff, now would be a good time to add that.
Comments aside, isn't this series incomplete from the perspective that there are
still many flows where KVM will hang if gfn_to_pfn() gets stuck in gup? E.g. if
KVM is retrieving a page pointed at by vmcs12.
> + flags |= KVM_GTP_INTERRUPTIBLE;
> fault->pfn = __gfn_to_pfn_memslot(slot, fault->gfn, flags, NULL,
> &fault->map_writable, &fault->hva);
> return RET_PF_CONTINUE;
> diff --git a/include/linux/kvm_host.h b/include/linux/kvm_host.h
> index 4f84a442f67f..c8d98e435537 100644
> --- a/include/linux/kvm_host.h
> +++ b/include/linux/kvm_host.h
> @@ -1163,6 +1163,7 @@ typedef unsigned int __bitwise kvm_gtp_flag_t;
>
> #define KVM_GTP_WRITE ((__force kvm_gtp_flag_t) BIT(0))
> #define KVM_GTP_ATOMIC ((__force kvm_gtp_flag_t) BIT(1))
> +#define KVM_GTP_INTERRUPTIBLE ((__force kvm_gtp_flag_t) BIT(2))
>
> kvm_pfn_t __gfn_to_pfn_memslot(const struct kvm_memory_slot *slot, gfn_t gfn,
> kvm_gtp_flag_t gtp_flags, bool *async,
> diff --git a/virt/kvm/kvm_main.c b/virt/kvm/kvm_main.c
> index 952400b42ee9..b3873cac5672 100644
> --- a/virt/kvm/kvm_main.c
> +++ b/virt/kvm/kvm_main.c
> @@ -2462,6 +2462,8 @@ static int hva_to_pfn_slow(unsigned long addr, bool *async,
> flags |= FOLL_WRITE;
> if (async)
> flags |= FOLL_NOWAIT;
> + if (gtp_flags & KVM_GTP_INTERRUPTIBLE)
> + flags |= FOLL_INTERRUPTIBLE;
>
> npages = get_user_pages_unlocked(addr, 1, &page, flags);
> if (npages != 1)
> @@ -2599,6 +2601,8 @@ kvm_pfn_t hva_to_pfn(unsigned long addr, kvm_gtp_flag_t gtp_flags, bool *async,
> npages = hva_to_pfn_slow(addr, async, gtp_flags, writable, &pfn);
> if (npages == 1)
> return pfn;
> + if (npages == -EINTR)
> + return KVM_PFN_ERR_INTR;
>
> mmap_read_lock(current->mm);
> if (npages == -EHWPOISON ||
> --
> 2.32.0
>
next prev parent reply other threads:[~2022-06-23 14:46 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-22 21:36 [PATCH 0/4] kvm/mm: Allow GUP to respond to non fatal signals Peter Xu
2022-06-22 21:36 ` [PATCH 1/4] mm/gup: Add FOLL_INTERRUPTIBLE Peter Xu
2022-06-25 0:35 ` Jason Gunthorpe
2022-06-25 1:23 ` Peter Xu
2022-06-25 23:59 ` Jason Gunthorpe
2022-06-27 15:29 ` Peter Xu
2022-06-28 2:07 ` John Hubbard
2022-06-28 19:31 ` Peter Xu
2022-06-28 21:40 ` John Hubbard
2022-06-28 22:33 ` Peter Xu
2022-06-29 0:31 ` John Hubbard
2022-06-29 15:47 ` Peter Xu
2022-06-30 1:53 ` John Hubbard
2022-06-30 13:49 ` Peter Xu
2022-06-30 19:01 ` John Hubbard
2022-06-30 21:27 ` Peter Xu
2022-07-04 22:48 ` Matthew Wilcox
2022-07-07 15:06 ` Peter Xu
2022-06-22 21:36 ` [PATCH 2/4] kvm: Merge "atomic" and "write" in __gfn_to_pfn_memslot() Peter Xu
2022-06-23 14:49 ` Sean Christopherson
2022-06-23 19:46 ` Peter Xu
2022-06-23 20:29 ` Sean Christopherson
2022-06-23 21:29 ` Peter Xu
2022-06-23 21:52 ` Sean Christopherson
2022-06-27 19:12 ` John Hubbard
2022-06-28 2:17 ` John Hubbard
2022-06-28 19:46 ` Peter Xu
2022-06-28 21:52 ` John Hubbard
2022-06-28 22:50 ` Peter Xu
2022-06-28 22:55 ` John Hubbard
2022-06-28 23:02 ` Peter Xu
2022-06-22 21:36 ` [PATCH 3/4] kvm: Add new pfn error KVM_PFN_ERR_INTR Peter Xu
2022-06-23 14:31 ` Sean Christopherson
2022-06-23 19:32 ` Peter Xu
2022-06-22 21:36 ` [PATCH 4/4] kvm/x86: Allow to respond to generic signals during slow page faults Peter Xu
2022-06-23 14:46 ` Sean Christopherson [this message]
2022-06-23 19:31 ` Peter Xu
2022-06-23 20:07 ` Sean Christopherson
2022-06-23 20:18 ` Peter Xu
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=YrR8sKap6KHT22Dx@google.com \
--to=seanjc@google.com \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=dgilbert@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=pbonzini@redhat.com \
--cc=peterx@redhat.com \
/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).