Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Date:   Fri, 13 Mar 2020 04:51:02 -0700
From:   Andi Kleen <andi@firstfloor.org>
To:     Andy Lutomirski <luto@amacapital.net>
Cc:     Andi Kleen <andi@firstfloor.org>, x86@kernel.org,
        linux-kernel@vger.kernel.org, Andi Kleen <ak@linux.intel.com>
Subject: Re: [PATCH] x86: Add trace points to (nearly) all vectors
Message-ID: <20200313115100.3gdbfxkplrbe6wvy@two.firstfloor.org>
References: <20200312231916.132753-1-andi@firstfloor.org>
 <742AF79F-BAE4-4E6C-944D-10C3E6F66CD0@amacapital.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <742AF79F-BAE4-4E6C-944D-10C3E6F66CD0@amacapital.net>
User-Agent: NeoMutt/20170113 (1.7.2)
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On Thu, Mar 12, 2020 at 04:39:04PM -0700, Andy Lutomirski wrote:
> 
> > On Mar 12, 2020, at 4:19 PM, Andi Kleen <andi@firstfloor.org> wrote:
> > 
> > ﻿From: Andi Kleen <ak@linux.intel.com>
> > 
> > In some scenarios it can be useful to count or trace every kernel
> > entry.
> 
> Can you elaborate?  What problem does this solve?

So that we know how often or where kernel entries happen,
how long every kernel execution is, and also can do an accurate break
down.

> 
> > Most entry paths are covered by trace points already,
> > but some of the more obscure entry points do not have
> > trace points.
> > 
> > The most common uncovered one was KVM async page fault.
> 
> NAK.  This path is going away. 

Okay. Can you provide details? When will it go away?

Anyways KVM async is just one case, my patch covers lots of other cases
too. Even if KVM async goes away it still makes sense
for the other entry points and can be easily rebased (just drop
that hunk)

-Andi