From: Palmer Dabbelt <palmerdabbelt@google.com>
To: guoren@kernel.org
Cc: Paul Walmsley <paul.walmsley@sifive.com>,
anup@brainfault.org, greentime.hu@sifive.com, zong.li@sifive.com,
aou@eecs.berkeley.edu, tglx@linutronix.de, tycho@tycho.ws,
nickhu@andestech.com, linux-riscv@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-csky@vger.kernel.org,
guoren@linux.alibaba.com
Subject: Re: [PATCH V2 0/3] riscv: Enable LOCKDEP
Date: Thu, 09 Jul 2020 15:06:42 -0700 (PDT) [thread overview]
Message-ID: <mhng-af022fcc-7dce-4d1b-9204-d31241538412@palmerdabbelt-glaptop1> (raw)
In-Reply-To: <1593266228-61125-1-git-send-email-guoren@kernel.org>
On Sat, 27 Jun 2020 06:57:05 PDT (-0700), guoren@kernel.org wrote:
> From: Guo Ren <guoren@linux.alibaba.com>
>
> Lockdep is needed by proving the spinlocks and rwlocks. To support it,
> we need to add TRACE_IRQFLAGS codes in kernel/entry.S. These patches
> follow Documentation/irqflags-tracing.txt.
>
> Fixup 2 bugs that block the lockdep implementation.
>
> ---
> Changes in v2
> - Remove sX regs recovery codes which are unnecessary, because
> callee will handle them. Thx Greentime :)
>
> - Move "restore a0 - a7" to handle_syscall, but if _TIF_SYSCALL_WORK
> is set, "restore a1 - a7" is still duplicated. I prefer a C wrapper
> for syscall.
>
> 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 | 33 ++++++++++++++++++++++++++++++++-
> arch/riscv/kernel/smpboot.c | 1 -
> arch/riscv/kernel/vmlinux.lds.S | 2 +-
> 4 files changed, 36 insertions(+), 3 deletions(-)
These are on for-next. As far as I can tell lockdep is working, but I'm just
doing some simple boot tests.
Thanks!
next prev parent reply other threads:[~2020-07-09 22:06 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-27 13:57 [PATCH V2 0/3] riscv: Enable LOCKDEP guoren
2020-06-27 13:57 ` [PATCH V2 1/3] riscv: Fixup static_obj() fail guoren
2020-09-11 20:45 ` Aurelien Jarno
2020-09-12 2:39 ` Guo Ren
2020-09-14 10:38 ` Aurelien Jarno
2020-09-24 7:36 ` Andreas Schwab
2020-09-24 16:19 ` Guo Ren
2020-09-29 18:51 ` Aurelien Jarno
2020-10-05 19:14 ` Atish Patra
2020-10-06 16:46 ` Guo Ren
2020-10-06 20:38 ` Atish Patra
2020-10-07 14:45 ` Guo Ren
2020-10-05 8:25 ` Andreas Schwab
2020-10-05 16:39 ` Palmer Dabbelt
2020-10-05 18:40 ` Andreas Schwab
2020-10-05 19:45 ` Palmer Dabbelt
2020-10-05 21:12 ` Atish Patra
2020-10-05 21:17 ` Palmer Dabbelt
2020-10-06 16:55 ` Guo Ren
2020-06-27 13:57 ` [PATCH V2 2/3] riscv: Fixup lockdep_assert_held with wrong param cpu_running guoren
2020-09-29 22:12 ` Atish Patra
2020-06-27 13:57 ` [PATCH V2 3/3] riscv: Enable LOCKDEP_SUPPORT & fixup TRACE_IRQFLAGS_SUPPORT guoren
2020-07-09 22:06 ` Palmer Dabbelt [this message]
2020-07-09 23:15 ` [PATCH V2 0/3] riscv: Enable LOCKDEP Guo Ren
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=mhng-af022fcc-7dce-4d1b-9204-d31241538412@palmerdabbelt-glaptop1 \
--to=palmerdabbelt@google.com \
--cc=anup@brainfault.org \
--cc=aou@eecs.berkeley.edu \
--cc=greentime.hu@sifive.com \
--cc=guoren@kernel.org \
--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=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).