From: Alexander Graf <agraf@suse.de>
To: qemu-devel@nongnu.org
Cc: "Paolo Bonzini" <pbonzini@redhat.com>,
"Richard Henderson" <rth@twiddle.net>,
"Eduardo Habkost" <ehabkost@redhat.com>,
"Andrew Jones" <drjones@redhat.com>,
"Andreas Färber" <afaerber@suse.de>
Subject: [Qemu-devel] [PATCH] target-i386: enable kvm_pv_unhalt by default
Date: Wed, 13 Sep 2017 16:39:58 +0200 [thread overview]
Message-ID: <20170913143958.86385-1-agraf@suse.de> (raw)
Commit f010bc643a (target-i386: add feature kvm_pv_unhalt) introduced the
kvm_pv_unhalt feature but didn't enable it by default.
Without kvm_pv_unhalt we see a measurable degradation in scheduling
performance, so enabling it by default does make sense IMHO. This patch
just flips it to default to on by default.
[With kvm_pv_unhalt disabled]
$ perf bench sched messaging -l 10000
Total time: 8.573 [sec]
[With kvm_pv_unhalt enabled]
$ perf bench sched messaging -l 10000
Total time: 4.416 [sec]
Signed-off-by: Alexander Graf <agraf@suse.de>
---
Let's ask everyone who was involved back then whether this is a feature
that is good to enable by default. My measurements imply so, but who knows...
Also, I'd kindly like to ask for guidance on how to make this reasonably
well backwards compatible. I assume we only want to flip the default in newer
machine models? If so, how?
---
target/i386/cpu.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/target/i386/cpu.c b/target/i386/cpu.c
index 69676e13e1..c58f4ab24f 100644
--- a/target/i386/cpu.c
+++ b/target/i386/cpu.c
@@ -1581,6 +1581,7 @@ static PropValue kvm_default_props[] = {
{ "kvm-asyncpf", "on" },
{ "kvm-steal-time", "on" },
{ "kvm-pv-eoi", "on" },
+ { "kvm-pv-unhalt", "on" },
{ "kvmclock-stable-bit", "on" },
{ "x2apic", "on" },
{ "acpi", "off" },
--
2.12.3
next reply other threads:[~2017-09-13 14:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-13 14:39 Alexander Graf [this message]
2017-09-14 1:09 ` [Qemu-devel] [PATCH] target-i386: enable kvm_pv_unhalt by default Eduardo Habkost
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=20170913143958.86385-1-agraf@suse.de \
--to=agraf@suse.de \
--cc=afaerber@suse.de \
--cc=drjones@redhat.com \
--cc=ehabkost@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
/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).