From: Matthew Wilcox <willy@debian.org>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] [patch] 2.4.20 ia64_sal_mc_rendez must not lock
Date: Sat, 22 Mar 2003 13:03:57 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590723705291@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590723705290@msgid-missing>
On Sat, Mar 22, 2003 at 03:51:54PM +1100, Keith Owens wrote:
> No cpu will return from ia64_sal_mc_rendez() until all cpus have
> entered rendezvous and the monarch cpu sends the wake up ipi. All cpus
> try to call ia64_sal_mc_rendez() but only the first one makes it, the
> others all block on the spinlock and eventually SAL hits them with an
> INIT.
>
> Why do I get the feeling that I am the first person to really use this
> code?
Maybe this is (in part) what's causing
https://lists.linuxia64.org/archives/linux-ia64/2002-August/003876.html
Apparently the reason it hangs is that I leave my console at the default
9600 baud (you know, like a customer would ..) and when dumping state
it takes so long that the system assumes the CPU has hung. Bag o' shite.
--
"It's not Hollywood. War is real, war is primarily not about defeat or
victory, it is about death. I've seen thousands and thousands of dead bodies.
Do you think I want to have an academic debate on this subject?" -- Robert Fisk
next prev parent reply other threads:[~2003-03-22 13:03 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 [this message]
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
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-105590723705291@msgid-missing \
--to=willy@debian.org \
--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.