All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Lutomirski <luto@kernel.org>
To: Borislav Petkov <bp@alien8.de>, Michel Lespinasse <walken@google.com>
Cc: "H. Peter Anvin" <hpa@zytor.com>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: lockdep issue booting v4.1 upstream kernel with >64 x86_64 CPUs
Date: Tue, 30 Jun 2015 12:06:07 -0700	[thread overview]
Message-ID: <5592E89F.7010704@kernel.org> (raw)
In-Reply-To: <20150627104622.GC26543@pd.tnic>

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

      reply	other threads:[~2015-06-30 19:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-27  1:38 lockdep issue booting v4.1 upstream kernel with >64 x86_64 CPUs Michel Lespinasse
2015-06-27  8:56 ` Borislav Petkov
     [not found]   ` <CANN689GcAB1UzP_SfQBowaxvTDOo061DFn4NJxbq0z4rc1YhMQ@mail.gmail.com>
2015-06-27 10:46     ` Borislav Petkov
2015-06-30 19:06       ` Andy Lutomirski [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5592E89F.7010704@kernel.org \
    --to=luto@kernel.org \
    --cc=bp@alien8.de \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=walken@google.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.