From: Vincent Chen <vincentc@andestech.com>
To: <palmer@sifive.com>, <aou@eecs.berkeley.edu>,
<ebiederm@xmission.com>, <jimw@sifive.com>, <arnd@arndb.de>,
<linux-riscv@lists.infradead.org>, <linux-kernel@vger.kernel.org>
Cc: <deanbo422@gmail.com>, <vincentc@andestech.com>
Subject: [PATCH 0/3] riscv: Fix debug instruction check and support trap-based WARN()
Date: Thu, 28 Feb 2019 18:31:28 +0800 [thread overview]
Message-ID: <1551349891-22683-1-git-send-email-vincentc@andestech.com> (raw)
The handler for the debug exception will call is_valid_bugaddr(bugaddr) to
check if the instruction in bugaddr is a real debug instruction. However,
the expected instruction, ebreak, is possibly translated to c.ebreak by
assmebler when C extension is supported. This patchset will add c.ebreak
into the check mechanism. In addition, BUG() is currently unable to work in
the kernel module due to an inappropriated condition in is_valid_bugaddr().
This issue will be fixed in this patchset. Finally, this patchset enables
WARN() related functions to trap the code to help developers debug it.
Vincent Chen (3):
riscv: Add the support for c.ebreak check in is_valid_bugaddr()
riscv: Support BUG() in kernel module
riscv: Make WARN() related functions able to trigger a trap exception
next reply other threads:[~2019-02-28 10:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-28 10:31 Vincent Chen [this message]
2019-02-28 10:31 ` [PATCH 1/3] riscv: Add the support for c.ebreak check in is_valid_bugaddr() Vincent Chen
2019-02-28 10:31 ` [PATCH 2/3] riscv: Support BUG() in kernel module Vincent Chen
2019-02-28 10:31 ` [PATCH 3/3] riscv: Make WARN() related functions able to trigger a trap exception Vincent Chen
2019-03-04 20:35 ` [PATCH 0/3] riscv: Fix debug instruction check and support trap-based WARN() Palmer Dabbelt
2019-03-05 0:21 ` Vincent Chen
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=1551349891-22683-1-git-send-email-vincentc@andestech.com \
--to=vincentc@andestech.com \
--cc=aou@eecs.berkeley.edu \
--cc=arnd@arndb.de \
--cc=deanbo422@gmail.com \
--cc=ebiederm@xmission.com \
--cc=jimw@sifive.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@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
all inboxes | Powered by JetHome®