From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754383AbbLKP1n (ORCPT ); Fri, 11 Dec 2015 10:27:43 -0500 Received: from mga11.intel.com ([192.55.52.93]:35966 "EHLO mga11.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752737AbbLKP1m (ORCPT ); Fri, 11 Dec 2015 10:27:42 -0500 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.20,414,1444719600"; d="scan'208";a="616466322" From: Alexander Shishkin To: Peter Zijlstra Cc: Ingo Molnar , linux-kernel@vger.kernel.org, vince@deater.net, eranian@google.com, Arnaldo Carvalho de Melo , Mathieu Poirier Subject: Re: [PATCH v0 3/5] perf: Introduce instruction trace filtering In-Reply-To: <20151211150236.GU6356@twins.programming.kicks-ass.net> References: <1449840998-29902-1-git-send-email-alexander.shishkin@linux.intel.com> <1449840998-29902-4-git-send-email-alexander.shishkin@linux.intel.com> <20151211150236.GU6356@twins.programming.kicks-ass.net> User-Agent: Notmuch/0.21 (http://notmuchmail.org) Emacs/24.5.1 (x86_64-pc-linux-gnu) Date: Fri, 11 Dec 2015 17:27:22 +0200 Message-ID: <87wpslatut.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 Peter Zijlstra writes: > On Fri, Dec 11, 2015 at 03:36:36PM +0200, Alexander Shishkin wrote: >> +static int perf_event_itrace_filters_setup(struct perf_event *event) >> +{ >> + int ret; >> + >> + /* >> + * We can't use event_function_call() here, because that would >> + * require ctx::mutex, but one of our callers is called with >> + * mm::mmap_sem down, which would cause an inversion, see bullet >> + * (2) in put_event(). >> + */ >> + do { >> + if (READ_ONCE(event->state) != PERF_EVENT_STATE_ACTIVE) { >> + ret = event->pmu->itrace_filter_setup(event); >> + break; > > So this is tricky, if its not active it can be any moment, there is > nothing serializing against that. Indeed. But we should be able to call pmu::itrace_filter_setup() multiple times, so if after this we re-check that the event is still inactive, we can return, otherwise proceed with the cross-call. Does this make sense? > >> + } >> + >> + /* matches smp_wmb() in event_sched_in() */ >> + smp_rmb(); >> + >> + ret = cpu_function_call(READ_ONCE(event->oncpu), >> + __perf_event_itrace_filters_setup, event); > > This otoh, running with IRQs disabled on the CPU the thing is active on > guarantees it will not become inactive -- nothing can come in and switch > it off. > >> + } while (ret == -EAGAIN); >> + >> + return ret; >> +}