From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751829AbeBYOiM (ORCPT ); Sun, 25 Feb 2018 09:38:12 -0500 Received: from foss.arm.com ([217.140.101.70]:41480 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751814AbeBYOiI (ORCPT ); Sun, 25 Feb 2018 09:38:08 -0500 Date: Sun, 25 Feb 2018 14:38:03 +0000 From: Mark Rutland To: Saravana Kannan Cc: Peter Zijlstra , Ingo Molnar , Arnaldo Carvalho de Melo , Alexander Shishkin , Jiri Olsa , Namhyung Kim , avilaj@codeaurora.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH v1 2/2] perf/core: Add support for PMUs that can be read from any CPU Message-ID: <20180225143802.denbkubqjg2dc7af@salmiak> References: <1519431578-11995-1-git-send-email-skannan@codeaurora.org> <1519431578-11995-2-git-send-email-skannan@codeaurora.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1519431578-11995-2-git-send-email-skannan@codeaurora.org> User-Agent: NeoMutt/20170113 (1.7.2) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Feb 23, 2018 at 04:19:38PM -0800, Saravana Kannan wrote: > Some PMUs events can be read from any CPU. So allow the PMU to mark > events as such. For these events, we don't need to reject reads or > make smp calls to the event's CPU and cause unnecessary wake ups. > > Good examples of such events would be events from caches shared across > all CPUs. I think that if we need to generalize PERF_EV_CAP_READ_ACTIVE_PKG, it would be better to give events a pointer to a cpumask. That could then cover all cases quite trivially: static int __perf_event_read_cpu(struct perf_event *event, int event_cpu) { int local_cpu = smp_processor_id(); if (event->read_mask && cpumask_test_cpu(local_cpu, event->read_mask)) event_cpu = local_cpu; return event_cpu; } ... in the PERF_EV_CAP_READ_ACTIVE_PKG case, we can use the exiting(?) package masks, and more generally we can re-use the PMU's affinit mask if it has one. That said, I see that many pmu::read() implementations have side-effects on hwc->prev_count, and event->count, so I worry that this won't be sfe in general (e.g. if we race with the IRQ handler on another CPU). Thanks, Mark.