From: Frank Rowand <frowand@mvista.com>
To: linux-kernel@vger.kernel.org, mingo@elte.hu
Subject: [PATCH 0/5] ppc RT: Realtime preempt support for PPC
Date: Mon, 07 Mar 2005 13:48:13 -0800 [thread overview]
Message-ID: <422CCC1D.1050902@mvista.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2987 bytes --]
Ingo,
I have updated my patch of 16 Feb 2005 that adds realtime support for PowerPC
(32 bit only). The patches will be sent in following emails.
The patch series applies over Ingo's real-time preempt patch:
http://people.redhat.com/mingo/realtime-preempt/realtime-preempt-2.6.11-rc4-V0.7.39-02
The patches are:
1/5 ppc_rt.patch - the core realtime functionality for PPC
2/5 ppc_cpu_khz.patch - This is separated out from the first patch to
reduce the noise in the first patch. It defines
cpu_khz, which is needed by usecs_to_cyles() in
kernel/latency.c.
3/5 ppc_mcount.patch - Implements mcount() and _mcount() for performance
instrumentation.
The following two patches should not be applied by anyone unless they want
to test the other three patches on the IBM PPC 405GP eval board:
4/5 ibm_emac_core.patch - This patch has been separately submitted to PPC.
5/5 smp405.patch - a hack to allow compiling a PPC 405 kernel with
CONFIG_SMP=y
The changes from the previous patch are:
Added #ifdef CONFIG_PPC32 to raw_rwlock_t in include/linux/rt_lock.h. The
ppc lock is a signed int instead of an unsigned long.
Replaced us_to_tb with cpu_khz to more consistent with i386 and to remove
the #ifdef CONFIG_PPC in usecs_to_cycles().
Added mcount() and _mcount() that I previously said was a work in progress.
Added missing underscores in arch/ppc/lib/locks.c for __raw_read_trylock()
and __raw_read_lock().
Changed tlb->mm to tlb_mm(tlb) in include/asm-ppc/tlb.h.
Reverted change of dma_spin_lock in include/asm-ppc/dma.h from
raw_spinlock_t to spinlock_t to be consistent with kernel/dma.c.
This patch has been tested on the IBM PPC 405GP eval board only.
You might notice that this board is not an SMP board. A few small
changes were required to build an SMP kernel, even though only one cpu
is actually active.
The testing has included a short (~ten minute) stress test for sixteen
configuration permutations. The config files for the permutations are
in the attached tar in the following directories:
instrumentation off instrumentation on
---------------------- ----------------------
SMP=n SMP=y SMP=n SMP=y
---------- ---------- ---------- ----------
PREEMPT_NONE pn pn_smp lat_pn lat_pn_smp
PREEMPT_VOLUNTARY pv pv_smp lat_pv lat_pv_smp
PREEMPT_DESKTOP pd pd_smp lat_pd lat_pd_smp
PREEMPT_RT pr pr_smp lat_pr lat_pr_smp
Any comments, suggestions, needed changes, etc are welcome.
Thanks,
-Frank
--
Frank Rowand <frank_rowand@mvista.com>
MontaVista Software, Inc
[-- Attachment #2: config_tar.gz --]
[-- Type: application/x-gzip, Size: 7939 bytes --]
next reply other threads:[~2005-03-07 22:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-07 21:48 Frank Rowand [this message]
2005-03-16 10:09 ` [PATCH 0/5] ppc RT: Realtime preempt support for PPC Ingo Molnar
2005-03-16 15:30 ` K.R. Foley
2005-03-17 8:38 ` Ingo Molnar
2005-03-22 0:38 ` Frank Rowand
2005-03-31 1:36 ` Frank Rowand
2005-03-31 9:16 ` Ingo Molnar
2005-04-01 23:55 ` Frank Rowand
2005-04-05 5:39 ` Ingo Molnar
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=422CCC1D.1050902@mvista.com \
--to=frowand@mvista.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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