From: Jeremy Siegel <jsiegel@mvista.com>
To: linuxsh-dev@lists.sourceforge.net
Cc: Robert Love <rml@tech9.net>, linux-kernel@vger.kernel.org
Subject: Re: [linuxsh-dev] [PATCH] Preemptible kernel for SH
Date: Mon, 03 Dec 2001 13:16:00 -0800 [thread overview]
Message-ID: <3C0BEB90.16DC3749@mvista.com> (raw)
In-Reply-To: <1007261428.820.4.camel@phantasy>
Just FYI... the preemptible kernel depends on non-preemptible critical regions
denoted by spinlock calls (see Robert Love's excellent summary in
Documentation/preempt-locking.txt). Many common drivers are assumed to have
correct locking for SMP operation, but non-SMP drivers may not. I've only run
the PreK SH kernel on the Solution Engine w/Ethernet and serial, but I did not
yet check to see if additional locks might be required in drivers/char/sh-sci.c
or drivers/net/stnic.c, which are specific to SH platforms and thus not SMP-safe
otherwise.
--Jeremy
Robert Love wrote:
> The attached is the fully preemptible linux kernel patch, for the SH
> arch. This work is thanks to Jeremy Siegel of MontaVista.
>
> You will need an SH-patched kernel tree, available from
> http://sf.net/projects/linuxsh -- the CVS module "linux" has a drop-in
> replacement for 2.4.16.
>
> You will need the base preempt-kernel patch, available from
> ftp://ftp.kernel.org/pub/linux/kernel/people/rml/preempt-kernel
>
> Feedback is desired.
>
> Robert Love
next prev parent reply other threads:[~2001-12-04 0:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-02 2:50 [PATCH] Preemptible kernel for SH Robert Love
2001-12-02 3:28 ` Robert Love
2001-12-03 21:16 ` Jeremy Siegel [this message]
2001-12-03 22:18 ` [linuxsh-dev] " Robert Love
2001-12-05 22:22 ` Robert Love
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=3C0BEB90.16DC3749@mvista.com \
--to=jsiegel@mvista.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxsh-dev@lists.sourceforge.net \
--cc=rml@tech9.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.