From: Conor Dooley <conor@kernel.org>
To: Nam Cao <namcaov@gmail.com>
Cc: Conor Dooley <conor.dooley@microchip.com>,
Guo Ren <guoren@kernel.org>,
Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
bjorn@kernel.org
Subject: Re: [PATCH] riscv: provide riscv-specific is_trap_insn()
Date: Thu, 31 Aug 2023 17:29:42 +0100 [thread overview]
Message-ID: <20230831-untidy-geologic-8c8232eb3cac@spud> (raw)
In-Reply-To: <ZO2p1tScBT1UFMh1@nam-dell>
[-- Attachment #1: Type: text/plain, Size: 321 bytes --]
On Tue, Aug 29, 2023 at 10:18:30AM +0200, Nam Cao wrote:
> Now I'm not sure what you mean. But I agree with Guo Ren here, users can use
> compressed instructions but kernel does not have it enabled. So we should
> always check c.ebreak regardless of RISCV_ISA_C.
I think I was just being dumb, apologies for the noise.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
prev parent reply other threads:[~2023-08-31 16:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-27 20:56 [PATCH] riscv: provide riscv-specific is_trap_insn() Nam Cao
2023-08-28 12:48 ` Björn Töpel
2023-08-28 13:31 ` Nam Cao
2023-08-28 13:50 ` Nam Cao
2023-08-29 6:14 ` Björn Töpel
2023-08-29 18:54 ` Nam Cao
2023-08-30 7:32 ` Björn Töpel
2023-08-30 7:46 ` Nam Cao
2023-08-30 7:56 ` Nam Cao
2023-08-29 5:56 ` Guo Ren
2023-08-29 6:26 ` Conor Dooley
2023-08-29 8:12 ` Nam Cao
2023-08-29 8:18 ` Nam Cao
2023-08-31 16:29 ` Conor Dooley [this message]
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=20230831-untidy-geologic-8c8232eb3cac@spud \
--to=conor@kernel.org \
--cc=aou@eecs.berkeley.edu \
--cc=bjorn@kernel.org \
--cc=conor.dooley@microchip.com \
--cc=guoren@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=namcaov@gmail.com \
--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