[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <8735E3A2-795B-4D52-9634-D48C68645A5D@gmail.com>
Date: Fri, 11 Aug 2023 11:52:53 -0700
From: Nadav Amit <nadav.amit@...il.com>
To: Yan Zhao <yan.y.zhao@...el.com>
Cc: linux-mm <linux-mm@...ck.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
kvm@...r.kernel.org, Paolo Bonzini <pbonzini@...hat.com>,
Sean Christopherson <seanjc@...gle.com>,
Mike Kravetz <mike.kravetz@...cle.com>, apopple@...dia.com,
Jason Gunthorpe <jgg@...dia.com>,
Mike Rapoport <rppt@...nel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
kevin.tian@...el.com, david@...hat.com
Subject: Re: [RFC PATCH v2 4/5] mm/autonuma: call .numa_protect() when page is
protected for NUMA migrate
> On Aug 10, 2023, at 2:00 AM, Yan Zhao <yan.y.zhao@...el.com> wrote:
>
> Call mmu notifier's callback .numa_protect() in change_pmd_range() when
> a page is ensured to be protected by PROT_NONE for NUMA migration purpose.
Consider squashing with the previous patch. It’s better to see the user
(caller) with the new functionality.
It would be useful to describe what the expected course of action that
numa_protect callback should take.
Powered by blists - more mailing lists