From: Gerd Knorr <kraxel@bytesex.org>
To: xen-devel@lists.xensource.com
Subject: Re: PAE xen + linux kernel boots ...
Date: 27 Apr 2005 14:03:17 +0200 [thread overview]
Message-ID: <87ll74o29m.fsf@bytesex.org> (raw)
In-Reply-To: <20050425172624.GB22076@bytesex>
Gerd Knorr <kraxel@bytesex.org> writes:
> ... linux userspace doesn't come up yet though, thus it is still some
> way to go.
Well, now it does, boots up to a login prompt ;)
> Xen: http://dl.bytesex.org/patches/xen-4/pae-support
> Linux: http://dl.bytesex.org/patches/linux-xen-4/
New versions of the patches are in xen-5 + linux-xen-5, they are
against changeset 1.1385 (xen) 2.6.11 vanilla (linux-xen).
Currently open issues are:
* general: more testing, cleanups, drop debug code, review
all the FIXME's in the code ...
* interfaces: do_update_va_mapping() and do_mmu_update() use 32bit
values for page table entry updates, which will stop working as
soon as we'll attempt to use memory above 4GB (which isn't the
case yet).
* xen: quite a few places are not fixed yet to deal with physical
addresses above 4GB, i.e. are still 32 bit only.
* xen: writable pagetables need fixing, they use emulation at the
moment. I was very surprised that it did "just work", but that
was just the bug fixed by Keir recently causing the code do
emulation all the time ;-)
* xenlinux: Not sure how to deal best with the vsyscall page.
xenlinux places it just before the hypervisor area, which is a
different address in pae/non-pae mode. And there seems to be no
obvious way to make that depend on CONFIG_X86_PAE, the linker
script where the address is in is not processed by cpp ...
I think that's it for the moment. Comments are welcome.
Enjoy,
Gerd
--
#define printk(args...) fprintf(stderr, ## args)
next prev parent reply other threads:[~2005-04-27 12:03 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-25 17:26 PAE xen + linux kernel boots Gerd Knorr
2005-04-27 12:03 ` Gerd Knorr [this message]
2005-04-28 18:41 ` Chris Wright
2005-04-29 8:01 ` Gerd Knorr
2005-04-30 8:40 ` Scott Parish
2005-04-30 22:55 ` Gerd Knorr
2005-04-30 9:01 ` Scott Parish
2005-04-30 9:51 ` Scott Parish
2005-04-30 10:54 ` Keir Fraser
2005-05-01 8:12 ` Scott Parish
2005-05-02 14:03 ` Gerd Knorr
2005-05-02 16:02 ` Scott Parish
2005-05-04 2:20 ` Scott Parish
2005-05-04 8:03 ` Gerd Knorr
2005-05-04 15:20 ` Scott Parish
2005-05-04 2:28 ` Scott Parish
2005-05-04 3:22 ` Kip Macy
2005-05-04 3:23 ` Scott Parish
2005-05-04 7:58 ` Gerd Knorr
2005-04-30 23:15 ` Gerd Knorr
2005-04-30 23:01 ` Gerd Knorr
2005-04-30 22:57 ` Scott Parish
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=87ll74o29m.fsf@bytesex.org \
--to=kraxel@bytesex.org \
--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.