public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Babu Moger <babu.moger@oracle.com>
Cc: mingo@redhat.com, akpm@linux-foundation.org,
	keescook@chromium.org, dan.j.williams@intel.com,
	aryabinin@virtuozzo.com, tj@kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] Ajust lockdep static allocations
Date: Fri, 23 Sep 2016 17:04:39 +0200	[thread overview]
Message-ID: <20160923150439.GD5012@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <71daf047-059d-3478-9e08-989d44211a9c@oracle.com>

On Fri, Sep 23, 2016 at 09:50:52AM -0500, Babu Moger wrote:
> >Why can't you boot? You have that little memories? 4MB doesn't seem like
> >a worthwhile amount of memory.
> >
> >Also, you didn't say.  This seems a somewhat crucial point.
> 
>     Correct, We can't boot with lockdep. Sorry I did not make that clear.
> We have a limit on static size of the kernel.

This stuff should be in .bss not .data. It should not affect the static
size at all. Or am I misunderstanding things?

  reply	other threads:[~2016-09-23 15:04 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-22 18:43 [PATCH 0/2] Ajust lockdep static allocations Babu Moger
2016-09-22 18:43 ` [PATCH 1/2] lockdep: Keep the default static allocations small Babu Moger
2016-09-22 18:43 ` [PATCH 2/2] config: Add new CONFIG_PROVE_LOCKING_PLUS Babu Moger
2016-09-23  7:12 ` [PATCH 0/2] Ajust lockdep static allocations Peter Zijlstra
2016-09-23 14:04   ` Babu Moger
2016-09-23 14:34     ` Peter Zijlstra
2016-09-23 14:50       ` Babu Moger
2016-09-23 15:04         ` Peter Zijlstra [this message]
2016-09-23 15:15           ` Babu Moger
2016-09-23 15:40             ` Peter Zijlstra
2016-09-23 19:57               ` Babu Moger
2016-09-23 20:08                 ` Rob Gardner
2016-09-23 20:17                 ` Peter Zijlstra
2016-09-23 20:30                   ` Babu Moger

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=20160923150439.GD5012@twins.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=akpm@linux-foundation.org \
    --cc=aryabinin@virtuozzo.com \
    --cc=babu.moger@oracle.com \
    --cc=dan.j.williams@intel.com \
    --cc=keescook@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=tj@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox