From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: tim.post@netkinetics.net,
"Daniel P. Berrange" <berrange@redhat.com>,
xen-devel@lists.xensource.com,
Mark Williamson <mark.williamson@cl.cam.ac.uk>,
Ian Campbell <Ian.Campbell@xensource.com>
Subject: Re: 2.6.20.3 to be the next kernel?
Date: Mon, 04 Jun 2007 21:57:51 -0700 [thread overview]
Message-ID: <4664ED4F.2050006@goop.org> (raw)
In-Reply-To: <4664EB80.2080509@goop.org>
Jeremy Fitzhardinge wrote:
> So, its all a bit of an open question.
>
Oh, I meant to say, the UNSW/Gelato folks have been proposing a more
abstracted pagetable interface which should hide all the architectural
details of the pagetable from the core kernel. That's probably the
right way to go to make PAE/non-PAE runtime switchable (their actual
goal is to make efficient use of the myriad ia64 pagetable modes, which
makes PAE rather trivial by comparison). But I don't know what the
state of those patches is - I don't think they've been posted in a while.
J
next prev parent reply other threads:[~2007-06-05 4:57 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
2007-06-05 4:57 ` Jeremy Fitzhardinge [this message]
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=4664ED4F.2050006@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.