From: Daniel Henrique Barboza <dbarboza@ventanamicro.com>
To: qemu-devel@nongnu.org
Cc: qemu-riscv@nongnu.org, alistair.francis@wdc.com,
bmeng@tinylab.org, liweiwei@iscas.ac.cn,
zhiwei_liu@linux.alibaba.com, palmer@rivosinc.com,
Daniel Henrique Barboza <dbarboza@ventanamicro.com>,
Yong-Xuan Wang <yongxuan.wang@sifive.com>
Subject: [PATCH 0/2] riscv: fix --enable-debug in riscv-to-apply.next
Date: Tue, 29 Aug 2023 09:21:42 -0300 [thread overview]
Message-ID: <20230829122144.464489-1-dbarboza@ventanamicro.com> (raw)
Hi,
There is a couple of build problems that sneaked in riscv-to-apply.next
in the KVM AIA patches. Here's a potential solution for them.
Alistair, feel free to squash the fixes in the original commits since
they're not yet on master.
Cc: Yong-Xuan Wang <yongxuan.wang@sifive.com>
Daniel Henrique Barboza (2):
hw/intc/riscv_aplic.c fix non-KVM --enable-debug build
hw/riscv/virt.c: fix non-KVM --enable-debug build
hw/intc/riscv_aplic.c | 2 ++
target/riscv/kvm_riscv.h | 10 ++++++++++
2 files changed, 12 insertions(+)
--
2.41.0
next reply other threads:[~2023-08-29 12:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-29 12:21 Daniel Henrique Barboza [this message]
2023-08-29 12:21 ` [PATCH 1/2] hw/intc/riscv_aplic.c fix non-KVM --enable-debug build Daniel Henrique Barboza
2023-08-29 14:17 ` Philippe Mathieu-Daudé
2023-08-29 22:35 ` Daniel Henrique Barboza
2023-08-29 12:21 ` [PATCH 2/2] hw/riscv/virt.c: " Daniel Henrique Barboza
2023-08-29 14:18 ` Philippe Mathieu-Daudé
2023-08-29 23:09 ` Daniel Henrique Barboza
2023-08-29 23:30 ` Richard Henderson
2023-08-29 23:51 ` Daniel Henrique Barboza
2023-08-30 1:26 ` Richard Henderson
2023-08-30 9:34 ` Daniel Henrique Barboza
2023-08-30 13:49 ` Richard Henderson
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=20230829122144.464489-1-dbarboza@ventanamicro.com \
--to=dbarboza@ventanamicro.com \
--cc=alistair.francis@wdc.com \
--cc=bmeng@tinylab.org \
--cc=liweiwei@iscas.ac.cn \
--cc=palmer@rivosinc.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-riscv@nongnu.org \
--cc=yongxuan.wang@sifive.com \
--cc=zhiwei_liu@linux.alibaba.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.