From mboxrd@z Thu Jan 1 00:00:00 1970 From: Paul Mackerras Subject: Re: [PATCH 02/12] KVM: PPC: Book3S HV: Accumulate timing information for real-mode code Date: Fri, 27 Mar 2015 22:47:32 +1100 Message-ID: <20150327114732.GB18766@iris.ozlabs.ibm.com> References: <1427426996-17651-1-git-send-email-paulus@samba.org> <1427426996-17651-3-git-send-email-paulus@samba.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Alexander Graf To: kvm-ppc@vger.kernel.org, kvm@vger.kernel.org Return-path: Received: from ozlabs.org ([103.22.144.67]:55136 "EHLO ozlabs.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752708AbbC0Lrm (ORCPT ); Fri, 27 Mar 2015 07:47:42 -0400 Content-Disposition: inline In-Reply-To: <1427426996-17651-3-git-send-email-paulus@samba.org> Sender: kvm-owner@vger.kernel.org List-ID: On Fri, Mar 27, 2015 at 02:29:46PM +1100, Paul Mackerras wrote: > This reads the timebase at various points in the real-mode guest > entry/exit code and uses that to accumulate total, minimum and > maximum time spent in those parts of the code. Currently these > times are accumulated per vcpu in 5 parts of the code: I just realized that this is going to give bogus results if we have a non-zero timebase offset, so ignore this patch for now. I'll fix it and repost. Paul. From mboxrd@z Thu Jan 1 00:00:00 1970 From: Paul Mackerras Date: Fri, 27 Mar 2015 11:47:32 +0000 Subject: Re: [PATCH 02/12] KVM: PPC: Book3S HV: Accumulate timing information for real-mode code Message-Id: <20150327114732.GB18766@iris.ozlabs.ibm.com> List-Id: References: <1427426996-17651-1-git-send-email-paulus@samba.org> <1427426996-17651-3-git-send-email-paulus@samba.org> In-Reply-To: <1427426996-17651-3-git-send-email-paulus@samba.org> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: kvm-ppc@vger.kernel.org, kvm@vger.kernel.org Cc: Alexander Graf On Fri, Mar 27, 2015 at 02:29:46PM +1100, Paul Mackerras wrote: > This reads the timebase at various points in the real-mode guest > entry/exit code and uses that to accumulate total, minimum and > maximum time spent in those parts of the code. Currently these > times are accumulated per vcpu in 5 parts of the code: I just realized that this is going to give bogus results if we have a non-zero timebase offset, so ignore this patch for now. I'll fix it and repost. Paul.