From: Peter Xu <peterx@redhat.com>
To: linux-kernel@vger.kernel.org, kvm@vger.kernel.org
Cc: Sean Christopherson <seanjc@google.com>,
David Hildenbrand <david@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
Andrea Arcangeli <aarcange@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
"Dr . David Alan Gilbert" <dgilbert@redhat.com>,
Linux MM Mailing List <linux-mm@kvack.org>,
John Hubbard <jhubbard@nvidia.com>
Subject: Re: [PATCH v3 0/3] kvm/mm: Allow GUP to respond to non fatal signals
Date: Thu, 6 Oct 2022 16:47:43 -0400 [thread overview]
Message-ID: <Yz8+7/1uCzcGumBS@x1n> (raw)
In-Reply-To: <20220817003614.58900-1-peterx@redhat.com>
On Tue, Aug 16, 2022 at 08:36:11PM -0400, Peter Xu wrote:
> v3:
> - Patch 1
> - Added r-b for DavidH
> - Added support for hugetlbfs
> - Patch 2 & 3
> - Comment fixes [Sean]
> - Move introduction of "interruptible" parameter into patch 2 [Sean]
> - Move sigpending handling into kvm_handle_bad_page [Sean]
> - Renamed kvm_handle_bad_page() to kvm_handle_error_pfn() [Sean, DavidM]
> - Use kvm_handle_signal_exit() [Sean]
Any further comments from kvm side? Thanks,
--
Peter Xu
next prev parent reply other threads:[~2022-10-06 20:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-17 0:36 Peter Xu
2022-08-17 0:36 ` [PATCH v3 1/3] mm/gup: Add FOLL_INTERRUPTIBLE Peter Xu
2022-08-17 0:36 ` [PATCH v3 2/3] kvm: Add new pfn error KVM_PFN_ERR_SIGPENDING Peter Xu
2022-10-07 1:39 ` Sean Christopherson
2022-10-07 15:03 ` Peter Xu
2022-08-17 0:36 ` [PATCH v3 3/3] kvm/x86: Allow to respond to generic signals during slow page faults Peter Xu
2022-08-17 1:37 ` [PATCH v3 0/3] kvm/mm: Allow GUP to respond to non fatal signals Peter Xu
2022-10-06 20:47 ` Peter Xu [this message]
2022-10-07 1:40 ` Sean Christopherson
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=Yz8+7/1uCzcGumBS@x1n \
--to=peterx@redhat.com \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=dgilbert@redhat.com \
--cc=jhubbard@nvidia.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.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