From: Xiaoyao Li <xiaoyao.li@intel.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: "Marcelo Tosatti" <mtosatti@redhat.com>,
qemu-devel@nongnu.org,
"Daniel P . Berrangé" <berrange@redhat.com>,
"Zhenzhong Duan" <zhenzhong.duan@intel.com>,
"Xiaoyao Li" <xiaoyao.li@intel.com>
Subject: [PATCH] i386/tdx: Use .has_gpa field to check if the gpa is valid
Date: Thu, 10 Jul 2025 22:15:12 +0800 [thread overview]
Message-ID: <20250710141512.170302-1-xiaoyao.li@intel.com> (raw)
There is actually the .has_gpa field when translating the QAPI data
type GuestPanicInformationTdx to C structure.
Stop using the magic number -1 as the indicator for no valid gpa.
Instead just use .has_gpa field.
Signed-off-by: Xiaoyao Li <xiaoyao.li@intel.com>
---
system/runstate.c | 2 +-
target/i386/kvm/tdx.c | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/system/runstate.c b/system/runstate.c
index 38900c935a35..87cdcab4f388 100644
--- a/system/runstate.c
+++ b/system/runstate.c
@@ -690,7 +690,7 @@ void qemu_system_guest_panicked(GuestPanicInformation *info)
" error code: 0x%" PRIx32 " error message:\"%s\"\n",
info->u.tdx.error_code, message);
g_free(message);
- if (info->u.tdx.gpa != -1ull) {
+ if (info->u.tdx.has_gpa) {
qemu_log_mask(LOG_GUEST_ERROR, "Additional error information "
"can be found at gpa page: 0x%" PRIx64 "\n",
info->u.tdx.gpa);
diff --git a/target/i386/kvm/tdx.c b/target/i386/kvm/tdx.c
index 370a9b6e656c..14704eb523c5 100644
--- a/target/i386/kvm/tdx.c
+++ b/target/i386/kvm/tdx.c
@@ -1298,7 +1298,7 @@ int tdx_handle_report_fatal_error(X86CPU *cpu, struct kvm_run *run)
uint64_t reg_mask = run->system_event.data[R_ECX];
char *message = NULL;
uint64_t *tmp;
- uint64_t gpa = -1ull;
+ uint64_t gpa = 0;
bool has_gpa = false;
if (error_code & 0xffff) {
--
2.43.0
next reply other threads:[~2025-07-10 14:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-10 14:15 Xiaoyao Li [this message]
2025-07-10 14:25 ` [PATCH] i386/tdx: Use .has_gpa field to check if the gpa is valid Daniel P. Berrangé
2025-07-11 3:22 ` Duan, Zhenzhong
2025-09-12 5:53 ` Xiaoyao Li
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=20250710141512.170302-1-xiaoyao.li@intel.com \
--to=xiaoyao.li@intel.com \
--cc=berrange@redhat.com \
--cc=mtosatti@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=zhenzhong.duan@intel.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).