[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4B996335.7070907@gmail.com>
Date: Thu, 11 Mar 2010 22:40:05 +0100
From: Jiri Slaby <jirislaby@...il.com>
To: Yinghai Lu <yinghai@...nel.org>
CC: Andrew Morton <akpm@...ux-foundation.org>,
Johannes Weiner <hannes@...xchg.org>,
Greg Thelen <gthelen@...gle.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Ingo Molnar <mingo@...e.hu>, "H. Peter Anvin" <hpa@...or.com>,
Thomas Gleixner <tglx@...utronix.de>, cl@...ux-foundation.com
Subject: Re: mmotm boot panic bootmem-avoid-dma32-zone-by-default.patch
On 03/11/2010 09:12 PM, Yinghai Lu wrote:
> On 03/11/2010 02:54 AM, Jiri Slaby wrote:
>> Hi, yes, it is 2.6.27.
>
> SLES 11?
Sorry I wrote that in haste. It is SLES 10 in the end. That means it is
2.6.16, not 2.6.27. Hence no sparsemem whatsoever. With SLES11 it should
be OK, we are using flatmem only for i386.
Whatever, it should be no issue now, as flatmem currently (as of 2.6.25)
depends on i386.
On the other hand I still considered the patch as applicable to
contemporary kernels since there might be weird bios e820 maps and huge
(and sparse) bootmem allocations/reservations (memory cgroups, initrd)
so that code requiring much memory below 4g (swiotlb) will fail then.
Whatever, in the current kernel, the particular issue I was referring to
*is not reproducible*.
thanks,
--
js
--
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