From: Mike Rapoport <rppt@kernel.org>
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 Kravetz" <mike.kravetz@oracle.com>
Subject: Re: [PATCH] mm/mmu_notifier: Remove unused mmu_notifier_range_update_to_read_only export
Date: Mon, 9 Jan 2023 12:13:25 +0200 [thread overview]
Message-ID: <Y7voxRr+aM7f5e6d@kernel.org> (raw)
In-Reply-To: <20230109012207.79457-1-apopple@nvidia.com>
On Mon, Jan 09, 2023 at 12:22:07PM +1100, 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>
> ---
> include/linux/mmu_notifier.h | 2 --
> mm/mmu_notifier.c | 10 ----------
> 2 files changed, 12 deletions(-)
>
> diff --git a/include/linux/mmu_notifier.h b/include/linux/mmu_notifier.h
> index d6c06e140277..252e44afcc70 100644
> --- a/include/linux/mmu_notifier.h
> +++ b/include/linux/mmu_notifier.h
> @@ -269,7 +269,6 @@ extern struct lockdep_map __mmu_notifier_invalidate_range_start_map;
> #endif
>
> struct mmu_notifier_range {
> - struct vm_area_struct *vma;
> struct mm_struct *mm;
> unsigned long start;
> unsigned long end;
> @@ -519,7 +518,6 @@ static inline void mmu_notifier_range_init(struct mmu_notifier_range *range,
> unsigned long start,
> unsigned long end)
> {
> - range->vma = vma;
> range->event = event;
> range->mm = mm;
> range->start = start;
> diff --git a/mm/mmu_notifier.c b/mm/mmu_notifier.c
> index f45ff1b7626a..50c0dde1354f 100644
> --- a/mm/mmu_notifier.c
> +++ b/mm/mmu_notifier.c
> @@ -1120,13 +1120,3 @@ void mmu_notifier_synchronize(void)
> synchronize_srcu(&srcu);
> }
> EXPORT_SYMBOL_GPL(mmu_notifier_synchronize);
> -
> -bool
> -mmu_notifier_range_update_to_read_only(const struct mmu_notifier_range *range)
> -{
> - if (!range->vma || range->event != MMU_NOTIFY_PROTECTION_VMA)
> - return false;
> - /* Return true if the vma still have the read flag set. */
> - return range->vma->vm_flags & VM_READ;
> -}
> -EXPORT_SYMBOL_GPL(mmu_notifier_range_update_to_read_only);
> --
> 2.35.1
>
>
--
Sincerely yours,
Mike.
next prev parent reply other threads:[~2023-01-09 10:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-09 1:22 [PATCH] mm/mmu_notifier: Remove unused mmu_notifier_range_update_to_read_only export Alistair Popple
2023-01-09 10:13 ` Mike Rapoport [this message]
2023-01-09 13:11 ` Jason Gunthorpe
2023-01-09 19:20 ` Mike Kravetz
2023-01-10 0:37 ` Alistair Popple
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=Y7voxRr+aM7f5e6d@kernel.org \
--to=rppt@kernel.org \
--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=mike.kravetz@oracle.com \
--cc=rcampbell@nvidia.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.