Received: by 2002:a05:6a10:5bc5:0:0:0:0 with SMTP id os5csp358812pxb; Fri, 29 Oct 2021 11:09:53 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxwfug2jziq940/HWbRQ+4qhZdXV8N+PADnWR7mGG12LtRVbgNEDzXDVHs4ZbtWpqmlSPa+ X-Received: by 2002:a17:906:6ad0:: with SMTP id q16mr15462771ejs.552.1635530993484; Fri, 29 Oct 2021 11:09:53 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1635530993; cv=none; d=google.com; s=arc-20160816; b=AF3rBX4qJA34ufK3FjOaGZuP90aShjK0wpo99pJOxD2l4VbUTeIH+xnkq/1fIA0gGv f8jB4u2vjkjrL4DNlK+ThOwSeua7PdSPT8hC+PCOzOai3k4c2aCK/F5opUczdIqw3E9p 2r8WBFnyX2MV+vcXX6O3b2myzJ9IuBcaWVq7z8tp5ikaLTNr58go2gZQZb/h3K+upEYT zPAY2Z64RvOz+vyJ3tPPrMeXgSr5wIHtMJPwejFEI33hy2mV2WP6pfD5svAB+BNmhVaU gaL63B+4uhpTC2P4Er882JvdsowF7squOERp1oeu53uxrslj5zVBQnay0BeUPP+by58x QuYw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date; bh=jnNY7vh/59zGTETT4P8ZRdwZ0K6r0MBq773GEr7D46g=; b=x4HceYLJv3ner/7Bljdicoulyx1ullG9llp08iWYwCBoeJfsdwA9lj6JY3tOA0SQWV E/1dwuG6H4Z7jzVD0ZV+FcTGm9NT//mGWwNYzJpzjhYXNDlalcHVxUpHEqyFJZ9PQXCR RVYvu2mR8lPf7C/NHMMhCNTGC9jyXr+SBnEwAOklK832ScX/RHoxXXd8HnUyGrJUH5uE fPiJPCVYUFQU0oTYipA15tNvWlvD/Dr15RDQ+G/ESQ9RXKijZmvPvoAxqs0wFKCiY8/W eabpna4WC5VVvyQOVglC7gEq8qcx+XK0nQKRFuOiV0I1jsJm9DXaUR6CVXd2MlnjKxW3 qDgg== 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 hs3si11817090ejc.712.2021.10.29.11.09.29; Fri, 29 Oct 2021 11:09:53 -0700 (PDT) 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 S230077AbhJ2SI6 (ORCPT + 99 others); Fri, 29 Oct 2021 14:08:58 -0400 Received: from mail.kernel.org ([198.145.29.99]:35642 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229826AbhJ2SI5 (ORCPT ); Fri, 29 Oct 2021 14:08:57 -0400 Received: by mail.kernel.org (Postfix) with ESMTPSA id 1518860FC3; Fri, 29 Oct 2021 18:06:26 +0000 (UTC) Date: Fri, 29 Oct 2021 19:06:23 +0100 From: Catalin Marinas To: Suzuki K Poulose Cc: Arnd Bergmann , Will Deacon , Mathieu Poirier , Anshuman Khandual , Arnd Bergmann , Marc Zyngier , Mark Rutland , David Brazdil , linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] [RFC] arm64: export this_cpu_has_cap Message-ID: References: <20211029113023.760421-1-arnd@kernel.org> <9d4e09b4-47dc-ed3c-2b6d-e0d1a081e592@arm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <9d4e09b4-47dc-ed3c-2b6d-e0d1a081e592@arm.com> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Oct 29, 2021 at 02:31:23PM +0100, Suzuki K Poulose wrote: > On 29/10/2021 12:30, Arnd Bergmann wrote: > > From: Arnd Bergmann > > > > It's now used in a coresight driver that can be a loadable module: > > > > ERROR: modpost: "this_cpu_has_cap" [drivers/hwtracing/coresight/coresight-trbe.ko] undefined! > > > > Fixes: 8a1065127d95 ("coresight: trbe: Add infrastructure for Errata handling") > > Reviewed-by: Suzuki K Poulose > Tested-by: Suzuki K Poulose > > Will, Catalin, Mathieu, > > Do you have a preference on how this fix can be pulled in ? This may > be safe to go via coresight tree if it is not too late. Otherwise, > it could go via the arm64 tree. I think Will already closed/tagged the arm64 tree for the upcoming merging window, though he could take it as a fix afterwards. If it doesn't conflict with the arm64 for-next/core, it's fine by me to go through the coresight tree. > > Signed-off-by: Arnd Bergmann > > --- > > Not sure if we actually want this to be exported, this is my local > > workaround for the randconfig build bot. > > --- > > arch/arm64/kernel/cpufeature.c | 1 + > > 1 file changed, 1 insertion(+) > > > > diff --git a/arch/arm64/kernel/cpufeature.c b/arch/arm64/kernel/cpufeature.c > > index ecbdff795f5e..beccbcfa7391 100644 > > --- a/arch/arm64/kernel/cpufeature.c > > +++ b/arch/arm64/kernel/cpufeature.c > > @@ -2864,6 +2864,7 @@ bool this_cpu_has_cap(unsigned int n) > > return false; > > } > > +EXPORT_SYMBOL(this_cpu_has_cap); EXPORT_SYMBOL_GPL? I think this_cpu_has_cap() is a bit more more specialised than cpus_have_const_cap(). With that: Acked-by: Catalin Marinas