From: tgingold@free.fr
To: Xen-ia64-devel <xen-ia64-devel@lists.xensource.com>,
Xen-devel <xen-devel@lists.xensource.com>
Subject: [RFC] hvm-stub for ia64
Date: Thu, 22 Nov 2007 04:59:43 +0100 [thread overview]
Message-ID: <20071122035943.GA2512@localhost.localdomain> (raw)
Hi,
this is my initial work on hvm-stub domains.
HVM-stub domains are a mix of PV and HVM: it requires VT extension but
look externally as a PV domain.
All the io emulation is done within the domain by a stub firmware. This
layer translates raw IO accesses to PV commands, ie it can run unmodified
linux without running qemu-dm.
Currently it works only for ia64 and can boot linux (serial console).
I cross-post to xen-devel because I can be of a general interest.
I'd plan to submit patches soon but here is a preview.
Part 1: tools/ - modification to start an hvmstub domain (small)
Part 2: xen/ - IO reflection (small)
Part 3: extra/stubfw - stub firmware (large)
Change to common files are rather small and this is a good news.
The stub firmware is more a proof of concept and need serious enhancement.
It is just minimal to be able to boot linux (ie serial console and one ide
disk).
I am not sure where should go stubfw, so if anyone has suggestions...
Comments are welcome,
Tristan.
next reply other threads:[~2007-11-22 3:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-22 3:59 tgingold [this message]
2007-11-22 8:41 ` [RFC] hvm-stub for ia64 Keir Fraser
2007-11-22 9:31 ` [Xen-devel] " tgingold
2007-11-22 9:45 ` Keir Fraser
2007-11-22 10:00 ` tgingold
2007-11-22 10:34 ` Keir Fraser
2007-11-22 10:53 ` Samuel Thibault
2007-11-22 11:12 ` tgingold
2007-11-22 11:20 ` Samuel Thibault
2007-11-22 13:04 ` [Xen-devel] " tgingold
2007-11-22 22:20 ` Samuel Thibault
2007-11-23 3:30 ` [Xen-devel] " Tristan Gingold
2007-11-23 10:08 ` Samuel Thibault
2007-11-27 17:16 ` Samuel Thibault
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=20071122035943.GA2512@localhost.localdomain \
--to=tgingold@free.fr \
--cc=xen-devel@lists.xensource.com \
--cc=xen-ia64-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.