linux-kernel - Re: Enhancement for PLE handler in KVM

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20140308015416.GA26349@amt.cnet>
Date:	Fri, 7 Mar 2014 22:54:16 -0300
From:	Marcelo Tosatti <mtosatti@...hat.com>
To:	"Li, Bin (Bin)" <bin.bl.li@...atel-lucent.com>
Cc:	Paolo Bonzini <pbonzini@...hat.com>,
	"kvm@...r.kernel.org" <kvm@...r.kernel.org>,
	"Jatania, Neel (Neel)" <Neel.Jatania@...atel-lucent.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: Enhancement for PLE handler in KVM

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?

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/