All of lore.kernel.org
 help / color / mirror / Atom feed
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 22:20:44 +0000	[thread overview]
Message-ID: <20071122222044.GC4264@implementation> (raw)
In-Reply-To: <1195736687.47457e6fba715@imp.free.fr>

Hi,

tgingold@free.fr, le Thu 22 Nov 2007 14:04:47 +0100, a écrit :
> Quoting Samuel Thibault <samuel.thibault@eu.citrix.com>:
> > tgingold@free.fr, le Thu 22 Nov 2007 12:12:31 +0100, a écrit :
> > > Quoting Samuel Thibault <samuel.thibault@eu.citrix.com>:
> > > Of course it doesn't reimplement the emulation.  The current biggest
> > emulation
> > > is the IDE and I have copied ide.c from qemu and made almost no
> > modification.
> >
> > That's still forking.  And you'll also need to do it for vga,
> > network, ...
> 
> To be fair, I'd need to know better how stubdomain is implemented.

It's actually "just" a matter of compiling qemu against newlib, mini-os
and lwIP and make that run as a kernel in its own domain. That way it's
just the same code as the usual dm approach and mini-os, with some
#ifdefs.

Samuel

  reply	other threads:[~2007-11-22 22:20 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
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 [this message]
2007-11-23  3:30                   ` 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=20071122222044.GC4264@implementation \
    --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.