From: Mike Kravetz <mike.kravetz@oracle.com>
To: Alistair Popple <apopple@nvidia.com>
Cc: "Andrew Morton" <akpm@linux-foundation.org>,
linux-mm@kvack.org, "John Hubbard" <jhubbard@nvidia.com>,
"Ralph Campbell" <rcampbell@nvidia.com>,
"Jérôme Glisse" <jglisse@redhat.com>,
"Ira Weiny" <ira.weiny@intel.com>,
"Jason Gunthorpe" <jgg@nvidia.com>,
"Christoph Hellwig" <hch@lst.de>,
"Mike Rapoport" <rppt@kernel.org>
Subject: Re: [PATCH v2] mm/mmu_notifier: Remove unused mmu_notifier_range_update_to_read_only export
Date: Tue, 10 Jan 2023 09:53:07 -0800 [thread overview]
Message-ID: <Y72mA/A+Az5flpJB@monkey> (raw)
In-Reply-To: <20230110025722.600912-1-apopple@nvidia.com>
On 01/10/23 13:57, Alistair Popple wrote:
> mmu_notifier_range_update_to_read_only() was originally introduced in
> commit c6d23413f81b ("mm/mmu_notifier:
> mmu_notifier_range_update_to_read_only() helper") as an optimisation
> for device drivers that know a range has only been mapped
> read-only. However there are no users of this feature so remove it. As
> it is the only user of the struct mmu_notifier_range.vma field remove
> that also.
>
> Signed-off-by: Alistair Popple <apopple@nvidia.com>
> Acked-by: Mike Rapoport (IBM) <rppt@kernel.org>
> Reviewed-by: Jason Gunthorpe <jgg@nvidia.com>
>
> ---
>
> Changes for v2:
>
> - Added Mike's Acked-by
>
> - Added Jason's Reviewed-by
>
> - Removed the now unused vma parameter from
> mmu_notififer_range_init{_owner}()
> ---
> fs/proc/task_mmu.c | 2 +-
> include/linux/mmu_notifier.h | 13 +++++--------
> kernel/events/uprobes.c | 2 +-
> mm/huge_memory.c | 4 ++--
> mm/hugetlb.c | 13 ++++++-------
> mm/khugepaged.c | 6 +++---
> mm/ksm.c | 5 ++---
> mm/madvise.c | 2 +-
> mm/mapping_dirty_helpers.c | 2 +-
> mm/memory.c | 12 ++++++------
> mm/migrate_device.c | 4 ++--
> mm/mmu_notifier.c | 10 ----------
> mm/mprotect.c | 2 +-
> mm/mremap.c | 2 +-
> mm/oom_kill.c | 2 +-
> mm/rmap.c | 11 +++++------
> 16 files changed, 38 insertions(+), 54 deletions(-)
Thanks for removing the now unused vma parameter.
There has been some code movement in hugetlb.c and memory.c, so Andrew may
need to fixup a bit. However, that should be straight forward.
Reviewed-by: Mike Kravetz <mike.kravetz@oracle.com>
--
Mike Kravetz
prev parent reply other threads:[~2023-01-10 17:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-10 2:57 Alistair Popple
2023-01-10 6:47 ` Christoph Hellwig
2023-01-10 17:53 ` Mike Kravetz [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Y72mA/A+Az5flpJB@monkey \
--to=mike.kravetz@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=apopple@nvidia.com \
--cc=hch@lst.de \
--cc=ira.weiny@intel.com \
--cc=jgg@nvidia.com \
--cc=jglisse@redhat.com \
--cc=jhubbard@nvidia.com \
--cc=linux-mm@kvack.org \
--cc=rcampbell@nvidia.com \
--cc=rppt@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox