From: Frederic Weisbecker <frederic@kernel.org>
To: "Paul E. McKenney" <paulmck@linux.ibm.com>
Cc: "Joel Fernandes (Google)" <joel@joelfernandes.org>,
linux-kernel@vger.kernel.org, rcu@vger.kernel.org
Subject: Re: [PATCH -rcu dev 1/3] rcu/tree: tick_dep_set/clear_cpu should accept bits instead of masks
Date: Tue, 20 Aug 2019 14:08:45 +0200 [thread overview]
Message-ID: <20190820120843.GA2093@lenoir> (raw)
In-Reply-To: <20190819164420.GA28441@linux.ibm.com>
On Mon, Aug 19, 2019 at 09:44:20AM -0700, Paul E. McKenney wrote:
> On Mon, Aug 19, 2019 at 06:32:27PM +0200, Frederic Weisbecker wrote:
> > > But would the following patch make sense? This would not help for (say)
> > > use of TICK_MASK_BIT_POSIX_TIMER instead of TICK_DEP_BIT_POSIX_TIMER, but
> > > would help for any new values that might be added later on. And currently
> > > for TICK_DEP_MASK_CLOCK_UNSTABLE and TICK_DEP_MASK_RCU.
> >
> > I'd rather make the TICK_DEP_MASK_* values private to kernel/time/tick-sched.c but
> > that means I need to re-arrange a bit include/trace/events/timer.h
>
> That would be even better! For one thing, it would detect misuse of
> -all- of the _MASK_ values. ;-)
:o)
>
> > I'm looking into it. Meanwhile, your below patch that checks for the max value is
> > still valuable.
>
> If I were to push it, it would be v5.5 before it showed up. My guess
> is therefore that I should keep it for my own internal use in the near
> term, but not push it. If you would like to take it, feel free to use
> my Signed-off-by.
Ok, applying.
Thanks!
next prev parent reply other threads:[~2019-08-20 12:08 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-16 2:53 [PATCH -rcu dev 1/3] rcu/tree: tick_dep_set/clear_cpu should accept bits instead of masks Joel Fernandes (Google)
2019-08-16 2:53 ` [PATCH -rcu dev 2/3] rcu/tree: Fix issue where sometimes rcu_urgent_qs is not set on IPI Joel Fernandes (Google)
2019-08-16 2:57 ` Joel Fernandes
2019-08-16 2:53 ` [PATCH -rcu dev 3/3] RFC: rcu/tree: Read dynticks_nmi_nesting in advance Joel Fernandes (Google)
2019-08-16 16:24 ` Joel Fernandes
2019-08-16 16:52 ` Paul E. McKenney
2019-08-16 17:07 ` Joel Fernandes
2019-08-16 17:30 ` Paul E. McKenney
2019-08-19 12:59 ` Frederic Weisbecker
2019-08-19 14:22 ` Joel Fernandes
2019-08-19 14:41 ` Paul E. McKenney
2019-08-19 15:46 ` Joel Fernandes
2019-08-19 16:17 ` Paul E. McKenney
2019-08-19 14:40 ` Paul E. McKenney
2019-08-16 2:59 ` [PATCH v2 -rcu dev 2/3] rcu/tree: Fix issue where sometimes rcu_urgent_qs is not set on IPI Joel Fernandes (Google)
2019-08-16 17:04 ` Paul E. McKenney
2019-08-16 17:25 ` [PATCH -rcu dev 1/3] rcu/tree: tick_dep_set/clear_cpu should accept bits instead of masks Paul E. McKenney
2019-08-16 17:35 ` Joel Fernandes
2019-08-19 12:38 ` Frederic Weisbecker
2019-08-19 14:46 ` Paul E. McKenney
2019-08-19 16:32 ` Frederic Weisbecker
2019-08-19 16:44 ` Paul E. McKenney
2019-08-20 12:08 ` Frederic Weisbecker [this message]
2019-08-20 14:44 ` Paul E. McKenney
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190820120843.GA2093@lenoir \
--to=frederic@kernel.org \
--cc=joel@joelfernandes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@linux.ibm.com \
--cc=rcu@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).