Re: [PATCH] powerpc/64s/radix: reset mm_cpumask for single thread process when possible

2018-05-09 Thread Nicholas Piggin
On Wed, 09 May 2018 18:31:55 +1000 Benjamin Herrenschmidt wrote: > On Wed, 2018-05-09 at 16:56 +1000, Nicholas Piggin wrote: > > When a single-threaded process has a non-local mm_cpumask and requires > > a full PID tlbie invalidation, use that as an opportunity to reset the > >

Re: [PATCH] powerpc/64s/radix: reset mm_cpumask for single thread process when possible

2018-05-09 Thread Nicholas Piggin
On Wed, 9 May 2018 18:23:48 +1000 Balbir Singh wrote: > On Wed, May 9, 2018 at 4:56 PM, Nicholas Piggin wrote: > > When a single-threaded process has a non-local mm_cpumask and requires > > a full PID tlbie invalidation, use that as an opportunity to

Re: [PATCH] powerpc/64s/radix: reset mm_cpumask for single thread process when possible

2018-05-09 Thread Benjamin Herrenschmidt
On Wed, 2018-05-09 at 16:56 +1000, Nicholas Piggin wrote: > When a single-threaded process has a non-local mm_cpumask and requires > a full PID tlbie invalidation, use that as an opportunity to reset the > cpumask back to the current CPU we're running on. > > No other thread can concurrently

Re: [PATCH] powerpc/64s/radix: reset mm_cpumask for single thread process when possible

2018-05-09 Thread Balbir Singh
On Wed, May 9, 2018 at 4:56 PM, Nicholas Piggin wrote: > When a single-threaded process has a non-local mm_cpumask and requires > a full PID tlbie invalidation, use that as an opportunity to reset the > cpumask back to the current CPU we're running on. > > No other thread can

[PATCH] powerpc/64s/radix: reset mm_cpumask for single thread process when possible

2018-05-09 Thread Nicholas Piggin
When a single-threaded process has a non-local mm_cpumask and requires a full PID tlbie invalidation, use that as an opportunity to reset the cpumask back to the current CPU we're running on. No other thread can concurrently switch to this mm, because it must have had a reference on mm_users