From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: Anton Johansson <anjo@rev.ng>,
richard.henderson@linaro.org, Paolo Bonzini <pbonzini@redhat.com>
Cc: pierrick.bouvier@linaro.org, qemu-devel@nongnu.org,
alistair.francis@wdc.com, palmer@dabbelt.com
Subject: Re: [PATCH 4/5] target-info: Introduce runtime TARGET_PHYS_ADDR_SPACE_BITS
Date: Wed, 15 Oct 2025 16:32:59 +0200 [thread overview]
Message-ID: <673e3c7b-b8ef-4908-b74d-62203b131229@linaro.org> (raw)
In-Reply-To: <20251015-feature-single-binary-hw-v1-v1-4-8b416eda42cf@rev.ng>
On 15/10/25 15:27, Anton Johansson wrote:
> Signed-off-by: Anton Johansson <anjo@rev.ng>
> ---
> include/qemu/target-info-impl.h | 2 ++
> include/qemu/target-info.h | 8 ++++++++
> target-info.c | 5 +++++
> 3 files changed, 15 insertions(+)
>
> diff --git a/include/qemu/target-info-impl.h b/include/qemu/target-info-impl.h
> index 17887f64e2..80d1613128 100644
> --- a/include/qemu/target-info-impl.h
> +++ b/include/qemu/target-info-impl.h
> @@ -18,6 +18,8 @@ typedef struct TargetInfo {
> SysEmuTarget target_arch;
> /* runtime equivalent of TARGET_LONG_BITS definition */
> unsigned long_bits;
> + /* runtime equivalent of TARGET_PHYS_ADDR_SPACE_BITS definition */
> + unsigned phys_addr_space_bits;
> /* runtime equivalent of CPU_RESOLVING_TYPE definition */
> const char *cpu_type;
> /* QOM typename machines for this binary must implement */
> diff --git a/target-info.c b/target-info.c
> index 3110ab32f7..3d696ae0b3 100644
> --- a/target-info.c
> +++ b/target-info.c
> @@ -22,6 +22,11 @@ unsigned target_long_bits(void)
> return target_info()->long_bits;
> }
>
> +unsigned target_phys_addr_space_bits(void)
> +{
> + return target_info()->phys_addr_space_bits;
> +}
Missing field initialization in target_info_stub[].
BTW this definition seems unused by common code since commit
2e8fe327eb6 ("accel/tcg: Simplify L1_MAP_ADDR_SPACE_BITS").
Do we still need to expose it to common components?
next prev parent reply other threads:[~2025-10-15 14:35 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-15 13:27 [PATCH 0/5] single-binary: Prepare hw/riscv for single compilation Anton Johansson via
2025-10-15 13:27 ` [PATCH 1/5] hw/riscv: Use generic hwaddr for firmware addressses Anton Johansson via
2025-10-15 14:21 ` Philippe Mathieu-Daudé
2025-10-23 17:14 ` Anton Johansson via
2025-10-23 17:55 ` Philippe Mathieu-Daudé
2025-10-27 12:11 ` Anton Johansson via
2025-10-15 13:27 ` [PATCH 2/5] hw/riscv: Replace target_ulong uses Anton Johansson via
2025-10-15 14:22 ` Philippe Mathieu-Daudé
2025-10-15 16:31 ` Richard Henderson
2025-10-15 16:50 ` Philippe Mathieu-Daudé
2025-10-15 13:27 ` [PATCH 3/5] hw/riscv: Widen OpenSBI dynamic info struct Anton Johansson via
2025-10-16 23:42 ` Alistair Francis
2025-10-15 13:27 ` [PATCH 4/5] target-info: Introduce runtime TARGET_PHYS_ADDR_SPACE_BITS Anton Johansson via
2025-10-15 14:32 ` Philippe Mathieu-Daudé [this message]
2025-10-17 16:11 ` Anton Johansson via
2025-10-17 18:47 ` Richard Henderson
2025-10-18 2:34 ` Bibo Mao
2025-10-15 13:27 ` [PATCH 5/5] hw/riscv: Use runtime target_phys_addr_space_bits() Anton Johansson via
2025-10-16 23:43 ` Alistair Francis
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=673e3c7b-b8ef-4908-b74d-62203b131229@linaro.org \
--to=philmd@linaro.org \
--cc=alistair.francis@wdc.com \
--cc=anjo@rev.ng \
--cc=palmer@dabbelt.com \
--cc=pbonzini@redhat.com \
--cc=pierrick.bouvier@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.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 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).