From: Tejun Heo <teheo@novell.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: Jan Beulich <JBeulich@novell.com>, Ingo Molnar <mingo@elte.hu>,
linux-kernel@vger.kernel.org
Subject: Re: remap allocator for per-CPU memory
Date: Wed, 13 May 2009 20:29:20 +0900 [thread overview]
Message-ID: <4A0AAF10.3030709@novell.com> (raw)
In-Reply-To: <4A0AAB6B.3090903@novell.com>
Tejun Heo wrote:
> Andi Kleen wrote:
>> Tejun Heo <teheo@novell.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
next prev parent reply other threads:[~2009-05-13 11:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-12 15:30 remap allocator for per-CPU memory Jan Beulich
2009-05-12 15:43 ` Tejun Heo
2009-05-13 10:09 ` Tejun Heo
2009-05-13 11:05 ` Andi Kleen
2009-05-13 11:13 ` Tejun Heo
2009-05-13 11:29 ` Tejun Heo [this message]
2009-05-13 11:46 ` Andi Kleen
2009-05-13 12:51 ` Jan Beulich
[not found] ` <4A0ADE6A0200007800000BA7@novell.com>
2009-05-13 13:29 ` Tejun Heo
2009-05-13 13:44 ` Jan Beulich
2009-05-13 13:53 ` Tejun Heo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4A0AAF10.3030709@novell.com \
--to=teheo@novell.com \
--cc=JBeulich@novell.com \
--cc=andi@firstfloor.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox