[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20191211154429.7tscxcqk725guyce@box>
Date: Wed, 11 Dec 2019 18:44:29 +0300
From: "Kirill A. Shutemov" <kirill@...temov.name>
To: Mircea CIRJALIU - MELIU <mcirjaliu@...defender.com>
Cc: "linux-mm@...ck.org" <linux-mm@...ck.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Jerome Glisse <jglisse@...hat.com>,
Paolo Bonzini <pbonzini@...hat.com>,
"aarcange@...hat.com" <aarcange@...hat.com>
Subject: Re: [RFC PATCH v1 2/4] mm: also set VMA in khugepaged range
invalidation
On Wed, Dec 11, 2019 at 09:29:21AM +0000, Mircea CIRJALIU - MELIU wrote:
> MMU notifier client may need the VMA for extra info.
> This change is needed by the remote mapping feature that inspects anon VMAs
> with huge mappings.
The change itself is okay, but commit message should be better.
Do we have any user of mmu notifiers in current kernel that affected by
the missing vma here?
And subject starting with 'also' looks wrong to me.
--
Kirill A. Shutemov
Powered by blists - more mailing lists