From: Richard Henderson <richard.henderson@linaro.org>
To: "Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Mohamed Mediouni" <mohamed@unpredictable.fr>,
qemu-devel@nongnu.org
Subject: Re: [PATCH v4 14/17] hw/arm, accel/hvf, whpx: unify get_physical_address_range between WHPX and HVF
Date: Tue, 5 Aug 2025 09:13:58 +1000 [thread overview]
Message-ID: <cb5aa557-aab8-4a6f-977b-b9d15a5c6799@linaro.org> (raw)
In-Reply-To: <e5bfbc26-de3d-4f4c-b15d-6c7ea1b29e49@linaro.org>
On 8/5/25 09:03, Philippe Mathieu-Daudé wrote:
> On 4/8/25 16:23, Mohamed Mediouni wrote:
>> Signed-off-by: Mohamed Mediouni <mohamed@unpredictable.fr>
>> ---
>> accel/hvf/hvf-all.c | 7 +++++--
>> hw/arm/virt.c | 41 ++++----------------------------------
>> include/hw/boards.h | 4 ++--
>> include/system/hvf_int.h | 2 ++
>> target/arm/hvf-stub.c | 20 -------------------
>> target/arm/hvf/hvf.c | 6 +++---
>> target/arm/hvf_arm.h | 3 ---
>> target/arm/meson.build | 1 -
>> target/arm/whpx/whpx-all.c | 5 +++--
>> target/i386/hvf/hvf.c | 10 ++++++++++
>> 10 files changed, 29 insertions(+), 70 deletions(-)
>> delete mode 100644 target/arm/hvf-stub.c
>
>
>> diff --git a/target/i386/hvf/hvf.c b/target/i386/hvf/hvf.c
>> index 818b50419f..fa06e3b815 100644
>> --- a/target/i386/hvf/hvf.c
>> +++ b/target/i386/hvf/hvf.c
>> @@ -225,6 +225,16 @@ int hvf_arch_init(void)
>> return 0;
>> }
>> +uint32_t hvf_arch_get_default_ipa_bit_size(void)
>> +{
>> + return 48;
>> +}
>> +
>> +uint32_t hvf_arch_get_max_ipa_bit_size(void)
>> +{
>> + return 48;
>
> These don't make much sense on x86...
They don't *not* make sense. x86 does have two-stage translation, though it has both
48-bit and 52-bit translation.
While this is only invoked from hw/arm/virt.c at present, I can see that by piping the
path through accel/hvf/ means that x86 needs to provide the symbols. Though perhaps they
should just be g_assert_not_reached() stubs for now.
r~
next prev parent reply other threads:[~2025-08-04 23:14 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-04 14:23 [PATCH v4 00/17] WHPX support for Arm Mohamed Mediouni
2025-08-04 14:23 ` [PATCH v4 01/17] accel/system: Introduce hwaccel_enabled() helper Mohamed Mediouni
2025-08-04 16:00 ` Claudio Fontana
2025-08-04 16:12 ` Mohamed Mediouni
2025-08-04 18:58 ` Philippe Mathieu-Daudé
2025-08-04 14:23 ` [PATCH v4 02/17] hw/arm: virt: add GICv2m for the case when ITS is not available Mohamed Mediouni
2025-08-04 19:25 ` Pierrick Bouvier
2025-08-04 14:23 ` [PATCH v4 03/17] whpx: Move around files before introducing AArch64 support Mohamed Mediouni
2025-08-04 19:38 ` Pierrick Bouvier
2025-08-04 14:23 ` [PATCH v4 04/17] whpx: reshuffle common code Mohamed Mediouni
2025-08-04 19:41 ` Pierrick Bouvier
2025-08-04 14:23 ` [PATCH v4 05/17] whpx: ifdef out winhvemulation on non-x86_64 Mohamed Mediouni
2025-08-04 19:44 ` Pierrick Bouvier
2025-08-04 14:23 ` [PATCH v4 06/17] whpx: common: add WHPX_INTERCEPT_DEBUG_TRAPS define Mohamed Mediouni
2025-08-04 19:45 ` Pierrick Bouvier
2025-08-04 14:23 ` [PATCH v4 07/17] hw, target, accel: whpx: change apic_in_platform to kernel_irqchip Mohamed Mediouni
2025-08-04 19:48 ` Pierrick Bouvier
2025-08-04 14:23 ` [PATCH v4 08/17] whpx: interrupt controller support Mohamed Mediouni
2025-08-04 21:39 ` Pierrick Bouvier
2025-08-04 21:47 ` Mohamed Mediouni
2025-08-04 21:48 ` Pierrick Bouvier
2025-08-04 21:49 ` Pierrick Bouvier
2025-08-04 14:23 ` [PATCH v4 09/17] whpx: add arm64 support Mohamed Mediouni
2025-08-04 21:59 ` Pierrick Bouvier
2025-08-04 22:08 ` Mohamed Mediouni
2025-08-04 22:16 ` Pierrick Bouvier
2025-08-04 22:15 ` Pierrick Bouvier
2025-08-04 22:56 ` Philippe Mathieu-Daudé
2025-08-04 14:23 ` [PATCH v4 10/17] whpx: copy over memory management logic from hvf Mohamed Mediouni
2025-08-04 21:14 ` Pierrick Bouvier
2025-08-04 22:56 ` Philippe Mathieu-Daudé
2025-08-04 23:02 ` Pierrick Bouvier
2025-08-04 14:23 ` [PATCH v4 11/17] target/arm: cpu: mark WHPX as supporting PSCI 1.1 Mohamed Mediouni
2025-08-04 19:48 ` Pierrick Bouvier
2025-08-04 14:23 ` [PATCH v4 12/17] hw/arm: virt: cleanly fail on attempt to use the platform vGIC together with ITS Mohamed Mediouni
2025-08-04 19:50 ` Pierrick Bouvier
2025-08-04 19:56 ` Mohamed Mediouni
2025-08-04 20:40 ` Pierrick Bouvier
2025-08-04 20:59 ` Mohamed Mediouni
2025-08-04 21:22 ` Pierrick Bouvier
2025-08-04 22:59 ` Philippe Mathieu-Daudé
2025-08-04 23:52 ` Mohamed Mediouni
2025-08-04 14:23 ` [PATCH v4 13/17] whpx: arm64: clamp down IPA size Mohamed Mediouni
2025-08-04 20:46 ` Pierrick Bouvier
2025-08-04 14:23 ` [PATCH v4 14/17] hw/arm, accel/hvf, whpx: unify get_physical_address_range between WHPX and HVF Mohamed Mediouni
2025-08-04 20:58 ` Pierrick Bouvier
2025-08-04 23:03 ` Philippe Mathieu-Daudé
2025-08-04 23:10 ` Pierrick Bouvier
2025-08-04 23:13 ` Richard Henderson [this message]
2025-08-04 23:41 ` Mohamed Mediouni
2025-08-05 0:27 ` Mohamed Mediouni
2025-08-04 14:23 ` [PATCH v4 15/17] whpx: arm64: implement -cpu host Mohamed Mediouni
2025-08-04 21:27 ` Pierrick Bouvier
2025-08-04 21:49 ` Mohamed Mediouni
2025-08-04 22:00 ` Pierrick Bouvier
2025-08-04 14:23 ` [PATCH v4 16/17] target/arm: whpx: instantiate GIC early Mohamed Mediouni
2025-08-04 19:52 ` Pierrick Bouvier
2025-08-04 14:23 ` [PATCH v4 17/17] MAINTAINERS: Add myself as a maintainer for WHPX Mohamed Mediouni
2025-08-04 19:52 ` Pierrick Bouvier
2025-08-04 18:51 ` [PATCH v4 00/17] WHPX support for Arm Pierrick Bouvier
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=cb5aa557-aab8-4a6f-977b-b9d15a5c6799@linaro.org \
--to=richard.henderson@linaro.org \
--cc=mohamed@unpredictable.fr \
--cc=philmd@linaro.org \
--cc=qemu-devel@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 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).