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=-9.0 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,MENTIONS_GIT_HOSTING,SIGNED_OFF_BY,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 BFD3CC43219 for ; Fri, 3 May 2019 07:01:51 +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 3C67A205F4 for ; Fri, 3 May 2019 07:01:51 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 3C67A205F4 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 44wNNF3TQ2zDqQh for ; Fri, 3 May 2019 17:01:49 +1000 (AEST) Received: from ozlabs.org (bilbo.ozlabs.org [203.11.71.1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by lists.ozlabs.org (Postfix) with ESMTPS id 44wNK55wFfzDqPP for ; Fri, 3 May 2019 16:59:05 +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 44wNK55DB0z9sB8; Fri, 3 May 2019 16:59:05 +1000 (AEST) X-powerpc-patch-notification: thanks X-powerpc-patch-commit: a913e5e8b43be1d3897a141ce61c1ec071cad89c X-Patchwork-Hint: ignore In-Reply-To: <20181127082452.8307-2-anju@linux.vnet.ibm.com> To: Anju T Sudhakar From: Michael Ellerman Subject: Re: [PATCH] powerpc/perf: Return accordingly on invalid chip-id in Message-Id: <44wNK55DB0z9sB8@ozlabs.org> Date: Fri, 3 May 2019 16:59:05 +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: maddy@linux.vnet.ibm.com, linuxppc-dev@lists.ozlabs.org, anju@linux.vnet.ibm.com, dan.carpenter@oracle.com Errors-To: linuxppc-dev-bounces+linuxppc-dev=archiver.kernel.org@lists.ozlabs.org Sender: "Linuxppc-dev" On Tue, 2018-11-27 at 08:24:52 UTC, Anju T Sudhakar wrote: > Nest hardware counter memory resides in a per-chip reserve-memory. > During nest_imc_event_init(), chip-id of the event-cpu is considered to > calculate the base memory addresss for that cpu. Return, proper error > condition if the chip_id calculated is invalid. > > Reported-by: Dan Carpenter > Fixes: 885dcd709ba91 ("powerpc/perf: Add nest IMC PMU support") > Reviewed-by: Madhavan Srinivasan > Signed-off-by: Anju T Sudhakar Applied to powerpc next, thanks. https://git.kernel.org/powerpc/c/a913e5e8b43be1d3897a141ce61c1ec0 cheers