From: Steven Rostedt <srostedt@redhat.com>
To: Heiko Carstens <heiko.carstens@de.ibm.com>
Cc: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
Gautham R Shenoy <ego@in.ibm.com>,
Dipankar Sarma <dipankar@in.ibm.com>, Ingo Molnar <mingo@elte.hu>,
Martin Schwidefsky <schwidefsky@de.ibm.com>,
linux-kernel@vger.kernel.org
Subject: Re: preempt rcu bug on s390
Date: Mon, 11 Feb 2008 10:37:33 -0500 [thread overview]
Message-ID: <47B06BBD.4050306@redhat.com> (raw)
In-Reply-To: <20080210130150.GA9044@osiris.ibm.com>
Heiko Carstens wrote:
>> Does s390 start out in nohz mode? The reason I ask is that it feels like
>> an off-by-one error for the dynticks_progress_counter.
>
> Actually I forgot to add a few ifdefs to make the code do something :)
> That just reveals that we have a conflict with the dynticks implementation
> and s390's nohz that shows up in what rcu_irq_enter/exit assume.
> I didn't patch s390 and common code so it will work, but I think the
> patch you mentionened will fix the problem I reported.
> So I guess we should either convert s390 to use the generic dynticks
> implementation or disable preemptible rcu on s390 until we converted
> our code.
>
> Thanks for helping debugging this!
Heiko, thanks for reporting this.
This patch still didn't make it into -rc1, and it really should. Because
without this patch, PREEMPT_RCU and NO_HZ together is broken, on all boxes.
The patch is in Ingo's sched-devel git tree, as
9460545f81ea48b07dbb20456a8ede776d8ebc1b (last I checked) and titled:
rcu: add support for dynamic ticks and preempt rcu
-- Steve
prev parent reply other threads:[~2008-02-11 15:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-09 11:34 preempt rcu bug on s390 Heiko Carstens
2008-02-09 14:07 ` Paul E. McKenney
2008-02-09 17:14 ` Heiko Carstens
2008-02-09 22:02 ` Paul E. McKenney
2008-02-10 13:01 ` Heiko Carstens
2008-02-10 17:43 ` Paul E. McKenney
2008-02-11 15:37 ` Steven Rostedt [this message]
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=47B06BBD.4050306@redhat.com \
--to=srostedt@redhat.com \
--cc=dipankar@in.ibm.com \
--cc=ego@in.ibm.com \
--cc=heiko.carstens@de.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paulmck@linux.vnet.ibm.com \
--cc=schwidefsky@de.ibm.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.