From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-8.8 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,MENTIONS_GIT_HOSTING,SIGNED_OFF_BY,SPF_HELO_NONE,SPF_PASS autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id B20A2C2BA19 for ; Mon, 6 Apr 2020 13:22:09 +0000 (UTC) Received: from lists.ozlabs.org (lists.ozlabs.org [203.11.71.2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 0B38023107 for ; Mon, 6 Apr 2020 13:21:59 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 0B38023107 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=ellerman.id.au Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=linuxppc-dev-bounces+linuxppc-dev=archiver.kernel.org@lists.ozlabs.org Received: from lists.ozlabs.org (lists.ozlabs.org [IPv6:2401:3900:2:1::3]) by lists.ozlabs.org (Postfix) with ESMTP id 48wrmN6DYpzDqbw for ; Mon, 6 Apr 2020 23:21:56 +1000 (AEST) Received: from ozlabs.org (bilbo.ozlabs.org [IPv6:2401:3900:2:1::2]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by lists.ozlabs.org (Postfix) with ESMTPS id 48wrPf04lNzDqbt for ; Mon, 6 Apr 2020 23:05:42 +1000 (AEST) Authentication-Results: lists.ozlabs.org; dmarc=none (p=none dis=none) header.from=ellerman.id.au Received: by ozlabs.org (Postfix, from userid 1034) id 48wrPW5nRgz9sSK; Mon, 6 Apr 2020 23:05:35 +1000 (AEST) X-powerpc-patch-notification: thanks X-powerpc-patch-commit: a36e8ba60b991d563677227f172db69e030797e6 In-Reply-To: <20200313055238.8656-1-anju@linux.vnet.ibm.com> To: Anju T Sudhakar From: Michael Ellerman Subject: Re: [PATCH v4 1/2] powerpc/perf: Implement a global lock to avoid races between trace, core and thread imc events. Message-Id: <48wrPW5nRgz9sSK@ozlabs.org> Date: Mon, 6 Apr 2020 23:05:35 +1000 (AEST) X-BeenThere: linuxppc-dev@lists.ozlabs.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: linuxppc-dev@lists.ozlabs.org, harihare@in.ibm.com, maddy@linux.vnet.ibm.com, anju@linux.vnet.ibm.com Errors-To: linuxppc-dev-bounces+linuxppc-dev=archiver.kernel.org@lists.ozlabs.org Sender: "Linuxppc-dev" On Fri, 2020-03-13 at 05:52:37 UTC, Anju T Sudhakar wrote: > IMC(In-memory Collection Counters) does performance monitoring in > two different modes, i.e accumulation mode(core-imc and thread-imc events), > and trace mode(trace-imc events). A cpu thread can either be in > accumulation-mode or trace-mode at a time and this is done via the LDBAR > register in POWER architecture. The current design does not address the > races between thread-imc and trace-imc events. > > Patch implements a global id and lock to avoid the races between > core, trace and thread imc events. With this global id-lock > implementation, the system can either run core, thread or trace imc > events at a time. i.e. to run any core-imc events, thread/trace imc events > should not be enabled/monitored. > > Signed-off-by: Anju T Sudhakar Series applied to powerpc next, thanks. https://git.kernel.org/powerpc/c/a36e8ba60b991d563677227f172db69e030797e6 cheers