From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Cc: Samuel Thibault <samuel.thibault@ens-lyon.org>
Subject: Xen branches
Date: Thu, 17 Nov 2011 01:54:47 +0100 [thread overview]
Message-ID: <4EC45B57.80602@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 843 bytes --]
Hello, all. I have push some work for paravirtualised GRUB2 to XEN
branch: http://bzr.savannah.gnu.org/lh/grub/branches/xen. Currently only
x86-64 (I'm much less interested in i386). What works:
- modules, normal mode, console, date, all of the all-platform commands
(not all are tested though)
What doesn't (not implemented):
-network
-disks
-loaders
-most of platform-specific commands (well as expected, xen is a separate
platforms so its platform-specific commands will be different if any)
What's kludgy:
-Finding and checking xen headers (/usr/include hardcoded, no checking,
also it's so annoying that xen mixes its kernels intended for standalone
environment with standard userspace headers)
-Stack. Right now I just allocate space in .bss.
-Heap. Likewise.
--
Regards
Vladimir 'φ-coder/phcoder' Serbinenko
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 294 bytes --]
next reply other threads:[~2011-11-17 0:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-17 0:54 Vladimir 'φ-coder/phcoder' Serbinenko [this message]
2011-11-17 0:59 ` [Grub2] Xen branches Samuel Thibault
2011-11-17 0:59 ` Samuel Thibault
2011-11-17 1:49 ` Vladimir 'φ-coder/phcoder' Serbinenko
2011-11-17 1:49 ` Vladimir 'φ-coder/phcoder' Serbinenko
2011-11-17 9:07 ` Samuel Thibault
2011-11-17 9:07 ` Samuel Thibault
[not found] ` <m2n.s.1RR00M-272707@chiark.greenend.org.uk>
2011-11-24 16:55 ` [Xen-devel] " Ian Jackson
2011-11-24 16:55 ` Ian Jackson
-- strict thread matches above, loose matches on Subject: below --
2011-11-17 0:54 Vladimir 'φ-coder/phcoder' Serbinenko
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=4EC45B57.80602@gmail.com \
--to=phcoder@gmail.com \
--cc=grub-devel@gnu.org \
--cc=samuel.thibault@ens-lyon.org \
/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.