From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1751220AbdBONha (ORCPT <rfc822;w@1wt.eu>);
        Wed, 15 Feb 2017 08:37:30 -0500
Received: from merlin.infradead.org ([205.233.59.134]:59268 "EHLO
        merlin.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1750782AbdBONh3 (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Wed, 15 Feb 2017 08:37:29 -0500
Date: Wed, 15 Feb 2017 14:37:21 +0100
From: Peter Zijlstra <peterz@infradead.org>
To: Alexander Shishkin <alexander.shishkin@linux.intel.com>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
        Ingo Molnar <mingo@redhat.com>, linux-kernel@vger.kernel.org,
        vince@deater.net, eranian@google.com,
        Arnaldo Carvalho de Melo <acme@infradead.org>,
        Borislav Petkov <bp@suse.de>, Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH 2/2] perf/x86/intel/pt: Fail event creation if VMX
 operation is on
Message-ID: <20170215133721.GX6515@twins.programming.kicks-ass.net>
References: <20170214132416.26400-1-alexander.shishkin@linux.intel.com>
 <20170214132416.26400-3-alexander.shishkin@linux.intel.com>
 <20170214174734.GC4458@kernel.org>
 <87poijkg25.fsf@ashishki-desk.ger.corp.intel.com>
 <20170215085621.GQ25813@worktop.programming.kicks-ass.net>
 <87d1ejk3jt.fsf@ashishki-desk.ger.corp.intel.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <87d1ejk3jt.fsf@ashishki-desk.ger.corp.intel.com>
User-Agent: Mutt/1.5.23.1 (2014-03-12)
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Wed, Feb 15, 2017 at 03:05:10PM +0200, Alexander Shishkin wrote:
> Peter Zijlstra <peterz@infradead.org> writes:
> 
> > On Wed, Feb 15, 2017 at 10:34:58AM +0200, Alexander Shishkin wrote:
> >
> >> Well, we can't make the limitation go away. You'll still have to stop
> >> kvms to get any 'meaningful' PT data.
> >
> > Why would you need to stop all VMs in order to get your !VM data? Sure,
> > you get black holes where the VM runs, but we should be able to see
> > everything else.
> 
> No, what I mean is that if you run kvm prior to starting perf record,
> which I assume is the case for acme, your entire session is a black
> hole. The VMXON happens pretty early on, you can open /dev/kvm,
> ioctl(KVM_CREATE_VM) on it and that will do a VMXON already.

kvm_intel has a vmm_exclusive parameter, if you set that to 0 is
_should_ behave much better.