Alpha arch development list
 help / color / mirror / Atom feed
From: Matt Turner <mattst88@gmail.com>
To: linux-alpha@vger.kernel.org
Cc: linux-kernel@vger.kernel.org,
	Richard Henderson <richard.henderson@linaro.org>,
	Magnus Lindholm <linmag7@gmail.com>,
	Ivan Kokshaysky <ink@unseen.parts>,
	Matt Turner <mattst88@gmail.com>
Subject: [PATCH 0/3] alpha SMP fixes for EV7/Marvel
Date: Sat, 30 May 2026 16:25:41 -0400	[thread overview]
Message-ID: <20260530202544.59231-1-mattst88@gmail.com> (raw)

I acquired an AlphaServer ES47 in 2010, and it's never been stable --
deadlocking after random amounts of time. I could never make any
connections with load, uptime, etc.

The only dots I could connect was that the git test suite would always
trigger the deadlock.

I spent some time over the last week playing with Claude and have found
*a* solution. With the first two patches in place, I've successfully run
the git test suite 6 times in a row. I've never previously seen it run
successfully without deadlocking the system.

The first patch is generally applicable (not specific to EV7/Marvel).
I'm unsure why this would never have caused problems on other systems
(or why it would only be relevant for EV7/Marvel). That gives me some
pause.

The second patch applies only to EV7/Marvel, I believe. tl;dr: IPIs seem
to be lost.

The third patch adds some accounting to /proc/interrupts to report the
number of lost interrupts, confirming the problem from patch 2.

Please review.

Matt

Matt Turner (3):
  alpha: smp: Serialize all synchronous IPI operations to fix SMP
    deadlock
  alpha: Fix SMP IPI loss when target CPU is in interrupt handler
  alpha: Break down rescued IPI counter by type in /proc/interrupts

 arch/alpha/include/asm/smp.h  | 12 +++++
 arch/alpha/kernel/irq.c       | 12 +++++
 arch/alpha/kernel/irq_alpha.c | 29 ++++++++++-
 arch/alpha/kernel/proto.h     |  1 +
 arch/alpha/kernel/smp.c       | 97 +++++++++++++++++++++++++++++++++++
 arch/alpha/mm/tlbflush.c      |  3 ++
 6 files changed, 153 insertions(+), 1 deletion(-)

-- 
2.53.0


             reply	other threads:[~2026-05-30 20:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-30 20:25 Matt Turner [this message]
2026-05-30 20:25 ` [PATCH 1/3] alpha: smp: Serialize all synchronous IPI operations to fix SMP deadlock Matt Turner
2026-05-30 20:25 ` [PATCH 2/3] alpha: Fix SMP IPI loss when target CPU is in interrupt handler Matt Turner
2026-05-30 20:25 ` [PATCH 3/3] alpha: Break down rescued IPI counter by type in /proc/interrupts Matt Turner
2026-05-31  8:24 ` [PATCH 0/3] alpha SMP fixes for EV7/Marvel Magnus Lindholm

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=20260530202544.59231-1-mattst88@gmail.com \
    --to=mattst88@gmail.com \
    --cc=ink@unseen.parts \
    --cc=linmag7@gmail.com \
    --cc=linux-alpha@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=richard.henderson@linaro.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox