From: Samuel Thibault <samuel.thibault@ens-lyon.org>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>,
"The development of GRUB 2" <grub-devel@gnu.org>
Subject: Re: [Xen-devel] Xen branches
Date: Thu, 24 Nov 2011 18:32:09 +0100 [thread overview]
Message-ID: <20111124173209.GA4188@type> (raw)
In-Reply-To: <20174.30403.935317.872549@mariner.uk.xensource.com>
Ian Jackson, le Thu 24 Nov 2011 16:54:27 +0000, a écrit :
> Vladimir 'φ-coder/phcoder' Serbinenko writes ("[Xen-devel] Xen branches"):
> > 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.
>
> This is exciting. We've been wanting a pv grub2 for some time. Do
> you think this work will be upstreamable into grub2 master ?
(Just for the record: Vladimir *is* upstream :) I just added the Cc to
Xen-devel to the grub-devel thread)
Samuel
prev parent reply other threads:[~2011-11-24 17:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m2n.s.1RQqJL-149396@chiark.greenend.org.uk>
2011-11-24 16:54 ` [Xen-devel] Xen branches Ian Jackson
2011-11-24 17:32 ` Samuel Thibault [this message]
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=20111124173209.GA4188@type \
--to=samuel.thibault@ens-lyon.org \
--cc=Ian.Jackson@eu.citrix.com \
--cc=grub-devel@gnu.org \
--cc=phcoder@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).