From: William Lee Irwin III <wli@holomorphy.com>
To: sparclinux@vger.kernel.org
Subject: Re: Patch - Sun4d SMP now boots
Date: Thu, 19 Aug 2004 14:12:13 +0000 [thread overview]
Message-ID: <20040819141213.GM11200@holomorphy.com> (raw)
In-Reply-To: <Pine.LNX.4.53.0408191358400.2910@mailgate.netunix.com>
On Thu, Aug 19, 2004 at 02:32:47PM +0100, Chris Newport wrote:
> I have now applied the patch posted to the list by Pasi Pirhonen
> on 19Nov2003. This needs to be applied AFTER the patches from Thomas.
> More work is needed to get rid of the previously reported compiler
> warnings in the same function before this is fit to be submitted, but
> I will have to leave that to those who understand what they are doing
> <B-).
> This now boots and runs, but is horribly unstable.
Okay, this is great news. I know the spin_lock_bh() is wrong, but it
gets us to a point where we can actually do something and we actually
have enough to reproduce all this.
One major question is *WHY* spin_lock_bh() vs. spin_lock_irqsave()
works. Only trouble there is that we can't see what happens after
spin_lock_irqsave() very easily. One rather large possibility is that
since disabling bh's doesn't disable interrupts, some smp_call_function()
or similar that would deadlock if interrupts weren't disabled suddenly
appears to work and/or works for some limited cases...
This is in my queue also, though preferably some explanation of what's
going on with this (e.g. the real issue, maybe a better fix) will
happen instead.
-- wli
next prev parent reply other threads:[~2004-08-19 14:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-19 13:32 Patch - Sun4d SMP now boots Chris Newport
2004-08-19 14:12 ` William Lee Irwin III [this message]
2004-08-19 14:33 ` David S. Miller
2004-08-19 14:49 ` C.Newport
2004-08-19 15:00 ` William Lee Irwin III
2004-08-19 15:22 ` C.Newport
2004-08-19 15:29 ` William Lee Irwin III
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=20040819141213.GM11200@holomorphy.com \
--to=wli@holomorphy.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.