From: <ltaylorsimpson@gmail.com>
To: "'Brian Cain'" <bcain@quicinc.com>, <qemu-devel@nongnu.org>
Cc: <quic_mathbern@quicinc.com>, <sidneym@quicinc.com>,
<quic_mliebel@quicinc.com>,
"'Laurent Vivier'" <laurent@vivier.eu>
Subject: RE: [PATCH v2 1/2] target/hexagon: rename HEX_EXCP_*=>HEX_CAUSE_*
Date: Mon, 26 Aug 2024 19:44:33 -0600 [thread overview]
Message-ID: <000001daf822$ab12bf40$01383dc0$@gmail.com> (raw)
In-Reply-To: <20240827002631.3492200-2-bcain@quicinc.com>
> -----Original Message-----
> From: Brian Cain <bcain@quicinc.com>
> Sent: Monday, August 26, 2024 6:27 PM
> To: qemu-devel@nongnu.org
> Cc: bcain@quicinc.com; quic_mathbern@quicinc.com;
> sidneym@quicinc.com; quic_mliebel@quicinc.com;
> ltaylorsimpson@gmail.com; Laurent Vivier <laurent@vivier.eu>
> Subject: [PATCH v2 1/2] target/hexagon: rename
> HEX_EXCP_*=>HEX_CAUSE_*
>
> The values previously used for "HEX_EXCP_*" were the cause code
> definitions and not the event numbers. So in this commit, we update the
> names to reflect the cause codes. In HEX_EVENT_TRAP0's case, we add a
> new "HEX_EVENT_*" with the correct event number.
>
> Signed-off-by: Brian Cain <bcain@quicinc.com>
> ---
> linux-user/hexagon/cpu_loop.c | 4 ++--
> target/hexagon/cpu.h | 2 +-
> target/hexagon/cpu_bits.h | 15 ++++++++-------
> target/hexagon/gen_tcg.h | 2 +-
> target/hexagon/translate.c | 6 +++---
> 5 files changed, 15 insertions(+), 14 deletions(-)
Reviewed-by: Taylor Simpson <ltaylorsimpson@gmail.com>
next prev parent reply other threads:[~2024-08-27 1:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-27 0:26 [PATCH v2 0/2] target/hexagon: event codes Brian Cain
2024-08-27 0:26 ` [PATCH v2 1/2] target/hexagon: rename HEX_EXCP_*=>HEX_CAUSE_* Brian Cain
2024-08-27 1:44 ` ltaylorsimpson [this message]
2024-08-27 0:26 ` [PATCH v2 2/2] target/hexagon: add enums for event, cause Brian Cain
2024-08-27 1:45 ` ltaylorsimpson
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='000001daf822$ab12bf40$01383dc0$@gmail.com' \
--to=ltaylorsimpson@gmail.com \
--cc=bcain@quicinc.com \
--cc=laurent@vivier.eu \
--cc=qemu-devel@nongnu.org \
--cc=quic_mathbern@quicinc.com \
--cc=quic_mliebel@quicinc.com \
--cc=sidneym@quicinc.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).