All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Hellstrom <daniel@gaisler.com>
To: sparclinux@vger.kernel.org
Subject: Re: [PATCH 1/2 v2] sparc32: implement SMP IPIs using the generic
Date: Thu, 03 Feb 2011 08:50:05 +0000	[thread overview]
Message-ID: <4D4A6C3D.8070608@gaisler.com> (raw)
In-Reply-To: <1296675656-19165-1-git-send-email-daniel@gaisler.com>

David Miller wrote:

>From: Daniel Hellstrom <daniel@gaisler.com>
>Date: Wed,  2 Feb 2011 20:40:55 +0100
>
>  
>
>>The current sparc32 SMP IPI generation is implemented the
>>cross call function. The cross call function uses IRQ15 the
>>NMI, this is has the effect that IPIs will interrupt IRQ
>>critical areas and hang the system. Typically on/after
>>spin_lock_irqsave calls can be aborted.
>>
>>The cross call functionality must still exist to flush
>>cache/TLBS.
>>
>>This patch provides CPU models a custom way to implement
>>generation of IPIs on the generic code's request. The
>>typical approach is to generate an IRQ for each IPI case.
>>
>>After this patch each sparc32 SMP CPU model needs to
>>implement IPIs in order to function properly.
>>
>>Signed-off-by: Daniel Hellstrom <daniel@gaisler.com>
>>    
>>
>
>Ok, this looks mostly fine to me.
>
>Once we have the sun4m/sun4d versions written I can think about
>applying this.
>
>We might want to abstract out the common code of the dispatch and
>service stuff you have for LEON, otherwise we'll have 3 copies of
>that code that sets and clears the mask state.
>
>Perhaps something using BTFIXUP or similar.
>  
>
I was thinking so too, BTFIXUPs for CPU model specific "IPI operations" 
to avoid the switch-statement in the arch_ functions.

Daniel


  parent reply	other threads:[~2011-02-03  8:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-02 19:40 [PATCH 1/2 v2] sparc32: implement SMP IPIs using the generic functions Daniel Hellstrom
2011-02-03  8:38 ` [PATCH 1/2 v2] sparc32: implement SMP IPIs using the generic David Miller
2011-02-03  8:50 ` Daniel Hellstrom [this message]
2011-02-03  8:51 ` David Miller
2011-04-27 13:07 ` 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=4D4A6C3D.8070608@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.