From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:49026) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Qyp5T-0002UF-Gz for qemu-devel@nongnu.org; Wed, 31 Aug 2011 14:00:32 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Qyp5S-0004SG-CB for qemu-devel@nongnu.org; Wed, 31 Aug 2011 14:00:31 -0400 Received: from mail-bw0-f45.google.com ([209.85.214.45]:62023) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Qyp5S-0004S4-5S for qemu-devel@nongnu.org; Wed, 31 Aug 2011 14:00:30 -0400 Received: by bkbzv3 with SMTP id zv3so1088141bkb.4 for ; Wed, 31 Aug 2011 11:00:28 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: References: <4E5DF31A.1@redhat.com> Date: Wed, 31 Aug 2011 11:00:28 -0700 Message-ID: From: Dhaval Giani Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: Re: [Qemu-devel] [PATCH, RFC] trace: implement guest tracepoint passthrough List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Blue Swirl Cc: qemu-devel , =?ISO-8859-1?Q?Llu=EDs?= , Avi Kivity , Stefan Hajnoczi On Wed, Aug 31, 2011 at 10:58 AM, Blue Swirl wrote: > On Wed, Aug 31, 2011 at 8:38 AM, Avi Kivity wrote: >> On 08/26/2011 10:06 PM, Blue Swirl wrote: >>> >>> Let guests inject tracepoint data via fw_cfg device. >>> >>> >> >> At least on x86, fw_cfg is pretty slow, involving multiple exits. =A0IMO= , for >> kvm, even one exit per tracepoint is too high. =A0We need to use a share= d >> memory transport with a way to order guest/host events later on (by usin= g a >> clock). > > This could be an easy way, if the guest always had access to an > accurate clock, but that may not be the case. > >>From what I understand, kvmclock should be good enoguh for this purpose. That is what I am using. Dhaval