From: Leo Liang <ycliang@andestech.com>
To: Heinrich Schuchardt <heinrich.schuchardt@canonical.com>
Cc: Rick Chen <rick@andestech.com>,
Anup Patel <apatel@ventanamicro.com>,
Xiang W <merlew4n6@gmail.com>,
Chanho Park <chanho61.park@samsung.com>,
Sughosh Ganu <sughosh.ganu@linaro.org>, <u-boot@lists.denx.de>
Subject: Re: [PATCH v3 1/2] riscv: allow resume after exception
Date: Wed, 1 Nov 2023 16:55:57 +0800 [thread overview]
Message-ID: <ZUISnaQbphUmV_RF@swlinux02> (raw)
In-Reply-To: <20231031125552.26698-2-heinrich.schuchardt@canonical.com>
On Tue, Oct 31, 2023 at 02:55:51PM +0200, Heinrich Schuchardt wrote:
> If CSRs like seed are readable by S-mode, may not be determinable by
> S-mode. For safe driver probing allow to resume via a longjmp after an
> exception.
>
> Signed-off-by: Heinrich Schuchardt <heinrich.schuchardt@canonical.com>
> ---
> v3:
> Add API documentation
> v2:
> New patch
> ---
> arch/riscv/lib/interrupts.c | 13 +++++++++++
> doc/api/index.rst | 1 +
> include/interrupt.h | 45 +++++++++++++++++++++++++++++++++++++
> 3 files changed, 59 insertions(+)
> create mode 100644 include/interrupt.h
Reviewed-by: Leo Yu-Chi Liang <ycliang@andestech.com>
next prev parent reply other threads:[~2023-11-01 9:00 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-31 12:55 [PATCH v3 0/2] rng: Provide a RNG based on the RISC-V Zkr ISA extension Heinrich Schuchardt
2023-10-31 12:55 ` [PATCH v3 1/2] riscv: allow resume after exception Heinrich Schuchardt
2023-11-01 8:55 ` Leo Liang [this message]
2023-10-31 12:55 ` [PATCH v3 2/2] rng: Provide a RNG based on the RISC-V Zkr ISA extension Heinrich Schuchardt
2023-11-01 17:05 ` [PATCH v3 0/2] " Andre Przywara
2023-11-01 17:16 ` Sean Anderson
2023-11-01 17:49 ` Andre Przywara
2023-11-01 18:20 ` Sean Anderson
2023-11-01 20:20 ` Heinrich Schuchardt
2023-11-03 19:38 ` Simon Glass
2023-11-04 17:12 ` Andre Przywara
2023-11-04 19:45 ` Simon Glass
2023-11-04 20:36 ` Heinrich Schuchardt
2023-11-04 22:58 ` Simon Glass
2023-11-06 17:26 ` Andre Przywara
2023-11-06 20:13 ` Tom Rini
2023-11-06 20:38 ` Simon Glass
2023-11-06 20:46 ` Tom Rini
2023-11-07 1:10 ` Simon Glass
2023-11-07 19:30 ` Tom Rini
2023-11-07 21:52 ` Rob Herring
2023-11-07 22:10 ` Tom Rini
2023-11-07 22:27 ` Conor Dooley
2023-11-07 22:38 ` Tom Rini
2023-11-07 22:51 ` Simon Glass
2023-11-07 23:14 ` Tom Rini
2023-11-07 23:12 ` Conor Dooley
2023-11-07 23:23 ` Tom Rini
2023-11-08 0:29 ` Conor Dooley
2023-11-08 0:34 ` Tom Rini
2023-11-08 14:23 ` Heinrich Schuchardt
2023-11-08 14:37 ` Tom Rini
2023-11-08 15:25 ` Heinrich Schuchardt
2023-11-08 16:44 ` Tom Rini
2023-11-08 17:10 ` Heinrich Schuchardt
2023-11-08 17:38 ` Palmer Dabbelt
2023-11-10 11:50 ` Simon Glass
2023-11-06 21:53 ` Andre Przywara
2023-11-07 1:08 ` Simon Glass
2023-11-07 11:27 ` Andre Przywara
2023-11-07 12:22 ` Simon Glass
2023-11-07 15:12 ` Andre Przywara
2023-11-07 22:03 ` Tom Rini
2023-11-08 4:24 ` Simon Glass
2023-11-08 7:11 ` Ilias Apalodimas
2023-11-07 21:53 ` Tom Rini
2023-11-07 21:24 ` Tom Rini
2023-11-06 16:46 ` Tom Rini
2023-11-06 17:24 ` Simon Glass
2023-11-06 17:45 ` Andre Przywara
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=ZUISnaQbphUmV_RF@swlinux02 \
--to=ycliang@andestech.com \
--cc=apatel@ventanamicro.com \
--cc=chanho61.park@samsung.com \
--cc=heinrich.schuchardt@canonical.com \
--cc=merlew4n6@gmail.com \
--cc=rick@andestech.com \
--cc=sughosh.ganu@linaro.org \
--cc=u-boot@lists.denx.de \
/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