From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752873AbbF3TGO (ORCPT ); Tue, 30 Jun 2015 15:06:14 -0400 Received: from mail.kernel.org ([198.145.29.136]:46800 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752080AbbF3TGK (ORCPT ); Tue, 30 Jun 2015 15:06:10 -0400 Message-ID: <5592E89F.7010704@kernel.org> Date: Tue, 30 Jun 2015 12:06:07 -0700 From: Andy Lutomirski User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: Borislav Petkov , Michel Lespinasse CC: "H. Peter Anvin" , LKML Subject: Re: lockdep issue booting v4.1 upstream kernel with >64 x86_64 CPUs References: <20150627085631.GA27131@pd.tnic> <20150627104622.GC26543@pd.tnic> In-Reply-To: <20150627104622.GC26543@pd.tnic> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 06/27/2015 03:46 AM, Borislav Petkov wrote: > On Sat, Jun 27, 2015 at 03:32:40AM -0700, Michel Lespinasse wrote: >> Yes, tried this successfully both with <64 and >64 CPUs, this does get >> rid of the lockdep warning for me. > > Thanks, I'll add your Tested-by to the patch. > Just for kicks, can one of you big NUMA owners try running the sigreturn tests (tools/testing/selftests/x86/sigreturn_{32,64}) on one of these monsters with that patch applied, preferably on every cpu? Something like: for i in `seq 1 64`; do (taskset -c $i ./sigreturn_32 && taskset -c $i ./sigreturn_64) >/dev/null || echo FAIL; done I don't see why it would fail, but if the percpu conversion was botched, then these tests are likely to blow up. --Andy