linux-kernel - Re: [PATCH RFC 0/7] kvm pvtimer

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20171208151014.GE12069@x230.dumpdata.com>
Date:   Fri, 8 Dec 2017 10:10:14 -0500
From:   Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>
To:     Quan Xu <quan.xu0@...il.com>
Cc:     pbonzini@...hat.com, rkrcmar@...hat.com, yang.zhang.wz@...il.com,
        kvm@...r.kernel.org, linux-kernel@...r.kernel.org,
        Ben Luo <bn0418@...il.com>
Subject: Re: [PATCH RFC 0/7] kvm pvtimer

On Fri, Dec 08, 2017 at 04:39:43PM +0800, Quan Xu wrote:
> From: Ben Luo <bn0418@...il.com>
> 
> This patchset introduces a new paravirtualized mechanism to reduce VM-exit
> caused by guest timer accessing.

And how bad is this blib in arming the timer?

And how often do you get this timer to be armed? OR better yet - what
are the workloads in which you found this VMExit to be painful?

Thanks. Or better yet - what
are the workloads in which you found this VMExit to be painful?