[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220525221917.GA1151462@lothringen>
Date: Thu, 26 May 2022 00:19:17 +0200
From: Frederic Weisbecker <frederic@...nel.org>
To: LKML <linux-kernel@...r.kernel.org>
Cc: Tejun Heo <tj@...nel.org>, Peter Zijlstra <peterz@...radead.org>,
"Paul E . McKenney" <paulmck@...nel.org>,
Paul Gortmaker <paul.gortmaker@...driver.com>,
Johannes Weiner <hannes@...xchg.org>,
Marcelo Tosatti <mtosatti@...hat.com>,
Phil Auld <pauld@...hat.com>,
Zefan Li <lizefan.x@...edance.com>,
Waiman Long <longman@...hat.com>,
Daniel Bristot de Oliveira <bristot@...nel.org>,
Nicolas Saenz Julienne <nsaenz@...nel.org>,
rcu@...r.kernel.org
Subject: Re: [PATCH 1/4] rcu/nocb: Pass a cpumask instead of a single CPU to
offload/deoffload
On Thu, May 26, 2022 at 12:10:52AM +0200, Frederic Weisbecker wrote:
> @@ -1117,12 +1111,6 @@ static long rcu_nocb_rdp_offload(void *arg)
> struct rcu_data *rdp_gp = rdp->nocb_gp_rdp;
>
> WARN_ON_ONCE(rdp->cpu != raw_smp_processor_id());
> - /*
> - * For now we only support re-offload, ie: the rdp must have been
> - * offloaded on boot first.
> - */
> - if (!rdp->nocb_gp_rdp)
> - return -EINVAL;
>
> if (WARN_ON_ONCE(!rdp_gp->nocb_gp_kthread))
> return -EINVAL;
And why did I remove this critical check? I have no answer...
Powered by blists - more mailing lists