From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: avorontsov@ru.mvista.com
Cc: linuxppc-dev@ozlabs.org, Steven Rostedt <srostedt@redhat.com>,
linux-kernel@vger.kernel.org, linux-rt-users@vger.kernel.org
Subject: Re: 2.6.28-rt on PowerPC
Date: Fri, 30 Jan 2009 13:11:50 +1100 [thread overview]
Message-ID: <1233281510.18767.17.camel@pasglop> (raw)
In-Reply-To: <20090129213429.GA29014@oksana.dev.rtsoft.ru>
> This is trivially solved by converting arch/powerpc/sysdev/ipic.c
> back to spinlocks (ipic_lock).
>
> Assuming that converting-back is automatic, there are few other
> chained interrupt controllers you might want to convert-back:
>
> arch/powerpc/sysdev/i8259.c (i8259_lock)
> arch/powerpc/sysdev/mpic.c (mpic_lock)
> arch/powerpc/sysdev/qe_lib/qe_ic.c (qe_ic_lock)
Except that a bunch of those can be both primary and chained... It's
simply not a solution to have to "convert" interrupt controller code to
use a different locking scheme depending on whether they are chained or
primary...
Cheers,
Ben.
WARNING: multiple messages have this Message-ID (diff)
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: avorontsov@ru.mvista.com
Cc: Steven Rostedt <srostedt@redhat.com>,
linuxppc-dev@ozlabs.org, linux-kernel@vger.kernel.org,
linux-rt-users@vger.kernel.org
Subject: Re: 2.6.28-rt on PowerPC
Date: Fri, 30 Jan 2009 13:11:50 +1100 [thread overview]
Message-ID: <1233281510.18767.17.camel@pasglop> (raw)
In-Reply-To: <20090129213429.GA29014@oksana.dev.rtsoft.ru>
> This is trivially solved by converting arch/powerpc/sysdev/ipic.c
> back to spinlocks (ipic_lock).
>
> Assuming that converting-back is automatic, there are few other
> chained interrupt controllers you might want to convert-back:
>
> arch/powerpc/sysdev/i8259.c (i8259_lock)
> arch/powerpc/sysdev/mpic.c (mpic_lock)
> arch/powerpc/sysdev/qe_lib/qe_ic.c (qe_ic_lock)
Except that a bunch of those can be both primary and chained... It's
simply not a solution to have to "convert" interrupt controller code to
use a different locking scheme depending on whether they are chained or
primary...
Cheers,
Ben.
next prev parent reply other threads:[~2009-01-30 2:12 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-29 21:34 2.6.28-rt on PowerPC Anton Vorontsov
2009-01-29 21:34 ` Anton Vorontsov
2009-01-29 23:00 ` Steven Rostedt
2009-01-29 23:00 ` Steven Rostedt
2009-01-29 23:00 ` Steven Rostedt
2009-01-29 23:00 ` Steven Rostedt
2009-01-29 23:21 ` Frank Rowand
2009-01-29 23:21 ` Frank Rowand
2009-01-30 1:51 ` Steven Rostedt
2009-01-30 1:51 ` Steven Rostedt
2009-01-30 23:06 ` Robert Schwebel
2009-01-30 23:06 ` Robert Schwebel
2009-01-31 20:23 ` 2.6.28-rt on ARM [Was: 2.6.28-rt on PowerPC] Uwe Kleine-König
2009-01-31 20:23 ` Uwe Kleine-König
2009-01-30 23:06 ` 2.6.28-rt on PowerPC Robert Schwebel
2009-01-30 23:06 ` Robert Schwebel
2009-01-30 23:06 ` Robert Schwebel
2009-01-30 13:07 ` Josh Boyer
2009-01-30 13:07 ` Josh Boyer
2009-01-30 17:45 ` Anton Vorontsov
2009-01-30 17:45 ` Anton Vorontsov
2009-01-30 17:57 ` Steven Rostedt
2009-01-30 17:57 ` Steven Rostedt
2009-01-30 17:57 ` Steven Rostedt
2009-01-30 17:57 ` Steven Rostedt
2009-01-31 19:14 ` [PATCH -rt] powerpc/tracing: Add support for "PREEMPT_TRACE" tracer Anton Vorontsov
2009-01-31 19:14 ` Anton Vorontsov
2009-01-30 17:57 ` 2.6.28-rt on PowerPC Steven Rostedt
2009-01-29 23:00 ` Steven Rostedt
2009-01-30 2:11 ` Benjamin Herrenschmidt
2009-01-30 2:11 ` Benjamin Herrenschmidt [this message]
2009-01-30 2:11 ` Benjamin Herrenschmidt
2009-01-30 3:07 ` Anton Vorontsov
2009-01-30 3:07 ` Anton Vorontsov
2009-01-30 4:09 ` Benjamin Herrenschmidt
2009-01-30 4:09 ` Benjamin Herrenschmidt
2009-01-30 4:09 ` Benjamin Herrenschmidt
2009-01-30 4:09 ` Benjamin Herrenschmidt
2009-01-30 4:09 ` Benjamin Herrenschmidt
2009-01-30 2:11 ` Benjamin Herrenschmidt
2009-01-30 2:11 ` Benjamin Herrenschmidt
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=1233281510.18767.17.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=avorontsov@ru.mvista.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=srostedt@redhat.com \
/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.