From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Michael Schmitz <schmitz@opal.biophys.uni-duesseldorf.de>
Cc: "Michel Dänzer" <daenzer@debian.org>,
"linuxppc-dev list" <linuxppc-dev@lists.linuxppc.org>,
"debian-powerpc@lists.debian.org"
<debian-powerpc@lists.debian.org>
Subject: Re: PREEMPT on PPC
Date: Mon, 29 Mar 2004 22:01:11 +1000 [thread overview]
Message-ID: <1080561670.1210.23.camel@gaston> (raw)
In-Reply-To: <Pine.LNX.4.44.0403291329300.4088-100000@opal.biophys.uni-duesseldorf.de>
On Mon, 2004-03-29 at 21:29, Michael Schmitz wrote:
> > > What else are you using ? I suspect something like MOL may have troubles
> > > with preempt for example...
> >
> > Not using that regularly. Not sure what's special about my setup, XFS
> > maybe?
> >
> > What about this:
> >
> > -CONFIG_TASK_SIZE=0xc0000000
> > +CONFIG_TASK_SIZE=0x80000000
>
> Nope, that's what my kernel is built with as well.
BTW. I pushed more preempt fixes upsteam (see lkml if not in
mainstream yet).
Ben.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-03-29 12:01 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-25 6:47 PREEMPT on PPC Benjamin Herrenschmidt
2004-03-25 8:01 ` Benjamin Herrenschmidt
2004-03-25 16:09 ` Colin Leroy
2004-03-25 22:42 ` Benjamin Herrenschmidt
2004-03-26 17:48 ` Michael Schmitz
2004-03-26 19:27 ` Michel Dänzer
2004-03-27 9:14 ` Mathieu Segaud
2004-03-27 15:05 ` Michel Dänzer
2004-03-29 1:26 ` Benjamin Herrenschmidt
2004-03-29 1:38 ` Michel Dänzer
2004-03-29 1:55 ` Benjamin Herrenschmidt
2004-03-29 9:31 ` Michael Schmitz
2004-03-29 10:43 ` Michel Dänzer
2004-03-29 11:29 ` Michael Schmitz
2004-03-29 12:01 ` Benjamin Herrenschmidt [this message]
2004-03-29 12:00 ` Benjamin Herrenschmidt
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=1080561670.1210.23.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=daenzer@debian.org \
--cc=debian-powerpc@lists.debian.org \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=schmitz@opal.biophys.uni-duesseldorf.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;
as well as URLs for NNTP newsgroup(s).