From: Ingo Molnar <mingo@elte.hu>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Venkatesh Pallipadi <venkatesh.pallipadi@intel.com>,
arjan@linux.intel.com, tglx@linutronix.de, hpa@zytor.com,
andi@firstfloor.org, linux-kernel@vger.kernel.org,
Suresh Siddha <suresh.b.siddha@intel.com>,
Nick Piggin <nickpiggin@yahoo.com.au>,
Christoph Lameter <cl@linux-foundation.org>
Subject: Re: [patch 1/2] x86: track memtype for RAM in page struct
Date: Sun, 14 Sep 2008 16:22:13 +0200 [thread overview]
Message-ID: <20080914142213.GA28162@elte.hu> (raw)
In-Reply-To: <48CD1D1E.1050906@goop.org>
* Jeremy Fitzhardinge <jeremy@goop.org> wrote:
> > it should be defined in include/asm-x86/page.h though, not in
> > page-flags.h - other architectures are using this flag for other
> > purposes.
>
> No, other shared-use flags are all defined in page-flags.h:
>
> enum pageflags {
> [...]
> __NR_PAGEFLAGS,
>
> /* Filesystems */
> PG_checked = PG_owner_priv_1,
>
> /* XEN */
> PG_pinned = PG_owner_priv_1,
> PG_savepinned = PG_dirty,
>
> /* SLOB */
> PG_slob_page = PG_active,
> PG_slob_free = PG_private,
>
> /* SLUB */
> PG_slub_frozen = PG_active,
> PG_slub_debug = PG_error,
> };
>
>
> We could #ifdef CONFIG_X86 just to make it clear we're talking about a
> specific X86 usage. But page-flags.h does seem to have become the
> central authority on all struct page flags usage.
well, in case of the PG_arch_* flags, they are all defined in
architecture files:
./include/asm-parisc/pgtable.h:#define PG_dcache_dirty PG_arch_1
./include/asm-mips/cacheflush.h:#define PG_dcache_dirty PG_arch_1
./arch/sparc64/mm/init.c:#define PG_dcache_dirty PG_arch_1
./arch/sh/include/cpu-sh4/cpu/cacheflush.h:#define PG_mapped PG_arch_1
./arch/sh/include/cpu-sh3/cpu/cacheflush.h:#define PG_mapped PG_arch_1
./arch/arm/include/asm/cacheflush.h:#define PG_dcache_dirty PG_arch_1
they are explicitly reserved for per architecture details.
Ingo
next prev parent reply other threads:[~2008-09-14 14:22 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-13 0:00 [patch 0/2] PAT fix/optimization Venkatesh Pallipadi
2008-09-13 0:00 ` [patch 1/2] x86: track memtype for RAM in page struct Venkatesh Pallipadi
2008-09-13 17:03 ` Jeremy Fitzhardinge
2008-09-14 13:29 ` Ingo Molnar
2008-09-14 14:18 ` Jeremy Fitzhardinge
2008-09-14 14:22 ` Ingo Molnar [this message]
2008-09-23 21:46 ` Venki Pallipadi
2008-09-23 21:59 ` Christoph Lameter
2008-09-24 15:53 ` [patch 1/2] x86: track memtype for RAM in page struct - v3 Venki Pallipadi
2008-09-27 17:59 ` Ingo Molnar
2008-09-30 7:28 ` Nick Piggin
2008-09-30 11:21 ` Ingo Molnar
2008-09-30 21:14 ` Suresh Siddha
2008-10-01 9:29 ` Ingo Molnar
2008-10-02 2:27 ` Nick Piggin
2008-09-13 17:24 ` [patch 1/2] x86: track memtype for RAM in page struct Frans Pop
2008-09-14 14:12 ` Ingo Molnar
2008-09-23 21:48 ` Pallipadi, Venkatesh
2008-09-13 0:00 ` [patch 2/2] x86: Handle error returns in set_memory_* Venkatesh Pallipadi
2008-09-14 13:27 ` Ingo Molnar
2008-09-14 14:35 ` Frans Pop
2008-09-14 14:10 ` Ingo Molnar
2008-09-30 8:36 ` Frans Pop
2008-09-30 21:29 ` Suresh Siddha
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=20080914142213.GA28162@elte.hu \
--to=mingo@elte.hu \
--cc=andi@firstfloor.org \
--cc=arjan@linux.intel.com \
--cc=cl@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nickpiggin@yahoo.com.au \
--cc=suresh.b.siddha@intel.com \
--cc=tglx@linutronix.de \
--cc=venkatesh.pallipadi@intel.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.