From: Keith Packard via <qemu-devel@nongnu.org>
To: qemu-devel@nongnu.org
Cc: Keith Packard <keithp@keithp.com>
Subject: [PATCH 0/5] Renesas RX target fixes
Date: Fri, 14 Feb 2025 18:16:49 -0800 [thread overview]
Message-ID: <20250215021654.1786679-1-keithp@keithp.com> (raw)
I'm getting a Renesas toolchain working and found a couple of bugs
and a few fixes in the qemu target code for this device.
The two critical bugs which are fixed:
1. Exception vector base address is incorrect. The
right value is 0xffffff80.
2. A bunch of opcode helper functions are incorrectly labeled as
TCG_CALL_NO_WG. These helpers read and write virtual registers out
of the global environment and so must not be marked with this flag.
The other changes included are sufficient to use qemu without needing
to start gdb as well, starting the machine using the reset vector
found in the exception table and then re-loading that vector during
subsequent reset operations.
With these fixes, the picolibc CI tests are now passing.
Keith Packard (5):
hw/rx: Allow execution without either bios or kernel
target/rx: Set exception vector base to 0xffffff80
target/rx: Reset the CPU at qemu reset time
target/rx: Load reset vector from memory after first run
target/rx: Remove TCG_CALL_NO_WG from helpers which write env
hw/rx/rx-gdbsim.c | 3 ---
target/rx/cpu.c | 35 +++++++++++++++++++++++++++++------
target/rx/helper.c | 2 +-
target/rx/helper.h | 14 +++++++-------
4 files changed, 37 insertions(+), 17 deletions(-)
--
2.47.2
next reply other threads:[~2025-02-15 2:18 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-15 2:16 Keith Packard via [this message]
2025-02-15 2:16 ` [PATCH 1/5] hw/rx: Allow execution without either bios or kernel Keith Packard via
2025-02-15 18:12 ` Richard Henderson
2025-02-15 2:16 ` [PATCH 2/5] target/rx: Set exception vector base to 0xffffff80 Keith Packard via
2025-02-15 18:12 ` Richard Henderson
2025-02-15 2:16 ` [PATCH 3/5] target/rx: Reset the CPU at qemu reset time Keith Packard via
2025-02-17 7:41 ` Philippe Mathieu-Daudé
2025-02-17 9:53 ` Peter Maydell
2025-02-18 20:09 ` Keith Packard via
2025-02-15 2:16 ` [PATCH 4/5] target/rx: Load reset vector from memory after first run Keith Packard via
2025-02-15 18:24 ` Richard Henderson
2025-02-17 9:49 ` Peter Maydell
2025-02-18 20:22 ` Keith Packard via
2025-02-18 20:11 ` Keith Packard via
2025-02-18 20:18 ` Keith Packard via
2025-02-15 2:16 ` [PATCH 5/5] target/rx: Remove TCG_CALL_NO_WG from helpers which write env Keith Packard via
2025-02-15 9:21 ` Keith Packard via
2025-02-15 17:09 ` Richard Henderson
2025-02-15 18:42 ` Richard Henderson
2025-02-18 21:20 ` [PATCH 0/4] Renesas RX target fixes (v2) Keith Packard via
2025-02-18 21:21 ` [PATCH 1/4] target/rx: Set exception vector base to 0xffffff80 Keith Packard via
2025-03-07 11:26 ` Peter Maydell
2025-02-18 21:21 ` [PATCH 2/4] target/rx: Remove TCG_CALL_NO_WG from helpers which write env Keith Packard via
2025-03-07 11:22 ` Peter Maydell
2025-02-18 21:21 ` [PATCH 3/4] hw/rx: Reset the CPU at qemu reset time Keith Packard via
2025-03-07 13:26 ` Peter Maydell
2025-06-01 1:13 ` Keith Packard via
2025-02-18 21:21 ` [PATCH 4/4] rx: Support loading of ELF files too Keith Packard via
2025-03-07 13:38 ` Peter Maydell
2025-06-01 0:35 ` Keith Packard via
2025-03-07 13:51 ` [PATCH 0/4] Renesas RX target fixes (v2) Peter Maydell
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=20250215021654.1786679-1-keithp@keithp.com \
--to=qemu-devel@nongnu.org \
--cc=keithp@keithp.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).