Received: by 10.223.185.116 with SMTP id b49csp7326458wrg; Thu, 1 Mar 2018 03:50:10 -0800 (PST) X-Google-Smtp-Source: AG47ELszKUsWA8or1nOd0Qm0Kv0kTgvhoWGf34ephONe/F1PB5n9aa74xfqIbh29pvumpfci58y7 X-Received: by 2002:a17:902:8214:: with SMTP id x20-v6mr1678698pln.182.1519905010031; Thu, 01 Mar 2018 03:50:10 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1519905009; cv=none; d=google.com; s=arc-20160816; b=fKSXBhfUX4Vxu3A4KxcbGHi9QLWoHW/j6fyHIcQXrW82WrnJWOqCc6krXzZH8ZczXW 5XWCCwrw06xjNaWK4ZflEXIxZgBEiwHVdHYOYWnvP4qo40b16rM1suGhW3b+JrEdAsIf drj6P9TP25dTOO4cCks6bD+GA7yZ/KlU2rT/3fojRec/I0byOk0b9tsNhbGVqhh09SIC tVVUVdBlh0YIfFXM5Rj4nWYgqHA0N0WogGZH4FAdN8a56Y/Fgfrhr61D+0f54poZzlQ+ skZsNx8siZWLkxcd+cIFlR/SXKBMT46LOfZxN1ggpo0a2M8auvzAam9Xy0SsAmjwhfFb VvqQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:arc-authentication-results; bh=ZtmQExHAFAQR68gguzCHLUg0VLq/ExRDo71HUoSVk98=; b=jHXlY13lPs0SFV069+X7KVAAEHbpAzNsw9kuXsBvaJZqWx5+gxg/Igx2ZSZxZ8rT3y PYiyjbSA9G8H5Y+aOXbIcaSnV5TPLJlARK2tInZspvelTMlWjbcqlR8YLYL5/uuaw6tU 7VolvIluSXohudL7A8Mq4ubrIlaAOxYt0aSuaYKPNbhPgKQYIUOon1pcPEflCYnEvydn vhqewALnLEorJ/lj8dFOlM2jIbdenHJ1aoXIMbEDsOdyfcO3L4Oe185w2rvbEPKcraMg yA2uPpkTfbluj47aVdJ8XThI4rMfKC4yw/CDdmOvJ2/x2LQeY46tHNL5adn+VsyJMPR0 CThg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id f8si2320639pgs.667.2018.03.01.03.49.54; Thu, 01 Mar 2018 03:50:09 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S967811AbeCALtS (ORCPT + 99 others); Thu, 1 Mar 2018 06:49:18 -0500 Received: from usa-sjc-mx-foss1.foss.arm.com ([217.140.101.70]:36930 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S967708AbeCALtR (ORCPT ); Thu, 1 Mar 2018 06:49:17 -0500 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.72.51.249]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id B553E1529; Thu, 1 Mar 2018 03:49:16 -0800 (PST) Received: from lakrids.cambridge.arm.com (usa-sjc-imap-foss1.foss.arm.com [10.72.51.249]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 7DCDB3F318; Thu, 1 Mar 2018 03:49:14 -0800 (PST) Date: Thu, 1 Mar 2018 11:49:12 +0000 From: Mark Rutland To: Saravana Kannan Cc: robh@kernel.org, mathieu.poirier@linaro.org, Suzuki K Poulose , peterz@infradead.org, jonathan.cameron@huawei.com, will.deacon@arm.com, linux-kernel@vger.kernel.org, marc.zyngier@arm.com, sudeep.holla@arm.com, frowand.list@gmail.com, leo.yan@linaro.org, linux-arm-kernel@lists.infradead.org Subject: Re: [PATCH v11 8/8] perf: ARM DynamIQ Shared Unit PMU support Message-ID: <20180301114911.fundyuqxtj5klk4e@lakrids.cambridge.arm.com> References: <20180102112533.13640-1-suzuki.poulose@arm.com> <20180102112533.13640-9-suzuki.poulose@arm.com> <5A90B77E.8040105@codeaurora.org> <20180225143653.peb4quk3ha5h3t5x@salmiak> <5A972A7D.9020301@codeaurora.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5A972A7D.9020301@codeaurora.org> User-Agent: NeoMutt/20170113 (1.7.2) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Feb 28, 2018 at 02:17:33PM -0800, Saravana Kannan wrote: > On 02/25/2018 06:36 AM, Mark Rutland wrote: > > On Fri, Feb 23, 2018 at 04:53:18PM -0800, Saravana Kannan wrote: > > > On 01/02/2018 03:25 AM, Suzuki K Poulose wrote: > > > > +static void dsu_pmu_event_update(struct perf_event *event) > > > > +{ > > > > + struct hw_perf_event *hwc = &event->hw; > > > > + u64 delta, prev_count, new_count; > > > > + > > > > + do { > > > > + /* We may also be called from the irq handler */ > > > > + prev_count = local64_read(&hwc->prev_count); > > > > + new_count = dsu_pmu_read_counter(event); > > > > + } while (local64_cmpxchg(&hwc->prev_count, prev_count, new_count) != > > > > + prev_count); > > > > + delta = (new_count - prev_count) & DSU_PMU_COUNTER_MASK(hwc->idx); > > > > + local64_add(delta, &event->count); > > > > +} > > > > + > > > > +static void dsu_pmu_read(struct perf_event *event) > > > > +{ > > > > + dsu_pmu_event_update(event); > > > > +} > > > > > I sent out a patch that'll allow PMUs to set an event flag to avoid > > > unnecessary smp calls when the event can be read from any CPU. You could > > > just always set that if you can't have multiple DSU's running the kernel (I > > > don't know if the current ARM designs support having multiple DSUs in a > > > SoC/system) or set it if associated_cpus == cpu_present_mask. > > > > As-is, that won't be safe, given the read function calls the event_update() > > function, which has side-effects on hwc->prec_count and event->count. Those > > need to be serialized somehow. > > You have to grab the dsu_pmu->pmu_lock spin lock anyway because the system > registers are shared across all CPUs. I believe that lock is currently superfluous, because the perf core ensures operations are cpu-affine, and have interrupts disabled in most cases (thanks to the context lock). > So, just expanding it a bit to lock the hwc->prev_count and > event->count updated doesn't seem to be any worse. In fact, it's > better than sending pointless IPIs. That's a fair point. I'll leave it to Suzuki to decide. > The local64_read/cmpxchg/add etc makes sense when you have per-cpu system > registers like in the case of the ARM CPU PMU registers. It doesn't really > buy us much for registers shared across the CPUs. Theoretically, because operations are currnetly cpu-affine, they potentially reduce the overhead of sertialization and synchronization. In practice for arm64 they're just LL/SC loops, so I agree we don't lose much. Thanks, Mark.