From: Samuel Thibault <samuel.thibault@eu.citrix.com>
To: tgingold@free.fr
Cc: Xen-devel <xen-devel@lists.xensource.com>,
Xen-ia64-devel <xen-ia64-devel@lists.xensource.com>
Subject: Re: [RFC] hvm-stub for ia64
Date: Thu, 22 Nov 2007 10:53:59 +0000 [thread overview]
Message-ID: <20071122105359.GF4242@implementation.uk.xensource.com> (raw)
In-Reply-To: <1195725624.47455338d0e37@imp.free.fr>
tgingold@free.fr, le Thu 22 Nov 2007 11:00:24 +0100, a écrit :
> Quoting Keir Fraser <Keir.Fraser@cl.cam.ac.uk>:
>
> > On 22/11/07 09:31, "tgingold@free.fr" <tgingold@free.fr> wrote:
> >
> > Presumably the old HVM builder for ia64 becomes dead code though? So really
> > this is the 'new' hvm building path. Do you need to support the old way (on
> > ia64) if this is checked in?
> Yes, I don't plan to remove the old way on ia64. I have not implemented
> a VGA in the stub firmware and I don't plan to do it soon.
That's the main difference between your approach (reimplement a
firmware) and the approach being developped here at XenSource (embed
qemu in a tiny stubdomain). Your VMX work in Xen is most probably
something useful, but reimplementing the hardware emulation support of
qemu looks to me like duplicate work. I haven't ported my stubdomain to
ia64 yet, but that shouldn't be very hard now that it works for x86.
Samuel
next prev parent reply other threads:[~2007-11-22 10:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-22 3:59 [RFC] hvm-stub for ia64 tgingold
2007-11-22 8:41 ` 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 [this message]
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=20071122105359.GF4242@implementation.uk.xensource.com \
--to=samuel.thibault@eu.citrix.com \
--cc=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.