From: Benjamin Herrenschmidt <benh@ozlabs.org>
To: <linuxppc-dev@ozlabs.org>
Subject: [PATCH 0/4] [POWERPC] lockdep support for ppc64
Date: Wed, 02 Apr 2008 18:52:08 +1100 [thread overview]
Message-ID: <1207122728.672673.111194574046.qpush@grosgo> (raw)
[Not to merge just yet ... almost]
This serie of patches adds lockdep support for 64 bits
powerpc. Dale's patch for 32 bits still need me to review
and test it which I'll try to do asap.
It needs the iSeries hardirq enable fix that I posted
earlier (which is probably 2.6.25 material).
Note that we can already see potential problems exposed
by it. So far on my list:
- something wrong with iseries veth. Haven't got to figure
out what yet, could be a false positive
- possible deadlock with the device-tree rwlock. The one that
I caught with lockdep here is pSeries rtas_set_rtc_time() calls
rtas_token() from softirq, which does on of_find_property(),
which takes the read lock. Other things can call prom_add_propety()
which can take the write lock, while softirqs are enabled -> boom.
Maybe we should forbid OF device-tree access from IRQs and thus
things that need to use rtas_token() will have to cache the token.
next reply other threads:[~2008-04-02 7:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-02 7:52 Benjamin Herrenschmidt [this message]
2008-04-02 7:52 ` [PATCH 1/4] [POWERPC] Initialize paca->current earlier Benjamin Herrenschmidt
2008-04-02 12:30 ` Stephen Rothwell
2008-04-02 7:52 ` [PATCH 2/4] [POWERPC] lockdep stacktrace support Benjamin Herrenschmidt
2008-04-02 12:29 ` Stephen Rothwell
2008-04-02 7:52 ` [PATCH 3/4] [POWERPC] Fixup softirq preempt count Benjamin Herrenschmidt
2008-04-02 7:52 ` [PATCH 4/4] [POWERPC] irqtrace support to 64-bit powerpc Benjamin Herrenschmidt
2008-04-02 9:50 ` [PATCH 0/4] [POWERPC] lockdep support for ppc64 Johannes Berg
2008-04-02 11:02 ` Benjamin Herrenschmidt
2008-04-02 13:20 ` Johannes Berg
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=1207122728.672673.111194574046.qpush@grosgo \
--to=benh@ozlabs.org \
--cc=linuxppc-dev@ozlabs.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;
as well as URLs for NNTP newsgroup(s).