From: Avi Kivity <avi@qumranet.com>
To: carsteno@de.ibm.com
Cc: "Yang, Sheng" <sheng.yang@intel.com>,
kvm@vger.kernel.org, Hollis Blanchard <hollisb@us.ibm.com>,
Christian Ehrhardt <ehrhardt@linux.vnet.ibm.com>,
xiantao.zhang@intel.com, kvm-ppc@vger.kernel.org
Subject: Re: [PATCH 2/5] kvmtrace: make cycle calculation architecture aware
Date: Sun, 13 Jul 2008 15:41:04 +0000 [thread overview]
Message-ID: <487A2210.5020602@qumranet.com> (raw)
In-Reply-To: <48770CEF.6090102@de.ibm.com>
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.
This is all in-kernel, so no syscalls. Since I doubt you need sub-ns
granularity for kvmtrace, can we do without an arch hook?
--
error compiling committee.c: too many arguments to function
WARNING: multiple messages have this Message-ID (diff)
From: Avi Kivity <avi@qumranet.com>
To: carsteno@de.ibm.com
Cc: "Yang, Sheng" <sheng.yang@intel.com>,
kvm@vger.kernel.org, Hollis Blanchard <hollisb@us.ibm.com>,
Christian Ehrhardt <ehrhardt@linux.vnet.ibm.com>,
xiantao.zhang@intel.com, kvm-ppc@vger.kernel.org
Subject: Re: [PATCH 2/5] kvmtrace: make cycle calculation architecture aware
Date: Sun, 13 Jul 2008 18:41:04 +0300 [thread overview]
Message-ID: <487A2210.5020602@qumranet.com> (raw)
In-Reply-To: <48770CEF.6090102@de.ibm.com>
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.
This is all in-kernel, so no syscalls. Since I doubt you need sub-ns
granularity for kvmtrace, can we do without an arch hook?
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2008-07-13 15:41 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-07 13:56 [PATCH 0/5] kvmtrace: add powerpc support for KVM_TRACE ehrhardt
2008-07-07 13:56 ` ehrhardt
2008-07-07 13:56 ` [PATCH 1/5] kvmtrace: Remove use of bit fields in kvm trace structure v3 ehrhardt
2008-07-07 13:56 ` ehrhardt
2008-07-07 13:56 ` [PATCH 2/5] kvmtrace: make cycle calculation architecture aware ehrhardt
2008-07-07 13:56 ` ehrhardt
2008-07-07 15:45 ` Hollis Blanchard
2008-07-07 15:45 ` Hollis Blanchard
2008-07-09 8:25 ` Christian Ehrhardt
2008-07-09 8:25 ` Christian Ehrhardt
2008-07-07 16:37 ` Hollis Blanchard
2008-07-07 16:37 ` Hollis Blanchard
2008-07-09 9:17 ` Christian Ehrhardt
2008-07-09 9:17 ` Christian Ehrhardt
2008-07-09 15:03 ` Hollis Blanchard
2008-07-09 15:03 ` Hollis Blanchard
2008-07-10 10:22 ` Yang, Sheng
2008-07-10 10:22 ` Yang, Sheng
2008-07-10 10:24 ` Yang, Sheng
2008-07-10 10:24 ` Yang, Sheng
2008-07-10 13:32 ` Avi Kivity
2008-07-10 13:32 ` Avi Kivity
2008-07-11 1:06 ` Yang, Sheng
2008-07-11 1:06 ` Yang, Sheng
2008-07-11 7:34 ` Carsten Otte
2008-07-11 7:34 ` Carsten Otte
2008-07-11 15:19 ` Hollis Blanchard
2008-07-11 15:19 ` Hollis Blanchard
2008-07-13 15:41 ` Avi Kivity [this message]
2008-07-13 15:41 ` Avi Kivity
2008-07-14 7:44 ` Christian Borntraeger
2008-07-14 7:44 ` Christian Borntraeger
2008-07-07 13:56 ` [PATCH 3/5] kvmppc: kvmtrace: enable KVM_TRACE building for powerpc ehrhardt
2008-07-07 13:56 ` ehrhardt
2008-07-07 13:56 ` [PATCH 4/5] kvmppc: kvmtrace: adds trace points for ppc tlb activity v2 ehrhardt
2008-07-07 13:56 ` ehrhardt
2008-07-07 13:56 ` [PATCH 5/5] kvmppc: kvmtrace: trace powerpc instruction emulation ehrhardt
2008-07-07 13:56 ` ehrhardt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=487A2210.5020602@qumranet.com \
--to=avi@qumranet.com \
--cc=carsteno@de.ibm.com \
--cc=ehrhardt@linux.vnet.ibm.com \
--cc=hollisb@us.ibm.com \
--cc=kvm-ppc@vger.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=sheng.yang@intel.com \
--cc=xiantao.zhang@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.