qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Richard Henderson <richard.henderson@linaro.org>
To: Mohamed Mediouni <mohamed@unpredictable.fr>, qemu-devel@nongnu.org
Subject: Re: [PATCH v3 11/14] whpx: arm64: clamp down IPA size
Date: Sun, 3 Aug 2025 11:00:52 +1000	[thread overview]
Message-ID: <db6c8b4f-027a-460d-902a-33536b1123cc@linaro.org> (raw)
In-Reply-To: <20250802081800.76030-12-mohamed@unpredictable.fr>

On 8/2/25 18:17, Mohamed Mediouni wrote:
> +++ b/include/hw/boards.h
> @@ -276,6 +276,7 @@ struct MachineClass {
>       void (*wakeup)(MachineState *state);
>       int (*kvm_type)(MachineState *machine, const char *arg);
>       int (*hvf_get_physical_address_range)(MachineState *machine);
> +    int (*whpx_get_physical_address_range)(MachineState *machine);

We need to generalize this to an accelerator hook, so that there's one code path for both 
hvf and whpx.  And kvm, for that matter, though it's less obvious how that's handled.


r~


  reply	other threads:[~2025-08-03  1:01 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-02  8:17 [PATCH v3 00/14] WHPX support for Arm Mohamed Mediouni
2025-08-02  8:17 ` [PATCH v3 01/14] hw/arm: virt: add GICv2m for the case when ITS is not available Mohamed Mediouni
2025-08-02  8:17 ` [PATCH v3 02/14] whpx: Move around files before introducing AArch64 support Mohamed Mediouni
2025-08-02  8:53   ` Mohamed Mediouni
2025-08-03  0:03   ` Richard Henderson
2025-08-02  8:17 ` [PATCH v3 03/14] whpx: reshuffle common code Mohamed Mediouni
2025-08-03  0:15   ` Richard Henderson
2025-08-02  8:17 ` [PATCH v3 04/14] whpx: ifdef out some x86-only code paths Mohamed Mediouni
2025-08-03  0:41   ` Richard Henderson
2025-08-03  0:55     ` Mohamed Mediouni
2025-08-03  1:03       ` Richard Henderson
2025-08-03  1:08         ` Mohamed Mediouni
2025-08-03  1:14           ` Richard Henderson
2025-08-03  0:51   ` Richard Henderson
2025-08-02  8:17 ` [PATCH v3 05/14] hw, target, accel: whpx: change apic_in_platform to kernel_irqchip Mohamed Mediouni
2025-08-03  0:42   ` Richard Henderson
2025-08-02  8:17 ` [PATCH v3 06/14] whpx: interrupt controller support Mohamed Mediouni
2025-08-02  8:17 ` [PATCH v3 07/14] whpx: add arm64 support Mohamed Mediouni
2025-08-03  0:56   ` Richard Henderson
2025-08-03  1:03     ` Mohamed Mediouni
2025-08-02  8:17 ` [PATCH v3 08/14] whpx: copy over memory management logic from hvf Mohamed Mediouni
2025-08-02  8:17 ` [PATCH v3 09/14] target/arm: cpu: mark WHPX as supporting PSCI 1.1 Mohamed Mediouni
2025-08-03  0:56   ` Richard Henderson
2025-08-02  8:17 ` [PATCH v3 10/14] hw/arm: virt: cleanly fail on attempt to use the platform vGIC together with ITS Mohamed Mediouni
2025-08-03  0:57   ` Richard Henderson
2025-08-02  8:17 ` [PATCH v3 11/14] whpx: arm64: clamp down IPA size Mohamed Mediouni
2025-08-03  1:00   ` Richard Henderson [this message]
2025-08-02  8:17 ` [PATCH v3 12/14] whpx: arm64: implement -cpu host Mohamed Mediouni
2025-08-03  1:22   ` Richard Henderson
2025-08-02  8:17 ` [PATCH v3 13/14] target/arm: whpx: instantiate GIC early Mohamed Mediouni
2025-08-02  8:18 ` [PATCH v3 14/14] MAINTAINERS: Add myself as a maintainer for WHPX Mohamed Mediouni
2025-08-03  1:23   ` 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=db6c8b4f-027a-460d-902a-33536b1123cc@linaro.org \
    --to=richard.henderson@linaro.org \
    --cc=mohamed@unpredictable.fr \
    --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).