From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Mark Williamson <mark.williamson@cl.cam.ac.uk>
Cc: tim.post@netkinetics.net, xen-devel@lists.xensource.com,
"Daniel P. Berrange" <berrange@redhat.com>,
Ian Campbell <Ian.Campbell@xensource.com>
Subject: Re: 2.6.20.3 to be the next kernel?
Date: Mon, 04 Jun 2007 21:50:08 -0700 [thread overview]
Message-ID: <4664EB80.2080509@goop.org> (raw)
In-Reply-To: <200706050324.26723.mark.williamson@cl.cam.ac.uk>
Mark Williamson wrote:
> I was wondering how you handle PAE in pv-ops. Presumably you just toggle
> based on what the kernel was built for? It seems like PV-ops ought in
> principle to be able to make the kernel bimodal. I'm guessing the
> appropriate response to my question is probably a simple "patches
> welcome" ;-)
Indeed.
Actually, its something I gave some thought to, but unfortunately it
isn't that simple. The main problem is that the types of
pte_t/pmd_t/pgd_t change from 32 to 64 bit, and all the pmd folding
stuff is still done at compile-time.
I was also thinking about always using the PAE forms of the structures,
and actually do the conversion just as we read/write the entries. But
even then, the various pagetable accessors/traversal functions know how
large the entries are and how many levels the pagetables have, etc.
The only slightly workable approach I thought of was to maintain a
sort-of in-kernel shadow pagetable scheme, which maintains parallel PAE
and non-PAE pagetables. But that's hardly elegant, and poses all sorts
of its own problems (like propagating the hardware-set access/modified
bits properly, for example).
So, its all a bit of an open question.
J
next prev parent reply other threads:[~2007-06-05 4:50 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-04 12:44 2.6.20.3 to be the next kernel? Tim Post
2007-06-04 18:01 ` Mark Williamson
2007-06-04 18:10 ` Daniel P. Berrange
2007-06-04 18:31 ` Mark Williamson
2007-06-04 18:13 ` Nate Carlson
2007-06-04 18:17 ` Daniel P. Berrange
2007-06-04 18:33 ` Mark Williamson
2007-06-04 19:04 ` Jeremy Fitzhardinge
2007-06-04 19:58 ` Mark Williamson
2007-06-04 20:00 ` Daniel P. Berrange
2007-06-04 20:16 ` Jeremy Fitzhardinge
2007-06-04 20:15 ` Jeremy Fitzhardinge
2007-06-05 2:24 ` Mark Williamson
2007-06-05 4:50 ` Jeremy Fitzhardinge [this message]
2007-06-05 4:57 ` Jeremy Fitzhardinge
2007-06-05 15:57 ` Mark Williamson
2007-06-05 3:49 ` Tim Post
2007-06-05 4:53 ` Jeremy Fitzhardinge
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=4664EB80.2080509@goop.org \
--to=jeremy@goop.org \
--cc=Ian.Campbell@xensource.com \
--cc=berrange@redhat.com \
--cc=mark.williamson@cl.cam.ac.uk \
--cc=tim.post@netkinetics.net \
--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.