Re: [PATCH 2/5] kvmtrace: make cycle calculation architecture aware

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, 2008-07-11 at 09:34 +0200, Carsten Otte wrote:
> Avi Kivity wrote:
> > What is the overhead of ktime_get()?
> I think I'd like an arch specific timestamp. This way we could use our 
> clock-cycle-granularity-non-privileged-timestamp instruction ;-). If 
> we need a common implementation, I don't think there's much difference 
> between different syscalls in terms of overhead.

Carsten tried to elaborate on IRC, but the summary is that a) time on
S390 is complicated, and b) they have a time source that yields finer
granularity than nanoseconds. So I'm inclined to say fine, we can have
an arch-specific hook, and almost every arch will just use
getnstimeofday().

-- 
Hollis Blanchard
IBM Linux Technology Center

--
To unsubscribe from this list: send the line "unsubscribe kvm-ppc" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [KVM Development]     [KVM ARM]     [KVM ia64]     [Linux Virtualization]     [Linux USB Devel]     [Linux Video]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Big List of Linux Books]

  Powered by Linux