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 Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id B585AC5475B for ; Mon, 11 Mar 2024 21:07:25 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender:Content-Type: Content-Transfer-Encoding:List-Subscribe:List-Help:List-Post:List-Archive: List-Unsubscribe:List-Id:MIME-Version:References:Message-ID:In-Reply-To: Subject:cc:To:From:Date:Reply-To:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=X0NVHbOK4zY4gwC6NL7IqhwgoTS+bFSvuLtYzDsAEnM=; b=AkBUxKrvLnHL6uDYnwrkgs1aJb zHlYjA7tYk91G4FBtstLOm//xgaA9oNUarrNdgVv7wiSuCUxC6Op26omv2q3+jvFGHY0AXemvyxc6 4m6nLGjgXyAu0Yvzqa7UELLnhmIckL/esaaqKgIUTE5oelNNh+oMPxWQGzUUL0tmdxkw7/DMq9QdK ETj4a7jdDf3m1N4vk0kEpZFDslQSBjdEdYKd0lE+WuQsvJ2Ts0nYYzhdLI3k5Vi71Z5R6ZRWbbtq5 ZcAHkkX2A+kLVb0o1Kg2pv2KO3tNb+e93kZHpW8X4XmVrUKfDdBmEX09xB7zpioMgKEleybCFRgMh PvHZ3+pw==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.97.1 #2 (Red Hat Linux)) id 1rjmrY-00000003CDl-48EZ; Mon, 11 Mar 2024 21:07:12 +0000 Received: from gentwo.org ([2a02:4780:10:3cd9::1]) by bombadil.infradead.org with esmtps (Exim 4.97.1 #2 (Red Hat Linux)) id 1rjmrV-00000003CC9-0Vrq for linux-arm-kernel@lists.infradead.org; Mon, 11 Mar 2024 21:07:11 +0000 Received: by gentwo.org (Postfix, from userid 1003) id 84FD440940; Mon, 11 Mar 2024 14:07:04 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by gentwo.org (Postfix) with ESMTP id 83FD84093E; Mon, 11 Mar 2024 14:07:04 -0700 (PDT) Date: Mon, 11 Mar 2024 14:07:04 -0700 (PDT) From: "Christoph Lameter (Ampere)" To: Catalin Marinas cc: Marek Szyprowski , Mark Rutland , "linux-pm@vger.kernel.org" , "Rafael J. Wysocki" , Viresh Kumar , Will Deacon , Jonathan.Cameron@huawei.com, Matteo.Carlini@arm.com, Valentin.Schneider@arm.com, akpm@linux-foundation.org, anshuman.khandual@arm.com, Eric Mackay , dave.kleikamp@oracle.com, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, linux-mm@kvack.org, linux@armlinux.org.uk, robin.murphy@arm.com, vanshikonda@os.amperecomputing.com, yang@os.amperecomputing.com, Nishanth Menon , Stephen Boyd Subject: Re: [PATCH v3] ARM64: Dynamically allocate cpumasks and increase supported CPUs to 512 In-Reply-To: Message-ID: <9352f410-9dad-ac89-181a-b3cfc86176b8@linux.com> References: <37099a57-b655-3b3a-56d0-5f7fbd49d7db@gentwo.org> MIME-Version: 1.0 X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20240311_140709_208074_03E9EBB1 X-CRM114-Status: GOOD ( 18.76 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Mon, 11 Mar 2024, Catalin Marinas wrote: >> This patch landed in today's linux-next as commit 0499a78369ad ("ARM64: >> Dynamically allocate cpumasks and increase supported CPUs to 512"). >> Unfortunately it triggers the following warning during boot on most of >> my ARM64-based test boards. Here is an example from Odroid-N2 board: > > I spent a big part of this afternoon going through the code paths but > there's nothing obvious that triggered this problem. My suspicion is > some memory corruption, algorithmically I can't see anything that could > go wrong with CPUMASK_OFFSTACK. Unfortunately I could not reproduce it > yet to be able to add some debug info. > > So I decided to revert this patch. If we get to the bottom of it during > the merging window, I can still revive it. Otherwise we'll add it to > linux-next post -rc1. I also looked through the opp source and I cannot find even anything that even uses the functionality changed by the OFFSTACK option. This could be an issue in the ARM64 arch code itself where there maybe an assumption elsewhere that a cpumask can always store up to NR_CPU cpus and not only nr_cpu_ids as OFFSTACK does. How can I exercise the opp driver in order to recreate the problem? I assume the opp driver is ARM specific? x86 defaults to OFFSTACK so if there is an issue with OFFSTACK in opp then it should fail with kernel default configuration on that platform. _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel