From: Daniel Hellstrom <daniel@gaisler.com>
To: sparclinux@vger.kernel.org
Subject: Re: [PATCH 6/7] sparc32,leon: operate on boot-cpu IRQ controller
Date: Wed, 20 Apr 2011 07:02:16 +0000 [thread overview]
Message-ID: <4DAE84F8.9040901@gaisler.com> (raw)
In-Reply-To: <1303229239-21551-6-git-send-email-daniel@gaisler.com>
Sam Ravnborg wrote:
>On Tue, Apr 19, 2011 at 06:07:18PM +0200, Daniel Hellstrom wrote:
>
>
>>Each CPU has a separate set of IRQ controller registers, this
>>patch makes sure that the boot-cpu registers are used instead
>>of CPU0's. Note that there are other parts of the SPARC32/LEON
>>port which does not support booting on other than CPU0 anyway,
>>however this this cleans up the IRQ controller layer in that
>>regard.
>>
>>Signed-off-by: Daniel Hellstrom <daniel@gaisler.com>
>>---
>> arch/sparc/include/asm/leon.h | 1 +
>> arch/sparc/kernel/leon_kernel.c | 14 ++++++++------
>> 2 files changed, 9 insertions(+), 6 deletions(-)
>>
>>diff --git a/arch/sparc/include/asm/leon.h b/arch/sparc/include/asm/leon.h
>>index 31fb2ac..1776f71 100644
>>--- a/arch/sparc/include/asm/leon.h
>>+++ b/arch/sparc/include/asm/leon.h
>>@@ -335,6 +335,7 @@ extern int leon_flush_needed(void);
>> extern void leon_switch_mm(void);
>> extern int srmmu_swprobe_trace;
>> extern int leon3_ticker_irq;
>>+extern int leon3_boot_cpu;
>>
>>
>
>We already have boot_cpu_id - defiend in smp_32.c.
>Could it be used rather than a leon specific variable?
>
>We would need to define boot_cpu_id also in the non-SMP case
>to do so - but this could also clean up code
>in sun4d_irq.
>
>
Yes, it might remove a ifdef to the expence of a bigger footprint.
>Note: leon actually set this variable in head_32.S already.
>
>
I agree that it would be nicer, however I think the SUNs will never be
booted on CPU1 anyway? Anyways, I think this should go into another
patch series. I'm very interested in supporting booting on CPU1 for
LEON, that is really nice in AMP systems where for example RTEMS is
running on CPU0 and Linux on CPU1. Today RTEMS supports running on
CPU!=0, so it is not a big issue right now but is not very flexible.
As I state in the comment this patch does not aim to fix everything just
parts of the IRQ Controller code, there are a lot of other stuff that
needs to be done in order to support this, not only in Linux the PROM as
well. I plan to come back later with a patch set for this.
Sam, is that acceptable for now?
Daniel
next prev parent reply other threads:[~2011-04-20 7:02 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-19 16:07 [PATCH 6/7] sparc32,leon: operate on boot-cpu IRQ controller registers Daniel Hellstrom
2011-04-19 18:47 ` [PATCH 6/7] sparc32,leon: operate on boot-cpu IRQ controller Sam Ravnborg
2011-04-20 7:02 ` Daniel Hellstrom [this message]
2011-04-20 7:39 ` crn
2011-04-20 8:12 ` Daniel Hellstrom
2011-04-20 8:15 ` David Miller
2011-04-20 8:35 ` Daniel Hellstrom
2011-04-20 8:39 ` David Miller
2011-04-20 8:44 ` Daniel Hellstrom
2011-04-20 8:45 ` David Miller
2011-04-20 8:46 ` crn
2011-04-20 9:06 ` Sam Ravnborg
2011-04-20 9:38 ` Josip Rodin
2011-04-20 10:44 ` Sam Ravnborg
2011-04-20 10:47 ` Daniel Hellstrom
2011-04-20 11:25 ` Daniel Hellstrom
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=4DAE84F8.9040901@gaisler.com \
--to=daniel@gaisler.com \
--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 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.