From: guoren@kernel.org
To: palmerdabbelt@google.com, paul.walmsley@sifive.com,
anup@brainfault.org, zong.li@sifive.com, aou@eecs.berkeley.edu,
tglx@linutronix.de, tycho@tycho.ws, nickhu@andestech.com
Cc: linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
linux-csky@vger.kernel.org, Guo Ren <guoren@linux.alibaba.com>
Subject: [PATCH 0/3] riscv: Enable LOCKDEP
Date: Tue, 16 Jun 2020 15:56:58 +0000 [thread overview]
Message-ID: <1592323021-98541-1-git-send-email-guoren@kernel.org> (raw)
From: Guo Ren <guoren@linux.alibaba.com>
Lockdep is needed by proving the spinlocks and rwlocks. To suupport
it, we need fixup TRACE_IRQFLAGS_SUPPORT in kernel/entry.S. This
patch follow Documentation/irqflags-tracing.txt.
And there are 2 bugs block the lockdep implementation.
Guo Ren (2):
riscv: Fixup static_obj() fail
riscv: Enable LOCKDEP_SUPPORT & fixup TRACE_IRQFLAGS_SUPPORT
Zong Li (1):
riscv: Fixup lockdep_assert_held with wrong param cpu_running
arch/riscv/Kconfig | 3 +++
arch/riscv/kernel/entry.S | 41 ++++++++++++++++++++++++++++++++++++++++-
arch/riscv/kernel/smpboot.c | 1 -
arch/riscv/kernel/vmlinux.lds.S | 2 +-
4 files changed, 44 insertions(+), 3 deletions(-)
--
2.7.4
next reply other threads:[~2020-06-16 15:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-16 15:56 guoren [this message]
2020-06-16 15:56 ` [PATCH 1/3] riscv: Fixup static_obj() fail guoren
2020-06-16 15:57 ` [PATCH 2/3] riscv: Fixup lockdep_assert_held with wrong param cpu_running guoren
2020-06-16 15:57 ` [PATCH 3/3] riscv: Enable LOCKDEP_SUPPORT & fixup TRACE_IRQFLAGS_SUPPORT guoren
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=1592323021-98541-1-git-send-email-guoren@kernel.org \
--to=guoren@kernel.org \
--cc=anup@brainfault.org \
--cc=aou@eecs.berkeley.edu \
--cc=guoren@linux.alibaba.com \
--cc=linux-csky@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=nickhu@andestech.com \
--cc=palmerdabbelt@google.com \
--cc=paul.walmsley@sifive.com \
--cc=tglx@linutronix.de \
--cc=tycho@tycho.ws \
--cc=zong.li@sifive.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;
as well as URLs for NNTP newsgroup(s).