Re: [PATCH 2/3] rcu: Add warning to ensure rcu_seq_done_exact() is working

2025-03-26 Thread Paul E. McKenney
On Wed, Mar 26, 2025 at 10:50:13PM +, Joel Fernandes wrote: > > > > On Mar 26, 2025, at 6:36 PM, Paul E. McKenney wrote: > > > > On Mon, Mar 24, 2025 at 01:01:54PM -0400, Joel Fernandes wrote: > >> The previous patch improved the rcu_seq_done_exact() function by adding > >> a meaningful co

Re: [PATCH 2/3] rcu: Add warning to ensure rcu_seq_done_exact() is working

2025-03-26 Thread Joel Fernandes
> On Mar 26, 2025, at 6:36 PM, Paul E. McKenney wrote: > > On Mon, Mar 24, 2025 at 01:01:54PM -0400, Joel Fernandes wrote: >> The previous patch improved the rcu_seq_done_exact() function by adding >> a meaningful constant for the guardband. >> >> Ensure that this is working for the future by

Re: [PATCH 2/3] rcu: Add warning to ensure rcu_seq_done_exact() is working

2025-03-26 Thread Paul E. McKenney
On Mon, Mar 24, 2025 at 01:01:54PM -0400, Joel Fernandes wrote: > The previous patch improved the rcu_seq_done_exact() function by adding > a meaningful constant for the guardband. > > Ensure that this is working for the future by a quick check during > rcu_gp_init(). > > Signed-off-by: Joel Fern

[PATCH 2/3] rcu: Add warning to ensure rcu_seq_done_exact() is working

2025-03-24 Thread Joel Fernandes
The previous patch improved the rcu_seq_done_exact() function by adding a meaningful constant for the guardband. Ensure that this is working for the future by a quick check during rcu_gp_init(). Signed-off-by: Joel Fernandes --- kernel/rcu/tree.c | 5 + 1 file changed, 5 insertions(+) diff