From: Gerd Knorr <kraxel@bytesex.org>
To: Karen White <kawhite@us.ibm.com>
Cc: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>,
keir.fraser@cl.cam.ac.uk, xen-devel@lists.xensource.com,
Nuutti Kotivuori <naked@iki.fi>
Subject: Re: PAE support revisited - questions
Date: 30 Mar 2005 12:20:51 +0200 [thread overview]
Message-ID: <87acolbfjw.fsf@bytesex.org> (raw)
In-Reply-To: <1112142537.21025.60.camel@kwdevel.austin.ibm.com>
Karen White <kawhite@us.ibm.com> writes:
> > Thats my intention. Maybe build some CONFIG_PAGING_LEVELS_2/3/4 from
> > this and i386 vs. x86_64 to make the #ifdefs in the code a bit more
> > readable.
>
> I submitted a CONFIG_PAE patch, but Keir says PAE support will be
> determined at boot time, not compile time.
I think that was just because it was just the config option without it
being actually used anywhere.
> > I'd create include/asm-x86/x86_32/page-2l.h and page-3l.h and let
> > page.h include the correct one depending on CONFIG_X86_PAE (and also
> > have the common stuff there).
>
> Are you working on this? I have modeled a page.h after x86_32/page.h
> but for level-3 page tables. Not finished with it.
I have a old patch for that, it will not apply any more due to the
page table macro cleanups though. Once the page table macro stuff is
finished I want to look at this again.
Gerd
--
#define printk(args...) fprintf(stderr, ## args)
next prev parent reply other threads:[~2005-03-30 10:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-22 8:00 PAE support revisited Ian Pratt
2005-03-22 9:49 ` Jacob Gorm Hansen
2005-03-22 14:51 ` Ronald G. Minnich
2005-03-22 18:22 ` [patch] " Gerd Knorr
2005-03-22 23:21 ` Karen White
2005-03-23 23:23 ` PAE: config and file layout Karen White
[not found] ` <87oed2bpv5.fsf@bytesex.org>
2005-03-30 0:28 ` PAE support revisited - questions Karen White
2005-03-30 10:20 ` Gerd Knorr [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-03-30 7:30 Ian Pratt
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=87acolbfjw.fsf@bytesex.org \
--to=kraxel@bytesex.org \
--cc=kawhite@us.ibm.com \
--cc=keir.fraser@cl.cam.ac.uk \
--cc=m+Ian.Pratt@cl.cam.ac.uk \
--cc=naked@iki.fi \
--cc=xen-devel@lists.xensource.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.