From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: paulmck@linux.vnet.ibm.com
Cc: linux-kernel@vger.kernel.org, tony@bakeyournoodle.com,
paulus@samba.org, dino@in.ibm.com, tytso@us.ibm.com,
dvhltc@us.ibm.com, antonb@us.ibm.com, rostedt@goodmis.org,
niv@us.ibm.com
Subject: Re: [PATCH, RFC] hacks to allow -rt to run kernbench on POWER
Date: Tue, 30 Oct 2007 07:37:50 +1100 [thread overview]
Message-ID: <1193690270.9928.35.camel@pasglop> (raw)
In-Reply-To: <20071029202617.GF8824@linux.vnet.ibm.com>
On Mon, 2007-10-29 at 13:26 -0700, Paul E. McKenney wrote:
>
> > I see a lot of case where you add preempt_disable/enable around
> areas
> > that have the PTE lock held...
> >
> > So in -rt, spin_lock doesn't disable preempt ? I'm a bit worried...
> > there are some strong requirements that anything within that lock is
> not
> > preempted, so zap_pte_ranges() is the obvious ones but all of them
> would
> > need to be addressed.
>
> Right in one! One of the big changes in -rt is that spinlock critical
> sections (and RCU read-side critical sections, for that matter) are
> preemptible under CONFIG_PREEMPT_RT.
>
> And I agree that this patchset will have missed quite a few places
> where
> additional changes are required. Hence the word "including" above,
> rather
> than something like "specifically". ;-)
Ok, well, I'm pretty familiar with that MM code since I wrote a good
deal of the current version so I'll try to spend some time with your
patch have a look. It may have to wait for next week though, but feel
free to ping me if you don't hear back, in case it falls through the
hole in my brain :-)
Ben.
next prev parent reply other threads:[~2007-10-29 20:40 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 [this message]
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
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=1193690270.9928.35.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=antonb@us.ibm.com \
--cc=dino@in.ibm.com \
--cc=dvhltc@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=niv@us.ibm.com \
--cc=paulmck@linux.vnet.ibm.com \
--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