[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAE9FiQWhR9SG1WyqCCxKS2PkJXKeO-wpxQsuUN8_evKWebpAiA@mail.gmail.com>
Date: Mon, 11 Mar 2013 13:28:03 -0700
From: Yinghai Lu <yinghai@...nel.org>
To: Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>
Cc: Thomas Gleixner <tglx@...utronix.de>, Ingo Molnar <mingo@...e.hu>,
"H. Peter Anvin" <hpa@...or.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Tejun Heo <tj@...nel.org>, Thomas Renninger <trenn@...e.de>,
Tang Chen <tangchen@...fujitsu.com>,
linux-kernel@...r.kernel.org, Pekka Enberg <penberg@...nel.org>,
Jacob Shin <jacob.shin@....com>
Subject: Re: [PATCH v2 19/20] x86, mm: Make init_mem_mapping be able to be
called several times
On Mon, Mar 11, 2013 at 6:16 AM, Konrad Rzeszutek Wilk
<konrad.wilk@...cle.com> wrote:
> On Sat, Mar 09, 2013 at 10:44:46PM -0800, Yinghai Lu wrote:
>> Prepare to put page table on local nodes.
>>
>> Move calling of init_mem_mapping to early_initmem_init.
>>
>> Rework alloc_low_pages to alloc page table in following order:
>> BRK, local node, low range
>>
>> Still only load_cr3 one time, otherwise we would break xen 64bit again.
>>
>
> We could also fix that. Now that the regression storm has passed
> and I am able to spend some time on it we could make it a bit more
> resistant.
Never mind, We should only need to call load_cr3 one time.
as init_memory_mapping itself flush tlb everytime on 64bit.
Thanks
Yinghai
--
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