public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier.adi@gmail.com>
To: Ingo Molnar <mingo@redhat.com>
Cc: Linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: adding lockdep support to the Blackfin arch
Date: Mon, 8 Jun 2009 19:28:19 -0400	[thread overview]
Message-ID: <8bd0f97a0906081628o7d30e05ld961c00a690c140d@mail.gmail.com> (raw)

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);

btw, in order to get this to work in the first place, i had to extend
-mike

             reply	other threads:[~2009-06-08 23:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-08 23:28 Mike Frysinger [this message]
2009-06-08 23:36 ` adding lockdep support to the Blackfin arch Mike Frysinger
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=8bd0f97a0906081628o7d30e05ld961c00a690c140d@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