Received: by 10.223.164.202 with SMTP id h10csp907530wrb; Thu, 9 Nov 2017 17:03:50 -0800 (PST) X-Google-Smtp-Source: ABhQp+TQgCcLpArdDmHf+xE5JaxpBOnj5ErmldRa3jatqv5KjJ7GY5omil8fxvCGQRmBO0kZhol0 X-Received: by 10.84.174.1 with SMTP id q1mr2311650plb.220.1510275830558; Thu, 09 Nov 2017 17:03:50 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1510275830; cv=none; d=google.com; s=arc-20160816; b=LJpFed8QUyrKVZZDGI+A8+Dl9OU599HbOaSmveGzdZ2eEg15aIN5If3z0boypjbaPa XW3Bjt2AL1HXf6WiglFspupFyovt4HoqTAfrl+s4KUYWK5EEyB6SpF4sfp78SUIk4VeD BAkoTpFGDaasEJQV5zzEWJuPKHS72GnSEPeuF4ovL5R+roXSe8PQEl/ahjBdOuwDZ3/h fFWjylUXSB6SvPaTf+2t0qf+HTZAS2tCXH4oBH+bHzL6w+ZhIKjEjoX5IksghYsYdn8e Jk/xdinjUIJlOZTtlV/NXTskupCkhYz0QTM/lfVnVq5du9paMGmVovZp8CHgnd0zz/AL H5Dw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:message-id:content-language :content-transfer-encoding:in-reply-to:mime-version:user-agent:date :from:references:cc:to:subject:arc-authentication-results; bh=H++ZPDX5YdVijcEHA2blgzB7XMDW4qwFY96xgZZcq2Y=; b=A8qUOVsHjOFPeIV5uIkFQ5xEaEtfTQOclxP+y4ehrtUfYOOnj5IiXR9IoHzDiult48 W3svCBIuoHz0QyuTITyxGZYZ3iWS07GL3CdqJtKP7dExCWN09qakvG0MBfX0h8ZbVlZt kpMYlHmEWpS3KtV7PPT5MwmhLRoTlDWTdzBNis+lVghZOTTiXOKE9Cw2O7H9oxCbRks8 s6wNNvYkHXIB4hEnp8YbzwYM8osDFsSk4X+lK7TfAAr7MdLT+eu7F1FqYXHdrlMLQ0jw 3YLUfQQR4XXggUBvj8rRF6d0y/jzonWd34j5LxLZeyPAJqVKA/bEatRtWV0EOR7TKLOU htOg== 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=ibm.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id j18si7546048pga.407.2017.11.09.17.03.38; Thu, 09 Nov 2017 17:03:50 -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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=ibm.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755431AbdKJBCu (ORCPT + 83 others); Thu, 9 Nov 2017 20:02:50 -0500 Received: from mx0b-001b2d01.pphosted.com ([148.163.158.5]:59390 "EHLO mx0a-001b2d01.pphosted.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1755317AbdKJBCt (ORCPT ); Thu, 9 Nov 2017 20:02:49 -0500 Received: from pps.filterd (m0098413.ppops.net [127.0.0.1]) by mx0b-001b2d01.pphosted.com (8.16.0.21/8.16.0.21) with SMTP id vAA11hnH082689 for ; Thu, 9 Nov 2017 20:02:48 -0500 Received: from e06smtp11.uk.ibm.com (e06smtp11.uk.ibm.com [195.75.94.107]) by mx0b-001b2d01.pphosted.com with ESMTP id 2e4wb8m40t-1 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=NOT) for ; Thu, 09 Nov 2017 20:02:48 -0500 Received: from localhost by e06smtp11.uk.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Fri, 10 Nov 2017 01:02:46 -0000 Received: from b06cxnps4074.portsmouth.uk.ibm.com (9.149.109.196) by e06smtp11.uk.ibm.com (192.168.101.141) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted; Fri, 10 Nov 2017 01:02:44 -0000 Received: from d06av25.portsmouth.uk.ibm.com (d06av25.portsmouth.uk.ibm.com [9.149.105.61]) by b06cxnps4074.portsmouth.uk.ibm.com (8.14.9/8.14.9/NCO v10.0) with ESMTP id vAA12hLL36569096; Fri, 10 Nov 2017 01:02:43 GMT Received: from d06av25.portsmouth.uk.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 2EC4311C05E; Fri, 10 Nov 2017 00:57:39 +0000 (GMT) Received: from d06av25.portsmouth.uk.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 1EB2D11C054; Fri, 10 Nov 2017 00:57:38 +0000 (GMT) Received: from [9.79.179.106] (unknown [9.79.179.106]) by d06av25.portsmouth.uk.ibm.com (Postfix) with ESMTP; Fri, 10 Nov 2017 00:57:37 +0000 (GMT) Subject: Re: [PATCH] powerpc/powernv: Fix IMC_MAX_PMU macro To: Michael Ellerman , Anju T Sudhakar Cc: linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org References: <1510229426-5547-1-git-send-email-anju@linux.vnet.ibm.com> <877euzp3mo.fsf@concordia.ellerman.id.au> From: Madhavan Srinivasan Date: Fri, 10 Nov 2017 06:32:41 +0530 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0 MIME-Version: 1.0 In-Reply-To: <877euzp3mo.fsf@concordia.ellerman.id.au> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US X-TM-AS-GCONF: 00 x-cbid: 17111001-0040-0000-0000-0000040CA16A X-IBM-AV-DETECTION: SAVI=unused REMOTE=unused XFE=unused x-cbparentid: 17111001-0041-0000-0000-000020AF4828 Message-Id: <6429f614-ab35-3c7f-6bfd-1f9f59545bbb@linux.vnet.ibm.com> X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2017-11-09_11:,, signatures=0 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 impostorscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1707230000 definitions=main-1711100012 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Friday 10 November 2017 02:32 AM, Michael Ellerman wrote: > Anju T Sudhakar writes: > >> IMC_MAX_PMU is used for static storage (per_nest_pmu_arr) which holds >> nest pmu information. Current value for the macro is 32 based on >> the initial number of nest pmu units supported by the nest microcode. >> Currently 29 nest units are enabled based on the system configuration. >> But going forward, microcode could support more nest units (max of 64 >> nest units). Hence fix the value for the macro. > There should be no reason to have a hard coded limit. > > We should just fix the code to dynamically size the array based on > what's found in the device tree. Yes. My bad. Device tree handling part is done in the platform/powernv side and this data (total number of nest pmus) can be extended from there. Will work on it. Thanks for review comments. Maddy > > cheers > >> Fixes:8f95faaac56c1 ('powerpc/powernv: Detect and create IMC device') >> Signed-off-by: Anju T Sudhakar >> --- >> arch/powerpc/include/asm/imc-pmu.h | 2 +- >> 1 file changed, 1 insertion(+), 1 deletion(-) >> >> diff --git a/arch/powerpc/include/asm/imc-pmu.h b/arch/powerpc/include/asm/imc-pmu.h >> index 7f74c28..f9f0f2e 100644 >> --- a/arch/powerpc/include/asm/imc-pmu.h >> +++ b/arch/powerpc/include/asm/imc-pmu.h >> @@ -23,7 +23,7 @@ >> /* >> * For static allocation of some of the structures. >> */ >> -#define IMC_MAX_PMUS 32 >> +#define IMC_MAX_PMUS 64 >> >> /* >> * Compatibility macros for IMC devices >> -- >> 2.7.4 From 1583623854881687927@xxx Thu Nov 09 21:03:17 +0000 2017 X-GM-THRID: 1583590402295806271 X-Gmail-Labels: Inbox,Category Forums,HistoricalUnread