From: Zong Li <zong.li@sifive.com>
To: corbet@lwn.net, paul.walmsley@sifive.com, palmer@dabbelt.com,
aou@eecs.berkeley.edu, anup@brainfault.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-riscv@lists.infradead.org
Cc: Zong Li <zong.li@sifive.com>
Subject: [PATCH v2 0/2] Enable gcov for RISC-V
Date: Thu, 2 Jan 2020 12:14:43 +0800 [thread overview]
Message-ID: <20200102041445.98195-1-zong.li@sifive.com> (raw)
These patches enable GCOV code coverage measurement on RISC-V and update
the status of RISC-V arch in documentation.
Lightly tested on QEMU and Hifive Unleashed board, seems to work as
expected.
Changes in v2:
- Split into two patches for kconfig and documentation respectively.
Zong Li (2):
riscv: gcov: enable gcov for RISC-V
Documentation/features: support gcov on RISC-V
Documentation/features/debug/gcov-profile-all/arch-support.txt | 2 +-
arch/riscv/Kconfig | 1 +
2 files changed, 2 insertions(+), 1 deletion(-)
--
2.24.1
next reply other threads:[~2020-01-02 4:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-02 4:14 Zong Li [this message]
2020-01-02 4:14 ` [PATCH 1/2] riscv: gcov: enable gcov for RISC-V Zong Li
2020-01-02 4:14 ` [PATCH 2/2] Documentation/features: support gcov on RISC-V Zong Li
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=20200102041445.98195-1-zong.li@sifive.com \
--to=zong.li@sifive.com \
--cc=anup@brainfault.org \
--cc=aou@eecs.berkeley.edu \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@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).