[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <534D3D4E.9080408@redhat.com>
Date: Tue, 15 Apr 2014 10:08:14 -0400
From: Prarit Bhargava <prarit@...hat.com>
To: Andi Kleen <andi@...stfloor.org>
CC: Andrew Morton <akpm@...ux-foundation.org>,
linux-kernel@...r.kernel.org,
Richard Weinberger <richard.weinberger@...il.com>,
Josh Boyer <jwboyer@...oraproject.org>,
Rob Landley <rob@...dley.net>,
Steven Rostedt <rostedt@...dmis.org>,
Ingo Molnar <mingo@...nel.org>,
Peter Zijlstra <peterz@...radead.org>,
Frederic Weisbecker <fweisbec@...il.com>,
linux-doc@...r.kernel.org
Subject: Re: [PATCH] Add initcall_blacklist kernel parameter [v4]
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
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists