All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Hellstrom <daniel@gaisler.com>
To: sparclinux@vger.kernel.org
Subject: [PATCH 0/4 v2] sparc32: SMP IPI patches
Date: Mon, 02 May 2011 10:07:49 +0000	[thread overview]
Message-ID: <4DBE8275.5060604@gaisler.com> (raw)

Hello Dave,

I have made a new set of IPI patches, this time it includes patches for 
all SPARC32 architectures. It looks to me as if sun4d does not have a 
pending soft-IRQ register, so I handle it as a normal hard IRQ.

I'm not sure if I should add a STBAR/memory barrier or a spinlock to the 
sun4d implementation of smp4d_ipi_{single,mask_one,resched}. I'm a bit 
worried that the memory write happens after the IPI is generated to the 
other CPUs. Also, I'm not sure that IRQ14 is the best choice for IPI, 
the best is probably of put it on a separate IRQ but I don't know if 
there are free IRQs.

I hope that someone could try SMP on sun4m and sun4d with these patches.

Thanks,
Daniel

---

 arch/sparc/Kconfig                  |    3 +-
 arch/sparc/include/asm/cpudata_32.h |    5 ++
 arch/sparc/include/asm/leon.h       |    4 +-
 arch/sparc/include/asm/smp_32.h     |   22 +++----
 arch/sparc/kernel/entry.S           |   45 +++++++++++++-
 arch/sparc/kernel/irq.h             |    6 ++
 arch/sparc/kernel/irq_32.c          |   10 +++
 arch/sparc/kernel/leon_smp.c        |  109 
++++++++++++++++++++++++++++++++++-
 arch/sparc/kernel/smp_32.c          |   52 +++++++++++++++--
 arch/sparc/kernel/sun4d_irq.c       |    9 +++
 arch/sparc/kernel/sun4d_smp.c       |   79 +++++++++++++++++++++++++
 arch/sparc/kernel/sun4m_smp.c       |   29 +++++++++
 12 files changed, 345 insertions(+), 28 deletions(-)


             reply	other threads:[~2011-05-02 10:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-02 10:07 Daniel Hellstrom [this message]
2011-05-16 20:08 ` [PATCH 0/4 v2] sparc32: SMP IPI patches David Miller
2011-05-19 10:18 ` 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=4DBE8275.5060604@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.