From: Daniel Henrique Barboza <dbarboza@ventanamicro.com>
To: qemu-devel@nongnu.org
Cc: qemu-riscv@nongnu.org, alistair.francis@wdc.com,
Daniel Henrique Barboza <dbarboza@ventanamicro.com>
Subject: [PATCH v8 0/3] hw/riscv: clear kernel_entry high bits with 32bit CPUs
Date: Mon, 16 Jan 2023 09:29:45 -0300 [thread overview]
Message-ID: <20230116122948.757515-1-dbarboza@ventanamicro.com> (raw)
Hi,
This version has changes in patch 3 where we're now using extract64()
instead of a plain bit mask to return the 32 bit address in
translate_fn().
Changes from v7:
- patch 2:
- added Alistair's r-b
- patch 3:
- use extract64() to return the 32 bit address
v7 link: https://lists.gnu.org/archive/html/qemu-devel/2023-01/msg02916.html
Daniel Henrique Barboza (3):
hw/riscv/boot.c: consolidate all kernel init in riscv_load_kernel()
hw/riscv/boot.c: make riscv_load_initrd() static
hw/riscv: clear kernel_entry higher bits in load_elf_ram_sym()
hw/riscv/boot.c | 108 ++++++++++++++++++++++++-------------
hw/riscv/microchip_pfsoc.c | 12 +----
hw/riscv/opentitan.c | 3 +-
hw/riscv/sifive_e.c | 4 +-
hw/riscv/sifive_u.c | 12 +----
hw/riscv/spike.c | 13 +----
hw/riscv/virt.c | 12 +----
include/hw/riscv/boot.h | 3 +-
target/riscv/cpu_bits.h | 1 +
9 files changed, 87 insertions(+), 81 deletions(-)
--
2.39.0
next reply other threads:[~2023-01-16 12:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-16 12:29 Daniel Henrique Barboza [this message]
2023-01-16 12:29 ` [PATCH v8 1/3] hw/riscv/boot.c: consolidate all kernel init in riscv_load_kernel() Daniel Henrique Barboza
2023-01-18 22:43 ` Alistair Francis
2023-01-16 12:29 ` [PATCH v8 2/3] hw/riscv/boot.c: make riscv_load_initrd() static Daniel Henrique Barboza
2023-01-16 12:29 ` [PATCH v8 3/3] hw/riscv: clear kernel_entry higher bits in load_elf_ram_sym() Daniel Henrique Barboza
2023-01-16 12:37 ` Philippe Mathieu-Daudé
2023-01-16 12:45 ` Daniel Henrique Barboza
2023-01-18 22:45 ` Alistair Francis
2023-01-18 23:34 ` Daniel Henrique Barboza
2023-01-19 0:17 ` Bin Meng
2023-01-19 0:20 ` Bin Meng
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=20230116122948.757515-1-dbarboza@ventanamicro.com \
--to=dbarboza@ventanamicro.com \
--cc=alistair.francis@wdc.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-riscv@nongnu.org \
/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.