From: Qian Cai <cai@lca.pw>
To: Will Deacon <will@kernel.org>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
Dan Williams <dan.j.williams@intel.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: page_alloc.shuffle=1 + CONFIG_PROVE_LOCKING=y = arm64 hang
Date: Fri, 23 Aug 2019 07:52:13 -0400 [thread overview]
Message-ID: <1566561133.5576.12.camel@lca.pw> (raw)
In-Reply-To: <20190823113715.n3lc73vtc4ea2ln4@willie-the-truck>
On Fri, 2019-08-23 at 12:37 +0100, Will Deacon wrote:
> On Thu, Aug 22, 2019 at 05:33:23PM -0400, Qian Cai wrote:
> > https://raw.githubusercontent.com/cailca/linux-mm/master/arm64.config
> >
> > Booting an arm64 ThunderX2 server with page_alloc.shuffle=1 [1] +
> > CONFIG_PROVE_LOCKING=y results in hanging.
>
> Hmm, but the config you link to above has:
>
> # CONFIG_PROVE_LOCKING is not set
>
> so I'm confused. Also, which tree is this?
I manually turn on CONFIG_PROVE_LOCKING=y on the top of that, and reproduce on
both the mainline and linux-next trees.
WARNING: multiple messages have this Message-ID (diff)
From: Qian Cai <cai@lca.pw>
To: Will Deacon <will@kernel.org>
Cc: Peter Zijlstra <peterz@infradead.org>,
Catalin Marinas <catalin.marinas@arm.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Dan Williams <dan.j.williams@intel.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: page_alloc.shuffle=1 + CONFIG_PROVE_LOCKING=y = arm64 hang
Date: Fri, 23 Aug 2019 07:52:13 -0400 [thread overview]
Message-ID: <1566561133.5576.12.camel@lca.pw> (raw)
In-Reply-To: <20190823113715.n3lc73vtc4ea2ln4@willie-the-truck>
On Fri, 2019-08-23 at 12:37 +0100, Will Deacon wrote:
> On Thu, Aug 22, 2019 at 05:33:23PM -0400, Qian Cai wrote:
> > https://raw.githubusercontent.com/cailca/linux-mm/master/arm64.config
> >
> > Booting an arm64 ThunderX2 server with page_alloc.shuffle=1 [1] +
> > CONFIG_PROVE_LOCKING=y results in hanging.
>
> Hmm, but the config you link to above has:
>
> # CONFIG_PROVE_LOCKING is not set
>
> so I'm confused. Also, which tree is this?
I manually turn on CONFIG_PROVE_LOCKING=y on the top of that, and reproduce on
both the mainline and linux-next trees.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-08-23 11:52 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-22 21:33 page_alloc.shuffle=1 + CONFIG_PROVE_LOCKING=y = arm64 hang Qian Cai
2019-08-22 21:33 ` Qian Cai
2019-08-22 21:33 ` Qian Cai
2019-08-23 11:37 ` Will Deacon
2019-08-23 11:37 ` Will Deacon
2019-08-23 11:52 ` Qian Cai [this message]
2019-08-23 11:52 ` Qian Cai
2019-08-23 11:52 ` Qian Cai
2019-09-05 21:08 ` Qian Cai
2019-09-05 21:08 ` Qian Cai
2019-09-05 21:08 ` Qian Cai
2019-09-10 15:22 ` Qian Cai
2019-09-10 15:22 ` Qian Cai
2019-09-10 15:22 ` Qian Cai
2019-09-10 19:49 ` Qian Cai
2019-09-10 19:49 ` Qian Cai
2019-09-10 19:49 ` Qian Cai
2019-09-12 2:28 ` CONFIG_SHUFFLE_PAGE_ALLOCATOR=y lockdep splat (WAS Re: page_alloc.shuffle=1 + CONFIG_PROVE_LOCKING=y = arm64 hang) Qian Cai
2019-09-12 2:28 ` Qian Cai
2019-09-10 20:35 ` page_alloc.shuffle=1 + CONFIG_PROVE_LOCKING=y = arm64 hang Qian Cai
2019-09-10 20:35 ` Qian Cai
2019-09-10 20:35 ` Qian Cai
2019-09-11 1:10 ` Sergey Senozhatsky
2019-09-11 1:10 ` Sergey Senozhatsky
2019-09-12 12:05 ` Qian Cai
2019-09-12 12:05 ` Qian Cai
2019-09-12 12:05 ` Qian Cai
2019-09-16 14:42 ` Steven Rostedt
2019-09-16 14:42 ` Steven Rostedt
2019-09-17 0:53 ` Sergey Senozhatsky
2019-09-17 0:53 ` Sergey Senozhatsky
2019-09-18 14:39 ` printk() + memory offline deadlock (WAS Re: page_alloc.shuffle=1 + CONFIG_PROVE_LOCKING=y = arm64 hang) Qian Cai
2019-09-18 14:39 ` Qian Cai
2019-09-18 14:39 ` Qian Cai
2019-09-18 15:50 ` Sergey Senozhatsky
2019-09-18 15:50 ` Sergey Senozhatsky
2019-09-18 15:58 ` Sergey Senozhatsky
2019-09-18 15:58 ` Sergey Senozhatsky
2019-09-18 16:10 ` Qian Cai
2019-09-18 16:10 ` Qian Cai
2019-09-18 16:10 ` Qian Cai
2019-09-23 10:21 ` Sergey Senozhatsky
2019-09-23 10:21 ` Sergey Senozhatsky
2019-09-23 12:58 ` Petr Mladek
2019-09-23 12:58 ` Petr Mladek
2019-09-23 13:24 ` Qian Cai
2019-09-23 13:24 ` Qian Cai
2019-09-23 13:24 ` Qian Cai
2019-09-24 1:28 ` Sergey Senozhatsky
2019-09-24 1:28 ` Sergey Senozhatsky
2019-09-23 13:09 ` Qian Cai
2019-09-23 13:09 ` Qian Cai
2019-09-23 13:09 ` Qian Cai
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=1566561133.5576.12.camel@lca.pw \
--to=cai@lca.pw \
--cc=catalin.marinas@arm.com \
--cc=dan.j.williams@intel.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=peterz@infradead.org \
--cc=will@kernel.org \
/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.