[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87r5hni19y.fsf@basil.nowhere.org>
Date: Wed, 25 Aug 2010 09:45:13 +0200
From: Andi Kleen <andi@...stfloor.org>
To: Haicheng Li <haicheng.li@...ux.intel.com>
Cc: "H. Peter Anvin" <hpa@...or.com>, Ingo Molnar <mingo@...hat.com>,
Thomas Gleixner <tglx@...utronix.de>,
"akpm\@linux-foundation.org" <akpm@...ux-foundation.org>,
"ak\@linux.intel.com" <ak@...ux.intel.com>,
Wu Fengguang <fengguang.wu@...el.com>,
"linux-kernel\@vger.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-mm\@kvack.org" <linux-mm@...ck.org>
Subject: Re: [BUGFIX][PATCH 1/2] x86, mem: separate x86_64 vmalloc_sync_all() into separate functions
Haicheng Li <haicheng.li@...ux.intel.com> writes:
> hello,
>
> Resend these two patches for bug fixing:
>
> The bug is that when memory hotplug-adding happens for a large enough area that a new PGD entry is
> needed for the direct mapping, the PGDs of other processes would not get updated. This leads to some
> CPUs oopsing when they have to access the unmapped areas, e.g. onlining CPUs on the new added node.
The patches look good to me. Can we please move forward with this?
Reviewed-by: Andi Kleen <ak@...ux.intel.com>
-Andi
--
ak@...ux.intel.com -- Speaking for myself only.
--
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