[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080905114551.GB27878@elte.hu>
Date: Fri, 5 Sep 2008 13:45:51 +0200
From: Ingo Molnar <mingo@...e.hu>
To: Yinghai Lu <yhlu.kernel@...il.com>
Cc: David Witbrodt <dawitbro@...global.net>,
Jordan Crouse <jordan.crouse@....com>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Ivan Kokshaysky <ink@...assic.park.msu.ru>,
Thomas Gleixner <tglx@...utronix.de>,
"H. Peter Anvin" <hpa@...or.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Jesse Barnes <jbarnes@...tuousgeek.org>,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] x86: split e820 reserved entries record to late v4 -
fix v7
* Yinghai Lu <yhlu.kernel@...il.com> wrote:
> On Thu, Sep 4, 2008 at 12:04 PM, Ingo Molnar <mingo@...e.hu> wrote:
> >
> >> v7: remove wrong removing of write_unlock(&resource_lock) in adjust_resource()
> >
> > i've applied the generic commit below to tip/core/resources, and merged
> > tip/core/resources into tip/x86/core, and added the remaining e820.c
> > oneliner change (attached below as well).
> >
>
> wonder if need to put
>
> x86: split e820 reserved entries record to late v4
> IO resources: add reserve_region_with_split()
> x86: split e820 reserved entries record to late, v7
>
> into 2.6.27 for fix hang on David's system.
too late i think. It hung on v2.6.26 too, right? So v2.6.28 would be
more appropriate, and linux-next or tip/msater can be used as a
practical kernel in the meanwhile.
Ingo
--
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