Received: by 2002:a05:6a10:16a7:0:0:0:0 with SMTP id gp39csp1147682pxb; Fri, 20 Nov 2020 02:18:54 -0800 (PST) X-Google-Smtp-Source: ABdhPJwPUy0wUmGvTTSC4c8VugVjMXol8meFFoEBxIXT1M0Olxd2h28dIQw1vxCX4AcoPgOjbPcm X-Received: by 2002:a17:906:27c2:: with SMTP id k2mr16195832ejc.211.1605867534220; Fri, 20 Nov 2020 02:18:54 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1605867534; cv=none; d=google.com; s=arc-20160816; b=lsIHk/pfegxm8wEVQlMhIBTqmgFV8TC43YkIY7TCoWm66DwqXUJx2d5KqbJlyIxoJ5 HV6DjBn7HqblBc69plfSl/s9y/DT82m+Vd2YG+S6Eh8m78IDDbGJPvBcWw9FT78w7oG4 mhhVs3mRP9EsgSah1yvaaX4P/3LzCRjUzeM0F8/5tASqxgAh6f3UXx+6G3nC3oJVGLfX 8HUKyIZOjDRP5mt1f/YVZNGMYcYAGYtzrE5TRyeqJfBnnNwWYwSPJPUeSo/YCNU5xkS1 nJ1zS2hpLcgRn3DG2jUdEfQmaztRPmbgYdlcpmLqSCEkfezHlFA0fUgNhyEXcBTHoqLP v4gQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:content-language :in-reply-to:mime-version:user-agent:date:message-id:from:references :cc:to:subject; bh=ZakykszYNQVYXRM1ov5MHHL09K8MoQPrWkZKfYEdSLo=; b=zoWB/RI3Kelt25Zn4VTUdMYn6x+QUwZLml0MtixXmQbZzsF3wB5ldhpVyNWwIRXrWM SJgxnd/ShPxaZUIoHgy3NBlxH5AiQrAclBHm5TacZfpsyzVxARcCpv+ut+lo3EciLRQZ 5eB+nBIko9rLtoI8zbq7LG6qFleDdAjKN+YhLHt3qmI1fFt+fcAlfiDGOIvsAH+A4G7p JVzpy9WuK/EtTDbj0ew0Y7jiHE6gPqkm3MhtIueUVbzh/nPDEcpwyg1z4qYy1P3MU+uy E5IZJ8q3sdZzmQYNQsK5MUI/ExkaF+tfvlNRYWdUDS65kEbGu7FLOqvKqidhVwJoL/LF ZwyQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=arm.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id p13si1438518ejz.147.2020.11.20.02.18.31; Fri, 20 Nov 2020 02:18:54 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=arm.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727061AbgKTKOx (ORCPT + 99 others); Fri, 20 Nov 2020 05:14:53 -0500 Received: from foss.arm.com ([217.140.110.172]:46614 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726172AbgKTKOw (ORCPT ); Fri, 20 Nov 2020 05:14:52 -0500 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id 830031042; Fri, 20 Nov 2020 02:14:51 -0800 (PST) Received: from [10.57.26.201] (unknown [10.57.26.201]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id B19D03F70D; Fri, 20 Nov 2020 02:14:49 -0800 (PST) Subject: Re: AMU extension v1 support for cortex A76, A77, A78 CPUs To: Marc Zyngier Cc: Neeraj Upadhyay , mark.rutland@arm.com, suzuki.poulose@arm.com, ionela.voinescu@arm.com, MSM , lkml , catalin.marinas@arm.com, Will Deacon , valentin.schneider@arm.com, linux-arm-kernel@lists.infradead.org References: <2cc9dd44-0b4b-94a8-155a-7a2446a1b892@codeaurora.org> <1712842eb0767e51155a5396d282102c@kernel.org> From: Vladimir Murzin Message-ID: <9c504d04-8d20-91cb-6284-2891589eff37@arm.com> Date: Fri, 20 Nov 2020 10:14:50 +0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 11/20/20 9:54 AM, Marc Zyngier wrote: > On 2020-11-20 09:09, Vladimir Murzin wrote: >> On 11/20/20 8:56 AM, Marc Zyngier wrote: >>> On 2020-11-20 04:30, Neeraj Upadhyay wrote: >>>> Hi, >>>> >>>> For ARM cortex A76, A77, A78 cores (which as per TRM, support AMU) >>>> AA64PFR0[47:44] field is not set, and AMU does not get enabled for >>>> them. >>>> Can you please provide support for these CPUs in cpufeature.c? >>> >>> If that was the case, that'd be an erratum, and it would need to be >>> documented as such. It could also be that this is an optional feature >>> for these cores (though the TRM doesn't suggest that). >>> >>> Can someone at ARM confirm what is the expected behaviour of these CPUs? >> >> Not a confirmation, but IIRC, these are imp def features, while our cpufeatures >> catches architected one. > > Ah, good point. So these CPUs implement some sort of AMU, and not *the* AMU. > > Yet the register names are the same. Who thought that'd be a good idea? IMO, it is the case where imp def has been generalized into arch extension, so something have been moved over. Cheers Vladimir > >         M.