From: Jaap-Jan Boor <jjboor@aimsys•nl>
To: Steven Scholz <steven.scholz@imc-berlin•de>
Cc: Marius Groeger <mgroeger@sysgo•com>,
"linuxppc-embedded@lists•linuxppc.org"
<linuxppc-embedded@lists•linuxppc.org>
Subject: Re: Preemptive Kernel and MPC8xx ???
Date: Wed, 26 Nov 2003 17:19:24 +0100 [thread overview]
Message-ID: <1069863564.1263.1.camel@linpc003.aimsys.nl> (raw)
In-Reply-To: <3FC30F17.1070904@imc-berlin.de>
On Tue, 2003-11-25 at 09:13, Steven Scholz wrote:
> Hi,
>
> > On Mon, 24 Nov 2003, Jaap-Jan Boor wrote:
> >
> >>Yes I do on 2.4.20 and 2.4.22 from kernel.org. So far all seems
> >>to work but didn't do any measurements on it.
> >>(I both use the preempt and low-latency patches)
> Have you writting your own device drivers?
> How did you make them preemptable?
I didn't... I still assume the kernel will lock
e.g. the same SIU irq
>
> Marius Groeger wrote:
> > AFAIK, you can pretty much drop the low-latency patch in favor of
> > using the lock-breaking patch. It is also available from Robert Love
> > at the cited home page.
> How about homemade device drivers when using the lock-breaking patch?
>
> Thanks!
>
> --
> Steven Scholz
>
> imc Measurement & Control imc Meßsysteme GmbH
> Voltastr. 5 Voltastr. 5
> 13355 Berlin 13355 Berlin
> Germany Deutschland
> fon: +49 30 467090-0 Tel: 030 / 467090-0
> fax: +49 30 4631576 fax: 030 / 4631576
>
>
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-11-26 16:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-23 12:02 Preemptive Kernel and MPC8xx ??? Steven Scholz
2003-11-24 7:20 ` Jaap-Jan Boor
2003-11-24 8:01 ` Steven Scholz
2003-11-24 9:46 ` Jaap-Jan Boor
2003-11-24 9:55 ` Steven Scholz
2003-11-24 16:35 ` Marius Groeger
2003-11-24 22:33 ` Jaap-Jan Boor
2003-11-25 8:13 ` Steven Scholz
2003-11-26 16:19 ` Jaap-Jan Boor [this message]
2003-11-26 15:08 ` Steven Scholz
2003-11-26 16:23 ` Jaap-Jan Boor
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=1069863564.1263.1.camel@linpc003.aimsys.nl \
--to=jjboor@aimsys$(echo .)nl \
--cc=linuxppc-embedded@lists$(echo .)linuxppc.org \
--cc=mgroeger@sysgo$(echo .)com \
--cc=steven.scholz@imc-berlin$(echo .)de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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