From: Alexander Graf <agraf@suse.de>
To: qemu-devel@nongnu.org
Cc: qemu-ppc@nongnu.org
Subject: [Qemu-devel] [PATCH] PPC: KVM: Don't tell the user about missing SPR syncs
Date: Mon, 3 Feb 2014 22:53:02 +0100 [thread overview]
Message-ID: <1391464382-60634-1-git-send-email-agraf@suse.de> (raw)
We sync a lot of SPRs automatically between KVM and QEMU now. Some
of these only matter on newer hardware, some only matter on HV KVM.
With the current code runnign on my reasonably recent PR KVM kernel
I get a lot of SPR synchronization warnings though:
$ ./ppc64-softmmu/qemu-system-ppc64 -nographic -enable-kvm
Warning: Unable to set SPR 17 to KVM: Invalid argument
Warning: Unable to set SPR 29 to KVM: Invalid argument
Warning: Unable to set SPR 157 to KVM: Invalid argument
Warning: Unable to set SPR 308 to KVM: Invalid argument
Warning: Unable to set SPR 309 to KVM: Invalid argument
Warning: Unable to set SPR 318 to KVM: Invalid argument
Warning: Unable to set SPR 770 to KVM: Invalid argument
Warning: Unable to set SPR 945 to KVM: Invalid argument
Warning: Unable to set SPR 946 to KVM: Invalid argument
Warning: Unable to set SPR 1013 to KVM: Invalid argument
Warning: Unable to set SPR 17 to KVM: Invalid argument
Warning: Unable to set SPR 29 to KVM: Invalid argument
Warning: Unable to set SPR 157 to KVM: Invalid argument
Warning: Unable to set SPR 308 to KVM: Invalid argument
Warning: Unable to set SPR 309 to KVM: Invalid argument
Warning: Unable to set SPR 318 to KVM: Invalid argument
Warning: Unable to set SPR 770 to KVM: Invalid argument
Warning: Unable to set SPR 945 to KVM: Invalid argument
Warning: Unable to set SPR 946 to KVM: Invalid argument
Warning: Unable to set SPR 1013 to KVM: Invalid argument
Eventually we want to have something like a "verbose" flag that allows
us to get these warnings when we see something goes wrong. But until
then they do more harm than good exposed to casual users, so let's move
them to debug prints.
Signed-off-by: Alexander Graf <agraf@suse.de>
---
target-ppc/kvm.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/target-ppc/kvm.c b/target-ppc/kvm.c
index 8f3f0bf..dce2156 100644
--- a/target-ppc/kvm.c
+++ b/target-ppc/kvm.c
@@ -480,7 +480,7 @@ static void kvm_get_one_spr(CPUState *cs, uint64_t id, int spr)
ret = kvm_vcpu_ioctl(cs, KVM_GET_ONE_REG, ®);
if (ret != 0) {
- fprintf(stderr, "Warning: Unable to retrieve SPR %d from KVM: %s\n",
+ DPRINTF("Warning: Unable to retrieve SPR %d from KVM: %s\n",
spr, strerror(errno));
} else {
switch (id & KVM_REG_SIZE_MASK) {
@@ -529,7 +529,7 @@ static void kvm_put_one_spr(CPUState *cs, uint64_t id, int spr)
ret = kvm_vcpu_ioctl(cs, KVM_SET_ONE_REG, ®);
if (ret != 0) {
- fprintf(stderr, "Warning: Unable to set SPR %d to KVM: %s\n",
+ DPRINTF("Warning: Unable to set SPR %d to KVM: %s\n",
spr, strerror(errno));
}
}
--
1.8.1.4
next reply other threads:[~2014-02-03 21:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-03 21:53 Alexander Graf [this message]
2014-02-04 2:05 ` [Qemu-devel] [Qemu-ppc] [PATCH] PPC: KVM: Don't tell the user about missing SPR syncs Alexey Kardashevskiy
2014-02-04 7:32 ` Alexander Graf
2014-02-04 4:12 ` [Qemu-devel] [PATCH] PPC: KVM: suppress warnings about not supported SPRs Alexey Kardashevskiy
2014-02-04 7:38 ` Alexander Graf
2014-02-04 7:44 ` Alexey Kardashevskiy
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=1391464382-60634-1-git-send-email-agraf@suse.de \
--to=agraf@suse.de \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@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 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).