From mboxrd@z Thu Jan 1 00:00:00 1970 From: Samuel Thibault Subject: Re: [RFC] hvm-stub for ia64 Date: Thu, 22 Nov 2007 10:53:59 +0000 Message-ID: <20071122105359.GF4242@implementation.uk.xensource.com> References: <1195725624.47455338d0e37@imp.free.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Return-path: Content-Disposition: inline In-Reply-To: <1195725624.47455338d0e37@imp.free.fr> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: tgingold@free.fr Cc: Xen-devel , Xen-ia64-devel List-Id: xen-devel@lists.xenproject.org tgingold@free.fr, le Thu 22 Nov 2007 11:00:24 +0100, a =E9crit : > Quoting Keir Fraser : >=20 > > On 22/11/07 09:31, "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 w= ay (on > > ia64) if this is checked in? > Yes, I don't plan to remove the old way on ia64. I have not implemente= d > 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