[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4BECEBF4.7000402@oracle.com>
Date: Thu, 13 May 2010 23:21:40 -0700
From: Yinghai <yinghai.lu@...cle.com>
To: Benjamin Herrenschmidt <benh@...nel.crashing.org>
CC: Ingo Molnar <mingo@...e.hu>, Thomas Gleixner <tglx@...utronix.de>,
"H. Peter Anvin" <hpa@...or.com>,
Andrew Morton <akpm@...ux-foundation.org>,
David Miller <davem@...emloft.net>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Johannes Weiner <hannes@...xchg.org>,
linux-kernel@...r.kernel.org, linux-arch@...r.kernel.org
Subject: Re: [PATCH 03/35] lmb: Add ARCH_DISCARD_LMB to put lmb code to .init
On 05/13/2010 07:14 PM, Benjamin Herrenschmidt wrote:
> On Thu, 2010-05-13 at 17:19 -0700, Yinghai Lu wrote:
>> So those lmb bits could be released after kernel is booted up.
>>
>> Arch code could define ARCH_DISCARD_LMB in asm/lmb.h,
>> __init_lmb will become __init, __initdata_lmb will becom __initdata
>>
>> x86 code will use that.
>
> So you do not intend to use lmb after boot ? This will break the debugfs
> files unless you also remove those.
no, x86 don't lmb after boot.
yes
...
>> @@ -695,7 +695,7 @@ static int __init early_lmb(char *p)
>> }
>> early_param("lmb", early_lmb);
>>
>> -#ifdef CONFIG_DEBUG_FS
>> +#if defined(CONFIG_DEBUG_FS) && !defined(ARCH_DISCARD_LMB)
>>
>> static int lmb_debug_show(struct seq_file *m, void *private)
>> {
>
it will check ARCH_DISCARD_LMB
--
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