From: Katsuya Matsubara <matsu@igel.co.jp>
To: linux-rt-users <linux-rt-users@vger.kernel.org>
Cc: Steven Rostedt <srostedt@redhat.com>, Ingo Molnar <mingo@elte.hu>,
Thomas Gleixner <tglx@linutronix.de>,
Paul Mundt <lethal@linux-sh.org>,
LKML <linux-kernel@vger.kernel.org>,
Katsuya Matsubara <matsu@igel.co.jp>
Subject: [PATCH RT 0/4] sh arch support for 2.6.28-rt
Date: Thu, 12 Feb 2009 00:01:39 +0900 [thread overview]
Message-ID: <1234364503-857-1-git-send-email-matsu@igel.co.jp> (raw)
These patches apply preempt-rt treatments into sh specific code.
64 bit support is not included because I have no sh64 board.
These are based on the 2.6.28-rt git.
I made sure that these work on renesas rts7751r2dplus.
-- Katsuya Matsubara / matsu@igel.co.jp
---
Katsuya Matsubara (4):
sh: use __preempt_enable_no_resched in cpu_idle()
sh: enable interrupts in signal handling
sh: decouple the pagefault-disabled logic
convert-locks-list: add sh specific spin locks
arch/sh/kernel/process_32.c | 2 +-
arch/sh/kernel/signal_32.c | 7 +++++++
arch/sh/mm/fault_32.c | 2 +-
scripts/convert-locks-list | 12 ++++++++++++
4 files changed, 21 insertions(+), 2 deletions(-)
next reply other threads:[~2009-02-11 15:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-11 15:01 Katsuya Matsubara [this message]
2009-02-11 15:01 ` [PATCH RT 1/4] sh: use __preempt_enable_no_resched in cpu_idle() Katsuya Matsubara
2009-02-11 15:01 ` [PATCH RT 2/4] sh: enable interrupts in signal handling Katsuya Matsubara
2009-02-11 15:01 ` [PATCH RT 3/4] sh: decouple the pagefault-disabled logic Katsuya Matsubara
2009-02-11 15:01 ` [PATCH RT 4/4] convert-locks-list: add sh specific spin locks Katsuya Matsubara
2009-02-11 15:16 ` [PATCH RT 0/4] sh arch support for 2.6.28-rt Steven Rostedt
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=1234364503-857-1-git-send-email-matsu@igel.co.jp \
--to=matsu@igel.co.jp \
--cc=lethal@linux-sh.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=srostedt@redhat.com \
--cc=tglx@linutronix.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