Re: [PATCH RFC 13/24] mm: merge parameters for change_protection()

2019-01-23 Thread Peter Xu
On Mon, Jan 21, 2019 at 08:54:46AM -0500, Jerome Glisse wrote: > On Mon, Jan 21, 2019 at 03:57:11PM +0800, Peter Xu wrote: > > change_protection() was used by either the NUMA or mprotect() code, > > there's one parameter for each of the callers (dirty_accountable and > > prot_numa). Further,

Re: [PATCH RFC 13/24] mm: merge parameters for change_protection()

2019-01-21 Thread Jerome Glisse
On Mon, Jan 21, 2019 at 03:57:11PM +0800, Peter Xu wrote: > change_protection() was used by either the NUMA or mprotect() code, > there's one parameter for each of the callers (dirty_accountable and > prot_numa). Further, these parameters are passed along the calls: > > -

[PATCH RFC 13/24] mm: merge parameters for change_protection()

2019-01-21 Thread Peter Xu
change_protection() was used by either the NUMA or mprotect() code, there's one parameter for each of the callers (dirty_accountable and prot_numa). Further, these parameters are passed along the calls: - change_protection_range() - change_p4d_range() - change_pud_range() -