From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: qemu-devel@nongnu.org
Cc: "Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Huacai Chen" <chenhuacai@loongson.cn>,
"Xiaojuan Yang" <yangxiaojuan@loongson.cn>,
"Alex Bennée" <alex.bennee@linaro.org>, "Jiajie Chen" <c@jia.je>,
"Song Gao" <gaosong@loongson.cn>
Subject: [PATCH v2 0/8] target/loongarch: Cleanups in preparation of loongarch32 support
Date: Fri, 18 Aug 2023 19:20:08 +0200 [thread overview]
Message-ID: <20230818172016.24504-1-philmd@linaro.org> (raw)
v2:
- Do no rename loongarch_cpu_get/set_pc (rth)
- Rebased Jiajie's patches for convenience
- Added rth's R-b
Jiajie, this series contains few notes I took while
reviewing your series adding loongarch32 support [*].
If your series isn't merged, consider rebasing it on
this one.
Regards,
Phil.
[*] https://lore.kernel.org/qemu-devel/20230817093121.1053890-1-gaosong@loongson.cn/
Jiajie Chen (3):
target/loongarch: Add function to check current arch
target/loongarch: Add new object class for loongarch32 cpus
target/loongarch: Add GDB support for loongarch32 mode
Philippe Mathieu-Daudé (4):
target/loongarch: Log I/O write accesses to CSR registers
target/loongarch: Remove duplicated disas_set_info assignment
target/loongarch: Introduce abstract TYPE_LOONGARCH64_CPU
target/loongarch: Extract 64-bit specifics to
loongarch64_cpu_class_init
Song Gao (1):
target/loongarch: Fix loongarch_la464_initfn() misses setting LSPW
configs/targets/loongarch64-softmmu.mak | 2 +-
target/loongarch/cpu.h | 12 +++++
target/loongarch/cpu.c | 62 +++++++++++++++++++------
target/loongarch/gdbstub.c | 32 ++++++++++---
gdb-xml/loongarch-base32.xml | 45 ++++++++++++++++++
5 files changed, 132 insertions(+), 21 deletions(-)
create mode 100644 gdb-xml/loongarch-base32.xml
--
2.41.0
next reply other threads:[~2023-08-18 17:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-18 17:20 Philippe Mathieu-Daudé [this message]
2023-08-18 17:20 ` [PATCH v2 1/8] target/loongarch: Log I/O write accesses to CSR registers Philippe Mathieu-Daudé
2023-08-19 7:33 ` gaosong
2023-08-18 17:20 ` [PATCH v2 2/8] target/loongarch: Remove duplicated disas_set_info assignment Philippe Mathieu-Daudé
2023-08-19 7:34 ` gaosong
2023-08-18 17:20 ` [PATCH v2 3/8] target/loongarch: Fix loongarch_la464_initfn() misses setting LSPW Philippe Mathieu-Daudé
2023-08-18 17:20 ` [PATCH v2 4/8] target/loongarch: Introduce abstract TYPE_LOONGARCH64_CPU Philippe Mathieu-Daudé
2023-08-18 17:33 ` Richard Henderson
2023-08-18 17:20 ` [PATCH v2 5/8] target/loongarch: Extract 64-bit specifics to loongarch64_cpu_class_init Philippe Mathieu-Daudé
2023-08-18 17:32 ` Richard Henderson
2023-08-18 17:20 ` [PATCH v2 6/8] target/loongarch: Add function to check current arch Philippe Mathieu-Daudé
2023-08-18 17:20 ` [PATCH v2 7/8] target/loongarch: Add new object class for loongarch32 cpus Philippe Mathieu-Daudé
2023-08-18 17:20 ` [PATCH v2 8/8] target/loongarch: Add GDB support for loongarch32 mode Philippe Mathieu-Daudé
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=20230818172016.24504-1-philmd@linaro.org \
--to=philmd@linaro.org \
--cc=alex.bennee@linaro.org \
--cc=c@jia.je \
--cc=chenhuacai@loongson.cn \
--cc=gaosong@loongson.cn \
--cc=qemu-devel@nongnu.org \
--cc=yangxiaojuan@loongson.cn \
/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).