From: David Edmondson <david.edmondson@oracle.com> To: qemu-devel@nongnu.org Cc: qemu-trivial@nongnu.org, Paolo Bonzini <pbonzini@redhat.com>, kvm@vger.kernel.org, David Edmondson <david.edmondson@oracle.com> Subject: [PATCH] accel: kvm: clarify that extra exit data is hexadecimal Date: Wed, 28 Apr 2021 15:24:31 +0100 [thread overview] Message-ID: <20210428142431.266879-1-david.edmondson@oracle.com> (raw) When dumping the extra exit data provided by KVM, make it clear that the data is hexadecimal. At the same time, zero-pad the output. Signed-off-by: David Edmondson <david.edmondson@oracle.com> --- accel/kvm/kvm-all.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/accel/kvm/kvm-all.c b/accel/kvm/kvm-all.c index b6d9f92f15..93d7cbfeaf 100644 --- a/accel/kvm/kvm-all.c +++ b/accel/kvm/kvm-all.c @@ -2269,7 +2269,7 @@ static int kvm_handle_internal_error(CPUState *cpu, struct kvm_run *run) int i; for (i = 0; i < run->internal.ndata; ++i) { - fprintf(stderr, "extra data[%d]: %"PRIx64"\n", + fprintf(stderr, "extra data[%d]: 0x%016"PRIx64"\n", i, (uint64_t)run->internal.data[i]); } } -- 2.30.2
WARNING: multiple messages have this Message-ID (diff)
From: David Edmondson <david.edmondson@oracle.com> To: qemu-devel@nongnu.org Cc: qemu-trivial@nongnu.org, Paolo Bonzini <pbonzini@redhat.com>, David Edmondson <david.edmondson@oracle.com>, kvm@vger.kernel.org Subject: [PATCH] accel: kvm: clarify that extra exit data is hexadecimal Date: Wed, 28 Apr 2021 15:24:31 +0100 [thread overview] Message-ID: <20210428142431.266879-1-david.edmondson@oracle.com> (raw) When dumping the extra exit data provided by KVM, make it clear that the data is hexadecimal. At the same time, zero-pad the output. Signed-off-by: David Edmondson <david.edmondson@oracle.com> --- accel/kvm/kvm-all.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/accel/kvm/kvm-all.c b/accel/kvm/kvm-all.c index b6d9f92f15..93d7cbfeaf 100644 --- a/accel/kvm/kvm-all.c +++ b/accel/kvm/kvm-all.c @@ -2269,7 +2269,7 @@ static int kvm_handle_internal_error(CPUState *cpu, struct kvm_run *run) int i; for (i = 0; i < run->internal.ndata; ++i) { - fprintf(stderr, "extra data[%d]: %"PRIx64"\n", + fprintf(stderr, "extra data[%d]: 0x%016"PRIx64"\n", i, (uint64_t)run->internal.data[i]); } } -- 2.30.2
next reply other threads:[~2021-04-28 14:24 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-04-28 14:24 David Edmondson [this message] 2021-04-28 14:24 ` [PATCH] accel: kvm: clarify that extra exit data is hexadecimal David Edmondson 2021-04-28 16:03 ` Philippe Mathieu-Daudé 2021-04-30 13:07 ` Laurent Vivier
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=20210428142431.266879-1-david.edmondson@oracle.com \ --to=david.edmondson@oracle.com \ --cc=kvm@vger.kernel.org \ --cc=pbonzini@redhat.com \ --cc=qemu-devel@nongnu.org \ --cc=qemu-trivial@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: linkBe 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.