From: Zong Li <zong.li@sifive.com>
To: Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
rostedt@goodmis.org, Anup Patel <anup@brainfault.org>,
"linux-kernel@vger.kernel.org List"
<linux-kernel@vger.kernel.org>,
linux-riscv <linux-riscv@lists.infradead.org>
Subject: Re: [PATCH 0/2] RISC-V: fixes issues of ftrace graph tracer
Date: Thu, 2 Jan 2020 11:50:22 +0800 [thread overview]
Message-ID: <CANXhq0qTG-ezdrJpOEd9fhc-_iRL2syASO9KnQxbDfxoVXwfqQ@mail.gmail.com> (raw)
In-Reply-To: <20191223084614.67126-1-zong.li@sifive.com>
On Mon, Dec 23, 2019 at 4:46 PM Zong Li <zong.li@sifive.com> wrote:
>
> Ftrace graph tracer is broken now, these patches fix the problem of ftrace graph
> tracer and tested on QEMU and HiFive Unleashed board.
>
> Zong Li (2):
> riscv: ftrace: correct the condition logic in function graph tracer
> clocksource/drivers/riscv: add notrace to riscv_sched_clock
>
> arch/riscv/kernel/ftrace.c | 2 +-
> drivers/clocksource/timer-riscv.c | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
> --
> 2.24.1
>
ping
next prev parent reply other threads:[~2020-01-02 3:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-23 8:46 [PATCH 0/2] RISC-V: fixes issues of ftrace graph tracer Zong Li
2019-12-23 8:46 ` [PATCH 1/2] riscv: ftrace: correct the condition logic in function " Zong Li
2020-01-04 0:14 ` Paul Walmsley
2019-12-23 8:46 ` [PATCH 2/2] clocksource/drivers/riscv: add notrace to riscv_sched_clock Zong Li
2020-01-04 0:16 ` Paul Walmsley
2020-01-02 3:50 ` Zong Li [this message]
2020-01-02 15:14 ` [PATCH 0/2] RISC-V: fixes issues of ftrace graph tracer Steven Rostedt
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=CANXhq0qTG-ezdrJpOEd9fhc-_iRL2syASO9KnQxbDfxoVXwfqQ@mail.gmail.com \
--to=zong.li@sifive.com \
--cc=anup@brainfault.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=rostedt@goodmis.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).