From: Josh Boyer <jwboyer@linux.vnet.ibm.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org, Felix Radensky <felix@embedded-sol.com>
Subject: Re: Preemption question (4xx related)
Date: Thu, 2 Jul 2009 07:12:46 -0400 [thread overview]
Message-ID: <20090702111246.GG6189@zod.rchland.ibm.com> (raw)
In-Reply-To: <1246519992.7551.1.camel@pasglop>
On Thu, Jul 02, 2009 at 05:33:12PM +1000, Benjamin Herrenschmidt wrote:
>On Wed, 2009-07-01 at 20:14 -0400, Josh Boyer wrote:
>
>> I've toyed with that idea myself. I keep coming back to the fact that you need
>> a workload that would really leverage it, and I don't have one at the moment.
>
>To some extent that's true but just turning full preemption including
>kernel side with all the associated debug bits and lockdep should make a
>whole bunch of things show up even with ordinary workloads.
I can look at doing that for ppc44x_defconfig. I'll be honest and say I don't
expect it to go well, particularly with lockdep :).
>For 440 tend to boot an ubuntu distro off NFS root with all X & DRI 3D
>etc... and then run compiz :-)
Yes. Because that's a totally realistic workload for a 440. I'm surprised you
don't have a p595 machine acting as your home router too! ;)
josh
next prev parent reply other threads:[~2009-07-02 11:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-30 12:55 Preemption question (4xx related) Felix Radensky
2009-07-01 22:13 ` Benjamin Herrenschmidt
2009-07-02 0:14 ` Josh Boyer
2009-07-02 7:33 ` Benjamin Herrenschmidt
2009-07-02 11:12 ` Josh Boyer [this message]
2009-07-02 22:41 ` Benjamin Herrenschmidt
2009-07-03 0:34 ` Josh Boyer
2009-07-02 9:14 ` Michel Dänzer
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=20090702111246.GG6189@zod.rchland.ibm.com \
--to=jwboyer@linux.vnet.ibm.com \
--cc=benh@kernel.crashing.org \
--cc=felix@embedded-sol.com \
--cc=linuxppc-dev@ozlabs.org \
/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;
as well as URLs for NNTP newsgroup(s).