Re: [PATCH] sched/isolation: Make NO_HZ_FULL select CPU_ISOLATION

2017-12-09 Thread Paul E. McKenney
On Sat, Dec 09, 2017 at 02:09:07PM +0100, Frederic Weisbecker wrote: > 2017-12-07 18:29 UTC+01:00, Paul E. McKenney : > > On Thu, Dec 07, 2017 at 05:14:54PM +0100, Frederic Weisbecker wrote: > >> 2017-12-04 18:16 UTC+01:00, Paul E. McKenney > >> : > >> > On Mon, Dec 04, 2017 at 04:53:15PM +0100, Fr

Re: [PATCH] sched/isolation: Make NO_HZ_FULL select CPU_ISOLATION

2017-12-09 Thread Frederic Weisbecker
2017-12-07 18:29 UTC+01:00, Paul E. McKenney : > On Thu, Dec 07, 2017 at 05:14:54PM +0100, Frederic Weisbecker wrote: >> 2017-12-04 18:16 UTC+01:00, Paul E. McKenney >> : >> > On Mon, Dec 04, 2017 at 04:53:15PM +0100, Frederic Weisbecker wrote: >> >> 2017-12-02 20:24 UTC+01:00, Paul E. McKenney >>

Re: [PATCH] sched/isolation: Make NO_HZ_FULL select CPU_ISOLATION

2017-12-07 Thread Paul E. McKenney
On Thu, Dec 07, 2017 at 05:14:54PM +0100, Frederic Weisbecker wrote: > 2017-12-04 18:16 UTC+01:00, Paul E. McKenney : > > On Mon, Dec 04, 2017 at 04:53:15PM +0100, Frederic Weisbecker wrote: > >> 2017-12-02 20:24 UTC+01:00, Paul E. McKenney > >> I would prefer to keep it. It's useful for automated

Re: [PATCH] sched/isolation: Make NO_HZ_FULL select CPU_ISOLATION

2017-12-07 Thread Frederic Weisbecker
2017-12-04 18:16 UTC+01:00, Paul E. McKenney : > On Mon, Dec 04, 2017 at 04:53:15PM +0100, Frederic Weisbecker wrote: >> 2017-12-02 20:24 UTC+01:00, Paul E. McKenney >> I would prefer to keep it. It's useful for automated boot testing >> based on configs such as 0-day or -tip test machines. But I'm

Re: [PATCH] sched/isolation: Make NO_HZ_FULL select CPU_ISOLATION

2017-12-04 Thread Paul E. McKenney
On Mon, Dec 04, 2017 at 04:53:15PM +0100, Frederic Weisbecker wrote: > 2017-12-02 20:24 UTC+01:00, Paul E. McKenney : > > On Sat, Dec 02, 2017 at 02:59:12PM +0100, Frederic Weisbecker wrote: > >> 2017-11-30 21:20 UTC+01:00, Paul E. McKenney > >> : > >> > Commit 5c4991e24c69 ("sched/isolation: Split

Re: [PATCH] sched/isolation: Make NO_HZ_FULL select CPU_ISOLATION

2017-12-04 Thread Frederic Weisbecker
2017-12-02 20:24 UTC+01:00, Paul E. McKenney : > On Sat, Dec 02, 2017 at 02:59:12PM +0100, Frederic Weisbecker wrote: >> 2017-11-30 21:20 UTC+01:00, Paul E. McKenney >> : >> > Commit 5c4991e24c69 ("sched/isolation: Split out new >> > CONFIG_CPU_ISOLATION=y config from CONFIG_NO_HZ_FULL") can result

Re: [PATCH] sched/isolation: Make NO_HZ_FULL select CPU_ISOLATION

2017-12-02 Thread Paul E. McKenney
On Sat, Dec 02, 2017 at 02:59:12PM +0100, Frederic Weisbecker wrote: > 2017-11-30 21:20 UTC+01:00, Paul E. McKenney : > > Commit 5c4991e24c69 ("sched/isolation: Split out new > > CONFIG_CPU_ISOLATION=y config from CONFIG_NO_HZ_FULL") can result in RCU > > CPU stall warnings when running rcutorture

Re: [PATCH] sched/isolation: Make NO_HZ_FULL select CPU_ISOLATION

2017-12-02 Thread Frederic Weisbecker
2017-11-30 21:20 UTC+01:00, Paul E. McKenney : > Commit 5c4991e24c69 ("sched/isolation: Split out new > CONFIG_CPU_ISOLATION=y config from CONFIG_NO_HZ_FULL") can result in RCU > CPU stall warnings when running rcutorture with CONFIG_NO_HZ_FULL_ALL=y > and CONFIG_CPU_ISOLATION=n. These warnings ar

[PATCH] sched/isolation: Make NO_HZ_FULL select CPU_ISOLATION

2017-11-30 Thread Paul E. McKenney
Commit 5c4991e24c69 ("sched/isolation: Split out new CONFIG_CPU_ISOLATION=y config from CONFIG_NO_HZ_FULL") can result in RCU CPU stall warnings when running rcutorture with CONFIG_NO_HZ_FULL_ALL=y and CONFIG_CPU_ISOLATION=n. These warnings are caused by RCU's grace-period kthreads sleeping for a