From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Darren Hart <dvhltc@us.ibm.com>,
linux-kernel@vger.kernel.org, tony@bakeyournoodle.com,
paulus@samba.org, dino@in.ibm.com, tytso@us.ibm.com,
antonb@us.ibm.com, rostedt@goodmis.org
Subject: Re: [PATCH, RFC] hacks to allow -rt to run kernbench on POWER
Date: Thu, 1 Nov 2007 08:50:28 -0700 [thread overview]
Message-ID: <20071101155028.GB14231@linux.vnet.ibm.com> (raw)
In-Reply-To: <1193865328.9928.141.camel@pasglop>
On Thu, Nov 01, 2007 at 08:15:28AM +1100, Benjamin Herrenschmidt wrote:
>
> > So as Paul mentioned, spin_lock is now a mutex. There is a new
> > raw_spinlock however (simply change the way it is declared, calling
> > conventions are the same) which is used in a very few areas where a
> > traditional spin_lock is truly necessary. This may or may not be one of
> > those times, but I wanted to point it out.
>
> Yeah, I figured that. My main worry has more to do with some fishy
> assumptions the powerpc VM code does regarding what can and cannot
> happen in those locked sections, among other things. I'll have to sit
> and think about it for a little while to convince myself we are ok ...
> or not. Plus we do keep track of various MM related things in per-CPU
> data structures but it looks like Paul already spotted that.
My concern would be that I failed to spot all of them. ;-)
Thanx, Paul
next prev parent reply other threads:[~2007-11-01 15:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-29 18:50 [PATCH, RFC] hacks to allow -rt to run kernbench on POWER Paul E. McKenney
2007-10-29 20:07 ` Benjamin Herrenschmidt
2007-10-29 20:26 ` Paul E. McKenney
2007-10-29 20:37 ` Benjamin Herrenschmidt
2007-10-29 21:16 ` Paul E. McKenney
2007-10-31 20:54 ` Darren Hart
2007-10-31 21:15 ` Benjamin Herrenschmidt
2007-11-01 15:50 ` Paul E. McKenney [this message]
2007-12-13 3:56 ` Steven Rostedt
2007-12-13 6:10 ` Paul E. McKenney
2007-12-13 12:52 ` Steven Rostedt
2007-12-13 18:25 ` 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=20071101155028.GB14231@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=antonb@us.ibm.com \
--cc=benh@kernel.crashing.org \
--cc=dino@in.ibm.com \
--cc=dvhltc@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paulus@samba.org \
--cc=rostedt@goodmis.org \
--cc=tony@bakeyournoodle.com \
--cc=tytso@us.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