public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: rcu_init allocation failure trace on bootup
Date: Mon, 6 May 2013 17:56:29 -0400	[thread overview]
Message-ID: <20130506215629.GA20273@redhat.com> (raw)
In-Reply-To: <20130506210249.GJ3501@linux.vnet.ibm.com>

On Mon, May 06, 2013 at 02:02:49PM -0700, Paul E. McKenney wrote:

 > >  > You are quite right, I am getting ahead of myself.  Please see below
 > >  > for the patch.
 > > 
 > > Doesn't fix it for me.
 > > 
 > > Is it this one instead perhaps ?
 > > 
 > >   89 #ifndef CONFIG_RCU_NOCB_CPU_NONE
 > >   90         if (!have_rcu_nocb_mask) {
 > >   91                 alloc_bootmem_cpumask_var(&rcu_nocb_mask);
 > >   92                 have_rcu_nocb_mask = true;
 > >   93         }
 > 
 > Hmmm...  That was in fact the one that the patch was intended to change.
 > Just out of curiosity, where did the patch apply instead?

I think this might be my screwup. I did it by hand, and misapplied it
to the top of rcu_nocb_setup() instead.

	Dave




      reply	other threads:[~2013-05-06 21:56 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-06 17:56 rcu_init allocation failure trace on bootup Dave Jones
2013-05-06 19:05 ` Paul E. McKenney
2013-05-06 19:26   ` Dave Jones
2013-05-06 19:43     ` Paul E. McKenney
2013-05-06 20:09       ` Yinghai Lu
2013-05-06 21:09         ` Paul E. McKenney
2013-05-06 20:24       ` Dave Jones
2013-05-06 21:02         ` Paul E. McKenney
2013-05-06 21:56           ` Dave Jones [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=20130506215629.GA20273@redhat.com \
    --to=davej@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paulmck@linux.vnet.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox