Date: Wed, 26 Oct 2022 22:49:26 +0000
From: Sean Christopherson <seanjc@google.com>
To: Peter Xu <peterx@redhat.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
	John Hubbard <jhubbard@nvidia.com>,
	Paolo Bonzini <pbonzini@redhat.com>,
	David Matlack <dmatlack@google.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Andrea Arcangeli <aarcange@redhat.com>,
	"Dr . David Alan Gilbert" <dgilbert@redhat.com>,
	David Hildenbrand <david@redhat.com>,
	Linux MM Mailing List <linux-mm@kvack.org>,
	Mike Kravetz <mike.kravetz@oracle.com>
Subject: Re: [PATCH v4 3/4] kvm: Add interruptible flag to
 __gfn_to_pfn_memslot()
Message-ID: <Y1m5dv48PKOY6Xbq@google.com>
References: <20221011195809.557016-1-peterx@redhat.com>
 <20221011195809.557016-4-peterx@redhat.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20221011195809.557016-4-peterx@redhat.com>
Sender: owner-linux-mm@kvack.org
Precedence: bulk

"KVM:" for the shortlog.

On Tue, Oct 11, 2022, Peter Xu wrote:
> Add a new "interruptible" flag showing that the caller is willing to be
> interrupted by signals during the __gfn_to_pfn_memslot() request.  Wire it
> up with a FOLL_INTERRUPTIBLE flag that we've just introduced.
> 
> This prepares KVM to be able to respond to SIGUSR1 (for QEMU that's the
> SIGIPI) even during e.g. handling an userfaultfd page fault.
> 
> No functional change intended.
> 
> Signed-off-by: Peter Xu <peterx@redhat.com>
> ---

Reviewed-by: Sean Christopherson <seanjc@google.com>