Re: [PATCH] mm: remove zap_page_range and create zap_vma_pages

2023-02-28 Thread patchwork-bot+linux-riscv
Hello: This patch was applied to riscv/linux.git (for-next) by Andrew Morton : 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

Re: [PATCH] mm: remove zap_page_range and create zap_vma_pages

2023-02-14 Thread Palmer Dabbelt
On Tue, 03 Jan 2023 16:27:32 PST (-0800), mike.krav...@oracle.com 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 v

Re: [PATCH] mm: remove zap_page_range and create zap_vma_pages

2023-01-08 Thread Christoph Hellwig
I would have split this into one patch that adds the new zap_vma_pages helper, and one to remove zap_page_range to split the separate changes. But the overall result looks fine, so feel free to add: Reviewed-by: Christoph Hellwig to this or the split patches.

Re: [PATCH] mm: remove zap_page_range and create zap_vma_pages

2023-01-04 Thread Heiko Carstens
On Tue, Jan 03, 2023 at 04:27:32PM -0800, Mike Kravetz 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.

Re: [PATCH] mm: remove zap_page_range and create zap_vma_pages

2023-01-04 Thread Peter Xu
On Tue, Jan 03, 2023 at 04:27:32PM -0800, Mike Kravetz 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.

Re: [PATCH] mm: remove zap_page_range and create zap_vma_pages

2023-01-03 Thread Michal Hocko
On Tue 03-01-23 16:27:32, Mike Kravetz 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

[PATCH] mm: remove zap_page_range and create zap_vma_pages

2023-01-03 Thread Mike Kravetz
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