[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <m3my807ug3.fsf@pobox.com>
Date: Sun, 21 Jun 2009 23:39:56 -0500
From: Nathan Lynch <ntl@...ox.com>
To: Yinghai Lu <yinghai@...nel.org>
Cc: Christoph Lameter <cl@...ux-foundation.org>,
Andrew Morton <akpm@...ux-foundation.org>, mingo@...e.hu,
mel@....ul.ie, tglx@...utronix.de, hpa@...or.com,
suresh.b.siddha@...el.com, linux-kernel@...r.kernel.org,
viro@...iv.linux.org.uk, rusty@...tcorp.com.au, steiner@....com,
rientjes@...gle.com, containers@...ts.linux-foundation.org
Subject: Re: [PATCH] mm: clear N_HIGH_MEMORY map before se set it again -v4
Yinghai Lu <yinghai@...nel.org> writes:
> please check
>
> [PATCH] x86: only clear node_states for 64bit
>
> Nathan reported that
> | commit 73d60b7f747176dbdff826c4127d22e1fd3f9f74
> | Author: Yinghai Lu <yinghai@...nel.org>
> | Date: Tue Jun 16 15:33:00 2009 -0700
> |
> | page-allocator: clear N_HIGH_MEMORY map before we set it again
> |
> | SRAT tables may contains nodes of very small size. The arch code may
> | decide to not activate such a node. However, currently the early boot
> | code sets N_HIGH_MEMORY for such nodes. These nodes therefore seem to be
> | active although these nodes have no present pages.
> |
> | For 64bit N_HIGH_MEMORY == N_NORMAL_MEMORY, so that works for 64 bit too
>
> the cpuset.mems cgroup attribute on an i386 kvm guest
>
> try to fix it by only clear node_states[N_NORMAL_MEMORY] for 64bit only.
> and need to do save/restore for that in find_zone_movable_pfn
This works for my setup, thanks.
--
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