Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933579AbeAKLKM (ORCPT + 1 other); Thu, 11 Jan 2018 06:10:12 -0500 Received: from mx1.redhat.com ([209.132.183.28]:44686 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932073AbeAKLKL (ORCPT ); Thu, 11 Jan 2018 06:10:11 -0500 Date: Thu, 11 Jan 2018 12:10:01 +0100 From: Jiri Olsa To: "Liang, Kan" Cc: peterz@infradead.org, mingo@redhat.com, acme@kernel.org, linux-kernel@vger.kernel.org, tglx@linutronix.de, eranian@google.com, ak@linux.intel.com Subject: Re: [RESEND PATCH V2 3/4] perf/x86/intel: drain PEBS buffer in event read Message-ID: <20180111111001.GC31767@krava> References: <1515424516-143728-1-git-send-email-kan.liang@intel.com> <1515424516-143728-4-git-send-email-kan.liang@intel.com> <20180110103929.GB18942@krava> <6bb19af0-24e5-d711-cb6f-139eb99253c1@linux.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <6bb19af0-24e5-d711-cb6f-139eb99253c1@linux.intel.com> User-Agent: Mutt/1.9.1 (2017-09-22) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.30]); Thu, 11 Jan 2018 11:10:11 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Return-Path: On Wed, Jan 10, 2018 at 09:31:56AM -0500, Liang, Kan wrote: > > > On 1/10/2018 5:39 AM, Jiri Olsa wrote: > > On Mon, Jan 08, 2018 at 07:15:15AM -0800, kan.liang@intel.com wrote: > > > From: Kan Liang > > > > > > When the PEBS interrupt threshold is larger than one, there is no way to > > > get exact auto-reload times and value needed for event update unless > > > flush the PEBS buffer. > > > > > > Drain the PEBS buffer in event read when large PEBS is enabled. > > > > > > For the threshold is one, even auto-reload is enabled, it doesn't need > > > to be specially handled. Because auto-reload is only effect when event > > > overflow. There is no overflow in event read. > > > > > > Signed-off-by: Kan Liang > > > --- > > > arch/x86/events/intel/core.c | 9 +++++++++ > > > arch/x86/events/intel/ds.c | 10 ++++++++++ > > > arch/x86/events/perf_event.h | 2 ++ > > > 3 files changed, 21 insertions(+) > > > > > > diff --git a/arch/x86/events/intel/core.c b/arch/x86/events/intel/core.c > > > index 09c26a4..bdc35f8 100644 > > > --- a/arch/x86/events/intel/core.c > > > +++ b/arch/x86/events/intel/core.c > > > @@ -2060,6 +2060,14 @@ static void intel_pmu_del_event(struct perf_event *event) > > > intel_pmu_pebs_del(event); > > > } > > > +static void intel_pmu_read_event(struct perf_event *event) > > > +{ > > > + if (event->attr.precise_ip) > > > + return intel_pmu_pebs_read(event); > > > > check for (event->hw.flags & PERF_X86_EVENT_AUTO_RELOAD) > > would be more accurate? > > > > It will narrow down the events. > But considering the readability, I think it would be better to use > precise_ip.The exposed functions in ds.c should be generic functions for all > PEBS events, not specific case. > I think _AUTO_RELOAD looks too specific. hum, but the PEBS drain is specific just for PERF_X86_EVENT_AUTO_RELOAD events, right? wrt readability maybe you could add function like: bool pebs_drain_before_read(struct perf_event *event) { return event->hw.flags & PERF_X86_EVENT_AUTO_RELOAD; } thanks, jirka