[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <0183984a-c95f-c92e-629e-775071b5cd23@nvidia.com>
Date: Thu, 30 Jun 2022 12:01:53 -0700
From: John Hubbard <jhubbard@...dia.com>
To: Peter Xu <peterx@...hat.com>
Cc: kvm@...r.kernel.org, linux-kernel@...r.kernel.org,
Paolo Bonzini <pbonzini@...hat.com>,
Andrew Morton <akpm@...ux-foundation.org>,
David Hildenbrand <david@...hat.com>,
"Dr . David Alan Gilbert" <dgilbert@...hat.com>,
Andrea Arcangeli <aarcange@...hat.com>,
Linux MM Mailing List <linux-mm@...ck.org>,
Sean Christopherson <seanjc@...gle.com>
Subject: Re: [PATCH 1/4] mm/gup: Add FOLL_INTERRUPTIBLE
On 6/30/22 06:49, Peter Xu wrote:
> Looks good to me, I'd tune a bit to make it less ambiguous on a few places:
>
> /*
> * FAULT_FLAG_INTERRUPTIBLE is opt-in. GUP callers must set
> * FOLL_INTERRUPTIBLE to enable FAULT_FLAG_INTERRUPTIBLE.
> * That's because some callers may not be prepared to
> * handle early exits caused by non-fatal signals.
> */
>
> Would that be okay to you?
>
Yes, looks good. With that change, please feel free to add:
Reviewed-by: John Hubbard <jhubbard@...dia.com>
thanks,
--
John Hubbard
NVIDIA
Powered by blists - more mailing lists