From: Peter Zijlstra <peterz@infradead.org>
To: vatsa@in.ibm.com
Cc: Ingo Molnar <mingo@elte.hu>,
linux-kernel <linux-kernel@vger.kernel.org>,
Dhaval Giani <dhaval@linux.vnet.ibm.com>,
Balbir Singh <balbir@linux.vnet.ibm.com>,
shaggy@linux.vnet.ibm.com, brking@linux.vnet.ibm.com
Subject: Re: sched: only update rq->clock while holding rq->lock
Date: Thu, 16 Oct 2008 10:29:42 +0200 [thread overview]
Message-ID: <1224145782.28131.27.camel@twins> (raw)
In-Reply-To: <20081016023252.GA25969@linux.vnet.ibm.com>
On Thu, 2008-10-16 at 08:02 +0530, Srivatsa Vaddagiri wrote:
> On Wed, Oct 15, 2008 at 08:37:23PM +0200, Peter Zijlstra wrote:
> > Vatsa noticed rq->clock going funny and tracked it down to an update_rq_clock()
> > outside a rq->lock section.
>
> For the records, actually Brian King and David Kleikamp noticed this!
Thanks Brian and Shaggy!
prev parent reply other threads:[~2008-10-16 8:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-15 18:37 sched: only update rq->clock while holding rq->lock Peter Zijlstra
2008-10-16 2:32 ` Srivatsa Vaddagiri
2008-10-16 8:29 ` Peter Zijlstra [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=1224145782.28131.27.camel@twins \
--to=peterz@infradead.org \
--cc=balbir@linux.vnet.ibm.com \
--cc=brking@linux.vnet.ibm.com \
--cc=dhaval@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=shaggy@linux.vnet.ibm.com \
--cc=vatsa@in.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox