From: Peter Zijlstra <peterz@infradead.org>
To: Nick Piggin <npiggin@suse.de>
Cc: Ingo Molnar <mingo@elte.hu>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Mike Galbraith <efault@gmx.de>
Subject: Re: some recent scheduler patches
Date: Wed, 02 Dec 2009 20:04:02 +0100 [thread overview]
Message-ID: <1259780642.4003.1493.camel@laptop> (raw)
In-Reply-To: <20091202185328.GI31517@wotan.suse.de>
On Wed, 2009-12-02 at 19:53 +0100, Nick Piggin wrote:
>
>
> 83f54960c11a14942ab00b54c51e91906b9d8235: sched: for_each_domain() vs RCU
> I don't see what is the step that causes FAIL? sched-domains code is
> using synchronize_sched(), so that part should be safe.
Yeah, I got myself properly confused there. I was meaning to remove that
rcu_read_lock() there again.
prev parent reply other threads:[~2009-12-02 19:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-02 18:53 Nick Piggin
2009-12-02 19:04 ` 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=1259780642.4003.1493.camel@laptop \
--to=peterz@infradead.org \
--cc=efault@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=npiggin@suse.de \
/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
all inboxes | Powered by JetHome®