public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Luis R. Rodriguez" <mcgrof@suse.com>
To: Davidlohr Bueso <davidlohr@hp.com>
Cc: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>,
	hpa@linux.intel.com, akpm@linux-foundation.org,
	linux-kernel@vger.kernel.org, Michal Hocko <mhocko@suse.cz>,
	Petr Mladek <pmladek@suse.cz>, Joe Perches <joe@perches.com>,
	Arun KS <arunks.linux@gmail.com>,
	Kees Cook <keescook@chromium.org>,
	Chris Metcalf <cmetcalf@tilera.com>
Subject: Re: [PATCH v3] printk: allow increasing the ring buffer depending on the number of CPUs
Date: Sat, 14 Jun 2014 20:48:07 +0200	[thread overview]
Message-ID: <20140614184807.GE4841@wotan.suse.de> (raw)
In-Reply-To: <1402695712.27369.10.camel@buesod1.americas.hpqcorp.net>

It turns out we can't use num_possible_cpus() that early on boot, as
it hasn't yet been properly set, nor other helpers, a late setup for
big CPUs is therefore needed in order to use num_possible_cpus().
That also means we can use kzalloc() instead. I'll send a v4 and
I think we should test this a bit so will send as RFT.

  Luis

      parent reply	other threads:[~2014-06-14 18:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-13 18:28 [PATCH v3] printk: allow increasing the ring buffer depending on the number of CPUs Luis R. Rodriguez
2014-06-13 20:36 ` Davidlohr Bueso
2014-06-13 20:44   ` Luis R. Rodriguez
2014-06-13 21:28     ` Davidlohr Bueso
2014-06-13 21:41 ` Davidlohr Bueso
2014-06-13 22:05   ` Luis R. Rodriguez
2014-06-14  1:09     ` Luis R. Rodriguez
2014-06-14 18:48   ` Luis R. Rodriguez [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=20140614184807.GE4841@wotan.suse.de \
    --to=mcgrof@suse.com \
    --cc=akpm@linux-foundation.org \
    --cc=arunks.linux@gmail.com \
    --cc=cmetcalf@tilera.com \
    --cc=davidlohr@hp.com \
    --cc=hpa@linux.intel.com \
    --cc=joe@perches.com \
    --cc=keescook@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mcgrof@do-not-panic.com \
    --cc=mhocko@suse.cz \
    --cc=pmladek@suse.cz \
    /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