From: Mike Frysinger <vapier.adi@gmail.com>
To: Ingo Molnar <mingo@redhat.com>
Cc: Linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: adding lockdep support to the Blackfin arch
Date: Mon, 8 Jun 2009 19:36:09 -0400 [thread overview]
Message-ID: <8bd0f97a0906081636p760f190cue9ef01454658dd46@mail.gmail.com> (raw)
In-Reply-To: <8bd0f97a0906081628o7d30e05ld961c00a690c140d@mail.gmail.com>
On Mon, Jun 8, 2009 at 19:28, Mike Frysinger wrote:
> ive been extending the Blackfin arch recently to support lockdep.
> since i also had to implement irqflags/stacktrace as well, i wouldnt
> be surprised if this issue is nested in there, plus this is a no-mmu
> system.
>
> at any rate, when i boot up a Blackfin system with PROVE_LOCKING
> enabled, i end up with this warning:
> Badness at kernel/fork.c:988
>
> which correlates to this in copy_process():
> DEBUG_LOCKS_WARN_ON(!p->hardirqs_enabled);
sorry, stupid stuck keys triggered gmail sending before i finished
when i trace the code, i can see hardirqs_enabled toggling between 0
and 1 ... but when it makes it to copy_process(), apparently it's 0
which annoys the lockdep code. any tips for me ?
btw, in order to get this to work in the first place, i had to extend
kernel/lockdep.c's static_obj() function as the Blackfin has custom
data regions where some locks live (thus outside of the normal
start/end map). should this code use kallsyms' helper functions
instead ? otherwise, i needed this:
--- a/kernel/lockdep.c
+++ b/kernel/lockdep.c
@@ -634,6 +634,27 @@ static int static_obj(void *obj)
if ((addr >= start) && (addr < end))
return 1;
+#ifdef CONFIG_BLACKFIN
+ if (L1_DATA_A_LENGTH) {
+ start = (unsigned long) &_sdata_l1;
+ end = (unsigned long) &_ebss_l1;
+ if ((addr >= start) && (addr < end))
+ return 1;
+ }
+ if (L1_DATA_B_LENGTH) {
+ start = (unsigned long) &_sdata_b_l1;
+ end = (unsigned long) &_ebss_b_l1;
+ if ((addr >= start) && (addr < end))
+ return 1;
+ }
+ if (L2_LENGTH) {
+ start = (unsigned long) &_sdata_l2;
+ end = (unsigned long) &_ebss_l2;
+ if ((addr >= start) && (addr < end))
+ return 1;
+ }
+#endif
+
#ifdef CONFIG_SMP
/*
* percpu var?
-mike
next prev parent reply other threads:[~2009-06-08 23:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-08 23:28 Mike Frysinger
2009-06-08 23:36 ` Mike Frysinger [this message]
2009-06-09 6:32 ` Ingo Molnar
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=8bd0f97a0906081636p760f190cue9ef01454658dd46@mail.gmail.com \
--to=vapier.adi@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
/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
all inboxes | Powered by JetHome®