|
|
|
|
|
|
|
|
|
|
xen-devel
Re: [Xen-devel] Re: [PATCH 3/5] x86/pvclock: add vsyscall implementation
To: |
Glauber Costa <glommer@xxxxxxxxxx> |
Subject: |
Re: [Xen-devel] Re: [PATCH 3/5] x86/pvclock: add vsyscall implementation |
From: |
Avi Kivity <avi@xxxxxxxxxx> |
Date: |
Wed, 28 Oct 2009 11:34:09 +0200 |
Cc: |
Jeremy Fitzhardinge <jeremy@xxxxxxxx>, Jeremy Fitzhardinge <jeremy.fitzhardinge@xxxxxxxxxx>, kurt.hackel@xxxxxxxxxx, the arch/x86 maintainers <x86@xxxxxxxxxx>, Dan Magenheimer <dan.magenheimer@xxxxxxxxxx>, Linux Kernel Mailing List <linux-kernel@xxxxxxxxxxxxxxx>, Xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, Keir Fraser <keir.fraser@xxxxxxxxxxxxx>, zach.brown@xxxxxxxxxx, Glauber de Oliveira Costa <gcosta@xxxxxxxxxx>, Ingo Molnar <mingo@xxxxxxxxxx>, chris.mason@xxxxxxxxxx |
Delivery-date: |
Wed, 28 Oct 2009 02:35:00 -0700 |
Envelope-to: |
www-data@xxxxxxxxxxxxxxxxxxx |
In-reply-to: |
<20091028092900.GG3627@xxxxxxxxxxxxxxxxxxxxxx> |
List-help: |
<mailto:xen-devel-request@lists.xensource.com?subject=help> |
List-id: |
Xen developer discussion <xen-devel.lists.xensource.com> |
List-post: |
<mailto:xen-devel@lists.xensource.com> |
List-subscribe: |
<http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe> |
List-unsubscribe: |
<http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe> |
References: |
<4f079cd6-0872-4cb5-832b-ee6a46841192@default> <4AE739DA.20601@xxxxxxxx> <4AE7DC04.7080706@xxxxxxxxxx> <20091028092900.GG3627@xxxxxxxxxxxxxxxxxxxxxx> |
Sender: |
xen-devel-bounces@xxxxxxxxxxxxxxxxxxx |
User-agent: |
Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.4pre) Gecko/20091014 Fedora/3.0-2.8.b4.fc11 Thunderbird/3.0b4 |
On 10/28/2009 11:29 AM, Glauber Costa wrote:
How can you reliably measure performance in a virtualized environment?
If we loop gettimeofday(), I would expect the vsyscall-based version not to show
up in strace, right?
Much better to have an API for this. Life is hacky enough already.
--
error compiling committee.c: too many arguments to function
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
<Prev in Thread] |
Current Thread |
[Next in Thread>
|
- Re: [Xen-devel] Re: [PATCH 3/5] x86/pvclock: add vsyscall implementation, (continued)
- Re: [Xen-devel] Re: [PATCH 3/5] x86/pvclock: add vsyscall implementation, Avi Kivity
- Re: [Xen-devel] Re: [PATCH 3/5] x86/pvclock: add vsyscall implementation, Jeremy Fitzhardinge
- Re: [Xen-devel] Re: [PATCH 3/5] x86/pvclock: add vsyscall implementation, Avi Kivity
- Re: [Xen-devel] Re: [PATCH 3/5] x86/pvclock: add vsyscall implementation, Jeremy Fitzhardinge
- Re: [Xen-devel] Re: [PATCH 3/5] x86/pvclock: add vsyscall implementation, Avi Kivity
- Re: [Xen-devel] Re: [PATCH 3/5] x86/pvclock: add vsyscall implementation, Jeremy Fitzhardinge
- RE: [Xen-devel] Re: [PATCH 3/5] x86/pvclock: add vsyscall implementation, Dan Magenheimer
- Re: [Xen-devel] Re: [PATCH 3/5] x86/pvclock: add vsyscall implementation, Jeremy Fitzhardinge
- Re: [Xen-devel] Re: [PATCH 3/5] x86/pvclock: add vsyscall implementation, Avi Kivity
- Re: [Xen-devel] Re: [PATCH 3/5] x86/pvclock: add vsyscall implementation, Glauber Costa
- Re: [Xen-devel] Re: [PATCH 3/5] x86/pvclock: add vsyscall implementation,
Avi Kivity <=
- Re: [Xen-devel] Re: [PATCH 3/5] x86/pvclock: add vsyscall implementation, Jeremy Fitzhardinge
- Re: [Xen-devel] Re: [PATCH 3/5] x86/pvclock: add vsyscall implementation, Avi Kivity
- Re: [Xen-devel] Re: [PATCH 3/5] x86/pvclock: add vsyscall implementation, Chris Mason
- RE: [Xen-devel] Re: [PATCH 3/5] x86/pvclock: add vsyscall implementation, Dan Magenheimer
- Re: [Xen-devel] Re: [PATCH 3/5] x86/pvclock: add vsyscall implementation, Avi Kivity
- RE: [Xen-devel] Re: [PATCH 3/5] x86/pvclock: add vsyscall implementation, Dan Magenheimer
- RE: [Xen-devel] Re: [PATCH 3/5] x86/pvclock: add vsyscall implementation, Dan Magenheimer
- [Xen-devel] pvclock implementation in pv_ops kernel: why not __native_read_tsc()?, Dan Magenheimer
- [Xen-devel] Re: pvclock implementation in pv_ops kernel: why not __native_read_tsc()?, Jeremy Fitzhardinge
|
|
|
|
|