From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] [patch] 2.4.20 ia64_sal_mc_rendez must not lock
Date: Mon, 24 Mar 2003 21:54:56 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590723705306@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590723705290@msgid-missing>
I made the analogous change in 2.5 (patch didn't apply due to some
other changes). Also, I changed the local variable names in the
macros to avoid name collisions.
--david
>>>>> On Sat, 22 Mar 2003 15:51:54 +1100, Keith Owens <kaos@sgi.com> said:
Keith> No cpu will return from ia64_sal_mc_rendez() until all cpus have
Keith> entered rendezvous and the monarch cpu sends the wake up ipi. All cpus
Keith> try to call ia64_sal_mc_rendez() but only the first one makes it, the
Keith> others all block on the spinlock and eventually SAL hits them with an
Keith> INIT.
Keith> Why do I get the feeling that I am the first person to really use this
Keith> code?
Keith> With this patch and my previous patch to set
Keith> SAL_MC_PARAM_RZ_ALWAYS, kdb v4.0 gets backtrace on _ALL_ cpus
Keith> when an MCA occurs. Well, almost all, if any of the cpus are
Keith> spinning disabled then the MCA rendezvous interrupt does not
Keith> get through, SAL sends INIT and that cpu drops into INIT
Keith> processing. kdb processing for INIT handlers is not complete
Keith> yet, work in progress.
prev parent reply other threads:[~2003-03-24 21:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-22 4:51 [Linux-ia64] [patch] 2.4.20 ia64_sal_mc_rendez must not lock Keith Owens
2003-03-22 13:03 ` Matthew Wilcox
2003-03-22 15:43 ` Keith Owens
2003-03-24 19:53 ` David Mosberger
2003-03-24 20:06 ` Luck, Tony
2003-03-24 21:54 ` David Mosberger [this message]
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=marc-linux-ia64-105590723705306@msgid-missing \
--to=davidm@napali.hpl.hp.com \
--cc=linux-ia64@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.