From: Mohamed Mediouni <mohamed@unpredictable.fr>
To: qemu-devel@nongnu.org
Cc: "Pierrick Bouvier" <pierrick.bouvier@linaro.org>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Pedro Barbuda" <pbarbuda@microsoft.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Mohamed Mediouni" <mohamed@unpredictable.fr>
Subject: [PATCH v6 1/4] meson.build: remove i386-softmmu WHPX support
Date: Fri, 27 Mar 2026 02:11:49 +0100 [thread overview]
Message-ID: <20260327011152.4126-2-mohamed@unpredictable.fr> (raw)
In-Reply-To: <20260327011152.4126-1-mohamed@unpredictable.fr>
target/i386/emulate is pretty much incompatible
with i386-softmmu and fixing that doesn't look
worthwhile given the binary unification goals...
Signed-off-by: Mohamed Mediouni <mohamed@unpredictable.fr>
---
meson.build | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meson.build b/meson.build
index e6f17dd5f7..6f77309075 100644
--- a/meson.build
+++ b/meson.build
@@ -314,7 +314,7 @@ elif cpu == 'x86_64'
'CONFIG_HVF': ['x86_64-softmmu'],
'CONFIG_NITRO': ['x86_64-softmmu'],
'CONFIG_NVMM': ['i386-softmmu', 'x86_64-softmmu'],
- 'CONFIG_WHPX': ['i386-softmmu', 'x86_64-softmmu'],
+ 'CONFIG_WHPX': ['x86_64-softmmu'],
'CONFIG_MSHV': ['x86_64-softmmu'],
}
endif
--
2.50.1 (Apple Git-155)
next prev parent reply other threads:[~2026-03-27 1:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-27 1:11 [PATCH v6 0/4] whpx: i386: even more updates Mohamed Mediouni
2026-03-27 1:11 ` Mohamed Mediouni [this message]
2026-03-27 1:11 ` [PATCH v6 2/4] docs: add WHPX section with initial info Mohamed Mediouni
2026-03-27 16:05 ` Paolo Bonzini
2026-03-27 1:11 ` [PATCH v6 3/4] whpx: i386: trace unsupported MSR accesses Mohamed Mediouni
2026-03-27 1:11 ` [PATCH v6 4/4] target/i386: emulate: remove redundant logging for unmapped MMIO access Mohamed Mediouni
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=20260327011152.4126-2-mohamed@unpredictable.fr \
--to=mohamed@unpredictable.fr \
--cc=pbarbuda@microsoft.com \
--cc=pbonzini@redhat.com \
--cc=philmd@linaro.org \
--cc=pierrick.bouvier@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 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.