[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <167761867732.10135.11248419155612086016.git-patchwork-notify@kernel.org>
Date: Tue, 28 Feb 2023 21:11:17 +0000
From: patchwork-bot+linux-riscv@...nel.org
To: Mike Kravetz <mike.kravetz@...cle.com>
Cc: linux-riscv@...ts.infradead.org, linux-mm@...ck.org,
linux-kernel@...r.kernel.org, linuxppc-dev@...ts.ozlabs.org,
linux-s390@...r.kernel.org, netdev@...r.kernel.org,
hch@...radead.org, david@...hat.com, mhocko@...e.com,
peterx@...hat.com, nadav.amit@...il.com, willy@...radead.org,
vbabka@...e.cz, riel@...riel.com, will@...nel.org,
mpe@...erman.id.au, palmer@...belt.com, borntraeger@...ux.ibm.com,
dave.hansen@...ux.intel.com, brauner@...nel.org,
edumazet@...gle.com, akpm@...ux-foundation.org
Subject: Re: [PATCH] mm: remove zap_page_range and create zap_vma_pages
Hello:
This patch was applied to riscv/linux.git (for-next)
by Andrew Morton <akpm@...ux-foundation.org>:
On Tue, 3 Jan 2023 16:27:32 -0800 you wrote:
> zap_page_range was originally designed to unmap pages within an address
> range that could span multiple vmas. While working on [1], it was
> discovered that all callers of zap_page_range pass a range entirely within
> a single vma. In addition, the mmu notification call within zap_page
> range does not correctly handle ranges that span multiple vmas. When
> crossing a vma boundary, a new mmu_notifier_range_init/end call pair
> with the new vma should be made.
>
> [...]
Here is the summary with links:
- mm: remove zap_page_range and create zap_vma_pages
https://git.kernel.org/riscv/c/e9adcfecf572
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
Powered by blists - more mailing lists