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]
Date:	Thu, 30 Jun 2011 10:21:54 -0300
From:	Glauber Costa <glommer@...hat.com>
To:	Eric B Munson <emunson@...bm.net>
CC:	Avi Kivity <avi@...hat.com>, kvm@...r.kernel.org,
	linux-kernel@...r.kernel.org, Rik van Riel <riel@...hat.com>,
	Jeremy Fitzhardinge <jeremy.fitzhardinge@...rix.com>,
	Peter Zijlstra <peterz@...radead.org>,
	Anthony Liguori <aliguori@...ibm.com>
Subject: Re: [PATCH v3 2/9] KVM-HDR Add constant to represent KVM MSRs enabled
 bit

On 06/30/2011 09:59 AM, Eric B Munson wrote:
> On Thu, 30 Jun 2011, Avi Kivity wrote:
>
>> On 06/30/2011 12:56 AM, Eric B Munson wrote:
>>> My mail provider seems to have dropped patch 1 of the series so I can't reply
>>> directly to it, please add my Tested-by there as well.
>>
>> How did you test it then?
>>
>
> I built host and guest kernels with the patches and pinned a while(1) and the
> CPU thread from qemu to CPU 2 on the host.  I then started the same while(1)
> process in guest and verified that I see ~50% steal time reported.
>
> I then built 2.6.39 (just the code I had present) on the guest and time it
> while it was competing with the while(1) on the host for CPU time.  Next I
> built the guest kernel with STEAL_TIME=N and reran the kernel compile to make
> sure that there weren't any huge variations in performace.
>
> Eric
I think what Avi means is, it won't even compile without PATCH 1/9. If 
you don't have it, how could you test it ?

--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ