public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Prarit Bhargava <prarit@redhat.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org,
	Richard Weinberger <richard.weinberger@gmail.com>,
	Josh Boyer <jwboyer@fedoraproject.org>,
	Rob Landley <rob@landley.net>,
	Steven Rostedt <rostedt@goodmis.org>,
	Ingo Molnar <mingo@kernel.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Frederic Weisbecker <fweisbec@gmail.com>,
	linux-doc@vger.kernel.org
Subject: Re: [PATCH] Add initcall_blacklist kernel parameter [v4]
Date: Tue, 15 Apr 2014 10:08:14 -0400	[thread overview]
Message-ID: <534D3D4E.9080408@redhat.com> (raw)
In-Reply-To: <20140414224042.GG22728@two.firstfloor.org>



On 04/14/2014 06:40 PM, Andi Kleen wrote:
>> Let's not leak all those blacklist entries when we're finished?
> 
> It's difficult, because you cannot free bootmem after bootmem is
> finished.
> 
> For the rare debug case some leaking should be acceptable.
> 

Andrew, FWIW I agree with Andi on this.  It is a minor leak in a debug
situation.  I'd also like to know in a kdump situation what was specified as
blacklisted so keeping this memory around is IMO a good idea.

P.

> -Andi
> 

  reply	other threads:[~2014-04-15 14:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-01 15:19 [PATCH] Add initcall_blacklist kernel parameter [v4] Prarit Bhargava
2014-04-14 21:29 ` Andrew Morton
2014-04-14 22:40   ` Andi Kleen
2014-04-15 14:08     ` Prarit Bhargava [this message]
2014-04-15 15:15   ` [PATCH] Add initcall_blacklist kernel parameter [v5] Prarit Bhargava
2014-04-15 20:04     ` Andrew Morton

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=534D3D4E.9080408@redhat.com \
    --to=prarit@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=andi@firstfloor.org \
    --cc=fweisbec@gmail.com \
    --cc=jwboyer@fedoraproject.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=peterz@infradead.org \
    --cc=richard.weinberger@gmail.com \
    --cc=rob@landley.net \
    --cc=rostedt@goodmis.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