[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <13d3a7a4-5cf8-4fbe-8dba-d565525a71c6@amazon.com>
Date: Thu, 27 Nov 2025 11:19:35 +0000
From: Nikita Kalyazin <kalyazin@...zon.com>
To: Mike Rapoport <rppt@...nel.org>
CC: <linux-mm@...ck.org>, Andrea Arcangeli <aarcange@...hat.com>, "Andrew
Morton" <akpm@...ux-foundation.org>, Axel Rasmussen
<axelrasmussen@...gle.com>, Baolin Wang <baolin.wang@...ux.alibaba.com>,
David Hildenbrand <david@...hat.com>, Hugh Dickins <hughd@...gle.com>, "James
Houghton" <jthoughton@...gle.com>, "Liam R. Howlett"
<Liam.Howlett@...cle.com>, Lorenzo Stoakes <lorenzo.stoakes@...cle.com>,
Michal Hocko <mhocko@...e.com>, Paolo Bonzini <pbonzini@...hat.com>, Peter Xu
<peterx@...hat.com>, Sean Christopherson <seanjc@...gle.com>, Shuah Khan
<shuah@...nel.org>, Suren Baghdasaryan <surenb@...gle.com>, Vlastimil Babka
<vbabka@...e.cz>, <linux-kernel@...r.kernel.org>, <kvm@...r.kernel.org>,
<linux-kselftest@...r.kernel.org>
Subject: Re: [PATCH v2 4/5] guest_memfd: add support for userfaultfd minor
mode
On 27/11/2025 10:36, Mike Rapoport wrote:
> On Wed, Nov 26, 2025 at 04:49:31PM +0000, Nikita Kalyazin wrote:
>> On 25/11/2025 18:38, Mike Rapoport wrote:
>>> From: "Mike Rapoport (Microsoft)" <rppt@...nel.org>
>>>
>>> +#ifdef CONFIG_USERFAULTFD
>>> +static struct folio *kvm_gmem_get_folio(struct inode *inode, pgoff_t pgoff)
>>
>> We have to name it differently, otherwise it clashes with the existing one
>> in this file.
>
> It's all David's fault! ;-P
> How about kvm_gmem_get_prepared_folio() ?
I'm afraid it may not be ideal due to preparedness tracking being
removed from guest_memfd at some point [1]. Would it be too bad to add
an indication to userfaultfd in the name somehow given that it's already
guarded by the config?
[1]
https://lore.kernel.org/linux-coco/20251113230759.1562024-1-michael.roth@amd.com
>
> --
> Sincerely yours,
> Mike.
Powered by blists - more mailing lists