From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751218AbdBONJe (ORCPT ); Wed, 15 Feb 2017 08:09:34 -0500 Received: from mga01.intel.com ([192.55.52.88]:23839 "EHLO mga01.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750820AbdBONJd (ORCPT ); Wed, 15 Feb 2017 08:09:33 -0500 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.35,166,1484035200"; d="scan'208";a="1095040862" From: Alexander Shishkin To: Arnaldo Carvalho de Melo Cc: Peter Zijlstra , Ingo Molnar , linux-kernel@vger.kernel.org, vince@deater.net, eranian@google.com, Arnaldo Carvalho de Melo , Borislav Petkov , Thomas Gleixner Subject: Re: [PATCH 2/2] perf/x86/intel/pt: Fail event creation if VMX operation is on In-Reply-To: <20170215125128.GB4020@kernel.org> 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> <20170215125128.GB4020@kernel.org> User-Agent: Notmuch/0.23.5 (http://notmuchmail.org) Emacs/24.5.1 (x86_64-pc-linux-gnu) Date: Wed, 15 Feb 2017 15:09:25 +0200 Message-ID: <87a89nk3cq.fsf@ashishki-desk.ger.corp.intel.com> MIME-Version: 1.0 Content-Type: text/plain Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Arnaldo Carvalho de Melo writes: > Em Wed, Feb 15, 2017 at 10:34:58AM +0200, Alexander Shishkin escreveu: >> Arnaldo Carvalho de Melo writes: >> > Em Tue, Feb 14, 2017 at 03:24:16PM +0200, Alexander Shishkin escreveu: >> > Yeah, I saw that as well, and Andi told me about this limitation, so, >> > for quite a while now, everytime I need to test PT on the only machine I >> > have with it, I have to stop my kvm sessions :-\ > >> > Thanks for working on this! > >> Well, we can't make the limitation go away. You'll still have to stop >> kvms to get any 'meaningful' PT data. > > If we can't make the limitation go away we need to at least warn users > instead of let 'perf record' sit there doing nothing and then at the end > return as if everything went well only to when trying to use 'perf > script' nothing will appear. I tend to like Peter's idea about PERF_RECORD_AUX with a PAUSED flag to indicate this. Regards, -- Alex