[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200728191518.GA159104@nvidia.com>
Date: Tue, 28 Jul 2020 16:15:18 -0300
From: Jason Gunthorpe <jgg@...dia.com>
To: Ralph Campbell <rcampbell@...dia.com>
CC: <linux-rdma@...r.kernel.org>, <linux-mm@...ck.org>,
<nouveau@...ts.freedesktop.org>, <kvm-ppc@...r.kernel.org>,
<linux-kselftest@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
Jerome Glisse <jglisse@...hat.com>,
John Hubbard <jhubbard@...dia.com>,
Christoph Hellwig <hch@....de>,
Andrew Morton <akpm@...ux-foundation.org>,
Shuah Khan <shuah@...nel.org>, Ben Skeggs <bskeggs@...hat.com>,
Bharata B Rao <bharata@...ux.ibm.com>
Subject: Re: [PATCH v4 3/6] mm/notifier: add migration invalidation type
On Thu, Jul 23, 2020 at 03:30:01PM -0700, Ralph Campbell wrote:
> static inline int mm_has_notifiers(struct mm_struct *mm)
> @@ -513,6 +519,7 @@ static inline void mmu_notifier_range_init(struct mmu_notifier_range *range,
> range->start = start;
> range->end = end;
> range->flags = flags;
> + range->migrate_pgmap_owner = NULL;
> }
Since this function is commonly called and nobody should read
migrate_pgmap_owner unless MMU_NOTIFY_MIGRATE is set as the event,
this assignment can be dropped.
Jason
Powered by blists - more mailing lists