From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: Mohamed Mediouni <mohamed@unpredictable.fr>, qemu-devel@nongnu.org
Cc: "Daniel P. Berrangé" <berrange@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Sunil Muthuswamy" <sunilmut@microsoft.com>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Peter Maydell" <peter.maydell@linaro.org>,
qemu-arm@nongnu.org
Subject: Re: [RFC 3/9] whpx: common: use whpx_cpu_instance_init on x86 only
Date: Thu, 31 Jul 2025 10:30:22 +0200 [thread overview]
Message-ID: <ccee61c9-ee41-4183-a87b-2a9641d92dc0@linaro.org> (raw)
In-Reply-To: <20250731052753.93255-4-mohamed@unpredictable.fr>
Hi Mohamed,
On 31/7/25 07:27, Mohamed Mediouni wrote:
> We aren't using it on arm64.
>
> Signed-off-by: Mohamed Mediouni <mohamed@unpredictable.fr>
> ---
> accel/whpx/whpx-common.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/accel/whpx/whpx-common.c b/accel/whpx/whpx-common.c
> index 0b23deb7c4..43d0200afd 100644
> --- a/accel/whpx/whpx-common.c
> +++ b/accel/whpx/whpx-common.c
> @@ -486,9 +486,10 @@ static void whpx_set_kernel_irqchip(Object *obj, Visitor *v,
>
> static void whpx_cpu_accel_class_init(ObjectClass *oc, const void *data)
> {
> +#ifdef __x86_64__
> AccelCPUClass *acc = ACCEL_CPU_CLASS(oc);
> -
> acc->cpu_instance_init = whpx_cpu_instance_init;
> +#endif
> }
I'd rather keep whpx-*common* without any #ifdef'ry: add hooks
when architecture-specific code need to be handled, and add empty
arch stub when nothing to be done there (preferably with a comment
in the stub).
next prev parent reply other threads:[~2025-07-31 8:30 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-31 5:27 [RFC 0/9] WHPX support for Arm Mohamed Mediouni
2025-07-31 5:27 ` [RFC 1/9] whpx: Move around files before introducing AArch64 support Mohamed Mediouni
2025-07-31 8:27 ` Philippe Mathieu-Daudé
2025-08-01 5:44 ` Richard Henderson
2025-07-31 5:27 ` [RFC 2/9] whpx: reshuffle common code Mohamed Mediouni
2025-07-31 5:27 ` [RFC 3/9] whpx: common: use whpx_cpu_instance_init on x86 only Mohamed Mediouni
2025-07-31 8:30 ` Philippe Mathieu-Daudé [this message]
2025-07-31 5:27 ` [RFC 4/9] whpx: interrupt controller support Mohamed Mediouni
2025-07-31 5:27 ` [RFC 5/9] hw/virt: make Qemu aware that WHPX has a vGICv3 Mohamed Mediouni
2025-07-31 8:35 ` Philippe Mathieu-Daudé
2025-07-31 14:47 ` Mohamed Mediouni
2025-07-31 5:27 ` [RFC 6/9] hw: intc: arm_gicv3_common: add whpx Mohamed Mediouni
2025-07-31 8:33 ` Philippe Mathieu-Daudé
2025-07-31 5:27 ` [RFC 7/9] whpx: add arm64 support Mohamed Mediouni
2025-07-31 5:27 ` [RFC 8/9] whpx: copy over memory tracking logic from hvf Mohamed Mediouni
2025-07-31 5:27 ` [RFC 9/9] target/arm: cpu: mark WHPX as supporting PSCI 1.1 Mohamed Mediouni
2025-08-01 1:15 ` [RFC 0/9] WHPX support for Arm Pierrick Bouvier
2025-08-01 12:43 ` Mohamed Mediouni
2025-08-01 17:22 ` Pierrick Bouvier
2025-08-01 18:52 ` Mohamed Mediouni
2025-08-01 19:16 ` Pierrick Bouvier
2025-08-01 19:31 ` Mohamed Mediouni
2025-08-01 19:42 ` Pierrick Bouvier
2025-08-01 19:57 ` Mohamed Mediouni
2025-08-01 20:10 ` 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=ccee61c9-ee41-4183-a87b-2a9641d92dc0@linaro.org \
--to=philmd@linaro.org \
--cc=berrange@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=mohamed@unpredictable.fr \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=sunilmut@microsoft.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 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).