From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S934280AbdACJlL (ORCPT ); Tue, 3 Jan 2017 04:41:11 -0500 Received: from bombadil.infradead.org ([198.137.202.9]:58296 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751960AbdACJlI (ORCPT ); Tue, 3 Jan 2017 04:41:08 -0500 Date: Tue, 3 Jan 2017 10:40:59 +0100 From: Peter Zijlstra To: Jiri Olsa Cc: lkml , Ingo Molnar , Andi Kleen , Alexander Shishkin , Arnaldo Carvalho de Melo , Vince Weaver Subject: Re: [PATCH 2/4] perf/x86: Fix period for non sampling events Message-ID: <20170103094059.GC3093@worktop> References: <1482931866-6018-1-git-send-email-jolsa@kernel.org> <1482931866-6018-3-git-send-email-jolsa@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1482931866-6018-3-git-send-email-jolsa@kernel.org> User-Agent: Mutt/1.5.22.1 (2013-10-16) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Dec 28, 2016 at 02:31:04PM +0100, Jiri Olsa wrote: > When in counting mode we setup the counter with the > longest possible period and read the value with read > syscall. > > We also still setup the PMI to be triggered when such > counter overflow to reconfigure it. > > We also get PEBS interrupt if such counter has precise_ip > set (which makes no sense, but it's possible). I think we should reject non sampling pebs events, as you say they make no sense what so ever.