From: Thomas Schauss <schauss@tum.de>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Peter Zijlstra <peterz@infradead.org>,
John Kacur <jkacur@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
RT <linux-rt-users@vger.kernel.org>
Subject: Re: 3.2-rc1 and nvidia drivers
Date: Wed, 30 Nov 2011 16:07:29 +0100 [thread overview]
Message-ID: <4ED646B1.4020508@tum.de> (raw)
In-Reply-To: <1322663502.17003.121.camel@frodo>
On 11/30/2011 03:31 PM, Steven Rostedt wrote:
> Thomas (Schauss),
>
> Can you try this patch. It has both patches that Peter pointed to
> applied.
>
> Thanks,
>
> -- Steve
>
> diff --git a/mm/slab.c b/mm/slab.c
> index 096bf0a..86a8dec 100644
> --- a/mm/slab.c
> +++ b/mm/slab.c
> @@ -764,6 +764,7 @@ static enum {
> PARTIAL_AC,
> PARTIAL_L3,
> EARLY,
> + LATE,
> FULL
> } g_cpucache_up;
>
> @@ -795,7 +796,7 @@ static void init_node_lock_keys(int q)
> {
> struct cache_sizes *s = malloc_sizes;
>
> - if (g_cpucache_up != FULL)
> + if (g_cpucache_up< LATE)
> return;
>
> for (s = malloc_sizes; s->cs_size != ULONG_MAX; s++) {
> @@ -1744,6 +1745,11 @@ void __init kmem_cache_init_late(void)
> {
> struct kmem_cache *cachep;
>
> + g_cpucache_up = LATE;
> +
> + /* Annotate slab for lockdep -- annotate the malloc caches */
> + init_lock_keys();
> +
> /* 6) resize the head arrays to their final sizes */
> mutex_lock(&cache_chain_mutex);
> list_for_each_entry(cachep,&cache_chain, next)
> @@ -1754,9 +1760,6 @@ void __init kmem_cache_init_late(void)
> /* Done! */
> g_cpucache_up = FULL;
>
> - /* Annotate slab for lockdep -- annotate the malloc caches */
> - init_lock_keys();
> -
> /*
> * Register a cpu startup notifier callback that initializes
> * cpu_cache_get for all new cpus
Hello,
I will test this but can only do so on Friday.
On 3.0.9-rt25 (which I have been using here) patch 30765b92 is already
applied. And it is also present in patch-3.0.10-rt27.patch.
So the original patch from Peter
(http://article.gmane.org/gmane.linux.kernel.mm/70863/match=) applies
cleanly here.
Regards,
Thomas
next prev parent reply other threads:[~2011-11-30 15:07 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-16 9:10 3.2-rc1 and nvidia drivers Javier Sanz
2011-11-16 9:40 ` Thomas Schauss
2011-11-16 15:06 ` Thomas Gleixner
2011-11-28 10:08 ` Thomas Schauss
2011-11-28 11:31 ` John Kacur
2011-11-29 14:31 ` John Kacur
2011-11-30 2:36 ` Steven Rostedt
2011-11-30 8:23 ` John Kacur
2011-11-30 11:14 ` Peter Zijlstra
2011-11-30 14:14 ` Steven Rostedt
2011-11-30 14:16 ` Peter Zijlstra
2011-11-30 14:28 ` Steven Rostedt
2011-11-30 14:31 ` Steven Rostedt
2011-11-30 14:34 ` Peter Zijlstra
2011-11-30 15:07 ` Thomas Schauss [this message]
2011-11-30 15:20 ` Steven Rostedt
2011-12-02 17:41 ` Thomas Schauss
2011-12-02 19:37 ` Steven Rostedt
2011-11-30 13:34 ` Steven Rostedt
2011-11-30 13:39 ` John Kacur
2011-11-30 13:49 ` Steven Rostedt
2011-11-30 13:53 ` John Kacur
2011-11-30 9:06 ` Thomas Schauss
2011-11-16 9:52 ` Mike Galbraith
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=4ED646B1.4020508@tum.de \
--to=schauss@tum.de \
--cc=jkacur@redhat.com \
--cc=linux-rt-users@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).