From: Peter Kieser <peter@kieser.ca>
To: Wanpeng Li <wanpeng.li@hotmail.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
David Matlack <dmatlack@google.com>, kvm <kvm@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v4 0/3] KVM: Dynamic Halt-Polling
Date: Sat, 29 Aug 2015 17:13:07 -0700 [thread overview]
Message-ID: <55E24A93.3070606@kieser.ca> (raw)
In-Reply-To: <BLU436-SMTP11063B4FF1EBA21F57E3C79806D0@phx.gbl>
[-- Attachment #1: Type: text/plain, Size: 615 bytes --]
On 2015-08-29 4:55 PM, Wanpeng Li wrote:
> On 8/30/15 6:26 AM, Peter Kieser wrote:
>> Thanks, Wanpeng. Applied this to Linux 3.18 and seeing much higher
>> CPU usage (200%) for qemu 2.4.0 process on a Windows 10 x64 guest.
>> qemu parameters:
>
> Thanks for the report. If Paolo's patch "kvm: add halt_poll_ns module
> parameter" is applied on your 3.18? Btw, do you test the linux guest?
No high CPU usage on Linux guests. Following patch series are applied
(in order):
* kvm: add halt_poll_ns module parameter
* KVM: make halt_poll_ns static
* KVM: Dynamic Halt-Polling v4
-Peter
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4311 bytes --]
next prev parent reply other threads:[~2015-08-30 0:13 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-27 9:47 [PATCH v4 0/3] KVM: Dynamic Halt-Polling Wanpeng Li
[not found] ` <55E221B2.3000702@kieser.ca>
2015-08-29 22:21 ` Wanpeng Li
2015-08-29 22:26 ` Peter Kieser
2015-08-29 23:55 ` Wanpeng Li
2015-08-30 0:13 ` Peter Kieser [this message]
2015-08-30 0:21 ` Wanpeng Li
2015-08-31 7:44 ` Wanpeng Li
2015-08-31 7:47 ` Wanpeng Li
2015-09-01 21:45 ` David Matlack
2015-09-01 22:30 ` Wanpeng Li
2015-09-01 22:34 ` David Matlack
2015-09-01 22:58 ` Wanpeng Li
2015-09-01 23:24 ` David Matlack
2015-09-02 0:29 ` Wanpeng Li
2015-09-02 1:49 ` David Matlack
2015-09-02 6:01 ` Wanpeng Li
-- strict thread matches above, loose matches on Subject: below --
2015-08-27 9:52 Wanpeng 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=55E24A93.3070606@kieser.ca \
--to=peter@kieser.ca \
--cc=dmatlack@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=wanpeng.li@hotmail.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 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.