[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4A0AAF10.3030709@novell.com>
Date: Wed, 13 May 2009 20:29:20 +0900
From: Tejun Heo <teheo@...ell.com>
To: Andi Kleen <andi@...stfloor.org>
Cc: Jan Beulich <JBeulich@...ell.com>, Ingo Molnar <mingo@...e.hu>,
linux-kernel@...r.kernel.org
Subject: Re: remap allocator for per-CPU memory
Tejun Heo wrote:
> Andi Kleen wrote:
>> Tejun Heo <teheo@...ell.com> writes:
>>> Okay, just glanced over the pageattr code. I don't think we need any
>>> special provisions for this as long as the TLB is fine with having
>>> overlapping PMD and PTE mappings with different attributes (please
>>> note that these two mappings aren't occupying the same linear
>>> addresses - they're aliases). This is allowed, right?
>> Nope.
>
> Yeah, I'm going through the manual now and can't find anything which
> allows such behavior. I haven't been able to find anything which
> describes what happens between large page and 4k page aliases.
> Aieee... I'll dig through the manual a bit more and see whether this
> can be worked around somehow. :-(
Looks like we're screwed.
I couldn't find anything explicitly prohibiting PMD/PTE aliases w/
different attributes although there are plenty of warnings and don'ts
against giving different attributes to the same linear addresses. At
any rate, it definitely looks way too dangerous to depend on.
And, set_memory_*() is basically allowed on any memory allocated via
get_free_page(), so... we're between rock and hard place. Looks like
remapping partially using large pages is no go.
Any ideas?
Thanks.
--
tejun
--
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