From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Nick Piggin <nickpiggin@yahoo.com.au>
Cc: Ingo Molnar <mingo@elte.hu>, Hugh Dickens <hugh@veritas.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: Definition of x86 _PAGE_SPECIAL and sharing _PAGE_UNUSED1
Date: Wed, 27 Aug 2008 12:02:08 -0700 [thread overview]
Message-ID: <48B5A4B0.9050308@goop.org> (raw)
_PAGE_SPECIAL is overloading _PAGE_UNUSED1. Does it really leave
_PAGE_UNUSED1 available for other uses, or does it become an exclusive
user of that flag. Under what circumstances can they be shared?
arch/x86/mm/pageattr-test.c is now using _PAGE_UNUSED1 as the flag used
to make sure that huge pages are shattered properly (previously it used
_PAGE_GLOBAL). Is that going to clash with _PAGE_SPECIAL?
In other words, should we drop _PAGE_UNUSED1 altogether, or at least
define how the its different users can coexist?
Am I right in supposing that _PAGE_SPECIAL can only be set on user pages?
(Also, "SPECIAL" is awfully generic. Was there really no more
descriptive name for this?)
J
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next reply other threads:[~2008-08-27 19:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-27 19:02 Jeremy Fitzhardinge [this message]
2008-08-28 0:32 ` Nick Piggin
2008-08-28 0:47 ` Jeremy Fitzhardinge
2008-08-28 1:00 ` Nick Piggin
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=48B5A4B0.9050308@goop.org \
--to=jeremy@goop.org \
--cc=akpm@linux-foundation.org \
--cc=hugh@veritas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@elte.hu \
--cc=nickpiggin@yahoo.com.au \
/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