From: Marcelo Tosatti <mtosatti@redhat.com>
To: "Li, Bin (Bin)" <bin.bl.li@alcatel-lucent.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"Jatania, Neel (Neel)" <Neel.Jatania@alcatel-lucent.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Enhancement for PLE handler in KVM
Date: Fri, 7 Mar 2014 22:54:16 -0300 [thread overview]
Message-ID: <20140308015416.GA26349@amt.cnet> (raw)
In-Reply-To: <72F5E0D8DB6D83469579E473AD72DB23779F88CA@US70UWXCHMBA01.zam.alcatel-lucent.com>
On Fri, Mar 07, 2014 at 10:08:52PM +0000, Li, Bin (Bin) wrote:
> Fully agree.
> It will be a very helpful feature to make ple setting per VM.
> This feature will provide more flexible control to the VM user. All KVM user will love to have it.
>
> The enhancement we proposed is neither overlapping nor conflicting with this feature. The enhancement is targeting to provide the best real time performance to the guest OS.
> There will be more and more embedded system migrating to KVM. Especially in the telecom industry. And a lot of existing system will be running on top of customized embedded OS which significant different from generic OS (either linux or windows ).
The point Paolo raised is that the hypercall interface can increase CPU
consumption significantly. It would be good to understand why is
the interface the only way to fix the problem.
> Is there any concern regarding to the enhancement we need to address? Or more work need to be done?
It was not clear from the information you provided that increasing PLE
window alone is not sufficient to reduce clock jitter in the guest
to acceptable levels (from 400ms to <10ms).
BTW, can you explain the clock jitter measure?
next prev parent reply other threads:[~2014-03-08 1:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <53061044.2000009@alcatel-lucent.com>
[not found] ` <530B9637.6030708@alcatel-lucent.com>
2014-03-03 18:24 ` Enhancement for PLE handler in KVM Li, Bin (Bin)
2014-03-03 19:20 ` Paolo Bonzini
2014-03-05 14:17 ` Li, Bin (Bin)
2014-03-05 14:49 ` Paolo Bonzini
2014-03-05 21:16 ` Li, Bin (Bin)
2014-03-07 3:06 ` Marcelo Tosatti
2014-03-07 14:26 ` Li, Bin (Bin)
2014-03-07 17:41 ` Marcelo Tosatti
2014-03-07 22:08 ` Li, Bin (Bin)
2014-03-08 1:54 ` Marcelo Tosatti [this message]
[not found] ` <531F19D7.6030909@alcatel-lucent.com>
2014-03-11 16:14 ` Paolo Bonzini
2014-03-12 13:05 ` Li, Bin (Bin)
2014-03-24 14:12 Raghavendra KT
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=20140308015416.GA26349@amt.cnet \
--to=mtosatti@redhat.com \
--cc=Neel.Jatania@alcatel-lucent.com \
--cc=bin.bl.li@alcatel-lucent.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.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).