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 3/4] whpx: i386: trace unsupported MSR accesses
Date: Fri, 27 Mar 2026 02:11:51 +0100 [thread overview]
Message-ID: <20260327011152.4126-4-mohamed@unpredictable.fr> (raw)
In-Reply-To: <20260327011152.4126-1-mohamed@unpredictable.fr>
Not actionable information for users, so stop
having it displayed unconditionally.
Signed-off-by: Mohamed Mediouni <mohamed@unpredictable.fr>
Reviewed-by: Pierrick Bouvier <pierrick.bouvier@linaro.org>
---
meson.build | 1 +
target/i386/whpx/trace-events | 1 +
target/i386/whpx/trace.h | 2 ++
target/i386/whpx/whpx-all.c | 5 +++--
4 files changed, 7 insertions(+), 2 deletions(-)
create mode 100644 target/i386/whpx/trace-events
create mode 100644 target/i386/whpx/trace.h
diff --git a/meson.build b/meson.build
index 6f77309075..8bf1da3169 100644
--- a/meson.build
+++ b/meson.build
@@ -3692,6 +3692,7 @@ if have_system or have_user
'target/hppa',
'target/i386',
'target/i386/kvm',
+ 'target/i386/whpx',
'target/loongarch',
'target/mips/tcg',
'target/ppc',
diff --git a/target/i386/whpx/trace-events b/target/i386/whpx/trace-events
new file mode 100644
index 0000000000..ebdfa34b28
--- /dev/null
+++ b/target/i386/whpx/trace-events
@@ -0,0 +1 @@
+whpx_unsupported_msr_access(uint32_t msr, int is_write) "WHPX: Unsupported MSR access (0x%x), IsWrite=%i"
diff --git a/target/i386/whpx/trace.h b/target/i386/whpx/trace.h
new file mode 100644
index 0000000000..b7c090deff
--- /dev/null
+++ b/target/i386/whpx/trace.h
@@ -0,0 +1,2 @@
+/* SPDX-License-Identifier: GPL-2.0-or-later */
+#include "trace/trace-target_i386_whpx.h"
diff --git a/target/i386/whpx/whpx-all.c b/target/i386/whpx/whpx-all.c
index e8fe65f581..9a405118c5 100644
--- a/target/i386/whpx/whpx-all.c
+++ b/target/i386/whpx/whpx-all.c
@@ -41,6 +41,7 @@
#include "emulate/x86_emu.h"
#include "emulate/x86_flags.h"
#include "emulate/x86_mmu.h"
+#include "trace.h"
#include <winhvplatform.h>
@@ -1931,8 +1932,8 @@ int whpx_vcpu_run(CPUState *cpu)
1 : 3;
if (!is_known_msr) {
- warn_report("WHPX: Unsupported MSR access (0x%x), IsWrite=%i",
- vcpu->exit_ctx.MsrAccess.MsrNumber, vcpu->exit_ctx.MsrAccess.AccessInfo.IsWrite);
+ trace_whpx_unsupported_msr_access(vcpu->exit_ctx.MsrAccess.MsrNumber,
+ vcpu->exit_ctx.MsrAccess.AccessInfo.IsWrite);
}
hr = whp_dispatch.WHvSetVirtualProcessorRegisters(
--
2.50.1 (Apple Git-155)
next prev parent reply other threads:[~2026-03-27 1:12 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 ` [PATCH v6 1/4] meson.build: remove i386-softmmu WHPX support Mohamed Mediouni
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 ` Mohamed Mediouni [this message]
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-4-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.