All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Hellstrom <daniel@gaisler.com>
To: sparclinux@vger.kernel.org
Subject: Re: LEON SMP
Date: Wed, 05 Jan 2011 11:19:28 +0000	[thread overview]
Message-ID: <4D2453C0.3090506@gaisler.com> (raw)
In-Reply-To: <4CC714EC.2050001@gaisler.com>

Sam Ravnborg wrote:

>>I have started working on this timer patch again...
>>
>>I tried looking a sun4d and sun4m to get an example of how to implement  
>>this in a better way, however they seem to implement the per-cpu ticker  
>>using hardcoded IRQ number 14 and a custom trap handler for the per-cpu  
>>timer ticker (see bottom of kernel/sun4m_irq.c: sun4m_init_timers()).
>>    
>>
>
>I am slowly looking into introducing generic IRQ support for SPARC.
>If I succeed then we will shift to a more dynamic numbering
>of interrupts - like sparc64 does.
>  
>
That would be great. I have not looked so much into the other SPARC32 
ports or the SPARC64, however the LEON port handles IRQ always on the 
CPU calling request_irq(), since CPU0 initializes everything during 
startup CPU0 will end up doing a lot if IRQ work. I wish there where a 
way of implementing IRQ routing to different CPUs. In best case during 
runtime, however a static configuration is good enough.

>Right now I am in a situation where I try to analyse SPARC, existing
>codebase and genirq in the kernel. So it will take
>a while before I get anywhere with this.
>  
>
I understand, I'm appreciating your efforts.

Daniel


  parent reply	other threads:[~2011-01-05 11:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-26 17:50 LEON SMP Daniel Hellstrom
2010-10-26 17:54 ` David Miller
2010-10-26 18:11 ` Daniel Hellstrom
2011-01-05 10:20 ` Daniel Hellstrom
2011-01-05 10:48 ` Sam Ravnborg
2011-01-05 11:19 ` Daniel Hellstrom [this message]
2011-01-05 21:27 ` David Miller

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=4D2453C0.3090506@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.