From: Kirill Tkhai <tkhai@yandex.ru>
To: Allen Pais <allen.pais@oracle.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: "sparclinux@vger.kernel.org" <sparclinux@vger.kernel.org>,
"bigeasy@linutronix.de" <bigeasy@linutronix.de>
Subject: Re: [PATCH 0/3] PREEMPT_RT support for Sparc64
Date: Mon, 30 Dec 2013 16:42:47 +0400 [thread overview]
Message-ID: <135961388407367@web19g.yandex.ru> (raw)
In-Reply-To: <1387166853-10782-1-git-send-email-allen.pais@oracle.com>
16.12.2013, 08:08, "Allen Pais" <allen.pais@oracle.com>:
> PREEMPT_RT support for Sparc64.
> I have tested it on UltraSparc T4 (Niagara4).
>
> Allen Pais (3):
> sparc64: use generic rwsem spinlocks rt
> sparc64: convert spinlock_t to raw_spinlock_t in mmu_context_t
> sparc64: convert ctx_alloc_lock raw_spinlock_t
>
> arch/sparc/Kconfig | 7 +++----
> arch/sparc/include/asm/mmu_64.h | 2 +-
> arch/sparc/include/asm/mmu_context_64.h | 10 +++++-----
> arch/sparc/kernel/smp_64.c | 4 ++--
> arch/sparc/mm/init_64.c | 14 +++++++-------
> arch/sparc/mm/tsb.c | 20 ++++++++++----------
> 6 files changed, 28 insertions(+), 29 deletions(-)
Works good on my 16 CPU sun4u.
Tested-by: Kirill Tkhai <tkhai@yandex.ru>
next prev parent reply other threads:[~2013-12-30 12:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-16 4:07 [PATCH 0/3] PREEMPT_RT support for Sparc64 Allen Pais
2013-12-16 4:07 ` [PATCH 1/3] sparc64: use generic rwsem spinlocks rt Allen Pais
2013-12-16 10:26 ` Sebastian Andrzej Siewior
2013-12-16 11:01 ` Allen Pais
2013-12-16 4:07 ` [PATCH 2/3] sparc64: convert spinlock_t to raw_spinlock_t in mmu_context_t Allen Pais
2013-12-16 10:28 ` Sebastian Andrzej Siewior
2013-12-16 10:59 ` Allen Pais
2014-01-05 1:32 ` David Miller
2014-01-06 3:35 ` Allen Pais
2013-12-16 10:59 ` Allen Pais
2013-12-16 4:07 ` [PATCH 3/3] sparc64: convert ctx_alloc_lock raw_spinlock_t Allen Pais
2013-12-30 12:42 ` Kirill Tkhai [this message]
2013-12-30 12:44 ` [PATCH 0/3] PREEMPT_RT support for Sparc64 Allen Pais
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=135961388407367@web19g.yandex.ru \
--to=tkhai@yandex.ru \
--cc=allen.pais@oracle.com \
--cc=bigeasy@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=sparclinux@vger.kernel.org \
/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).