From: Harry Butterworth <harry@hebutterworth.freeserve.co.uk>
To: Jeremy Katz <katzj@redhat.com>
Cc: Rusty Russell <rusty@rustcorp.com.au>,
Xen Mailing List <xen-devel@lists.sourceforge.net>
Subject: Re: Proposal for init/kexec/hotplug format for Xen
Date: Mon, 28 Feb 2005 22:24:44 +0000 [thread overview]
Message-ID: <1109629484.6186.10.camel@localhost> (raw)
In-Reply-To: <1109622525.2899.14.camel@bree.local.net>
On Mon, 2005-02-28 at 15:28 -0500, Jeremy Katz wrote:
> I'd rather batch my complexity up to where it only has to be written
> once and not every time you port an OS. Keeping things simple for the
> guest (like this) seems reasonable to me.
I think you are going to have to write some OS specific code every time
you port an OS anyway. The question is where it ends up.
With the registry approach you have a clean protocol in domain 0 and the
guest OS specific code stays in each corresponding guest OS.
With the batching up the complexity approach I think there is a risk
that you end up with a bundle of guest OS specific code all coupled
together in the domain 0 code which seems less good to me.
--
Harry Butterworth <harry@hebutterworth.freeserve.co.uk>
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
next prev parent reply other threads:[~2005-02-28 22:24 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-26 20:57 Proposal for init/kexec/hotplug format for Xen Rusty Russell
2005-02-27 10:53 ` Keir Fraser
2005-02-27 11:46 ` Rusty Russell
2005-02-27 15:25 ` Anthony Liguori
2005-02-27 15:48 ` Keir Fraser
2005-02-27 15:54 ` Anthony Liguori
2005-02-27 16:09 ` Keir Fraser
2005-02-27 16:16 ` Anthony Liguori
2005-02-27 16:31 ` Harry Butterworth
2005-02-27 16:42 ` Anthony Liguori
2005-02-27 17:32 ` Keir Fraser
2005-02-27 17:59 ` Anthony Liguori
2005-02-27 18:12 ` Harry Butterworth
2005-02-27 18:24 ` Anthony Liguori
2005-02-27 18:55 ` Harry Butterworth
2005-02-27 18:57 ` Keir Fraser
2005-02-27 19:10 ` Anthony Liguori
2005-02-27 21:49 ` Keir Fraser
2005-02-27 22:39 ` Anthony Liguori
2005-02-27 23:29 ` Harry Butterworth
2005-02-28 8:59 ` Keir Fraser
2005-02-27 19:38 ` Harry Butterworth
2005-02-27 16:05 ` Harry Butterworth
2005-02-28 12:06 ` Rusty Russell
2005-02-28 15:46 ` Anthony Liguori
2005-02-28 20:28 ` Jeremy Katz
2005-02-28 22:24 ` Harry Butterworth [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-02-28 13:08 Re: " harry
2005-02-28 13:32 ` Rusty Russell
2005-02-28 13:40 ` Harry Butterworth
2005-02-28 14:33 ` Keir Fraser
2005-02-28 16:46 ` Re: " Rusty Russell
2005-03-01 13:15 ` Harry Butterworth
2005-03-01 15:08 ` Keir Fraser
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=1109629484.6186.10.camel@localhost \
--to=harry@hebutterworth.freeserve.co.uk \
--cc=katzj@redhat.com \
--cc=rusty@rustcorp.com.au \
--cc=xen-devel@lists.sourceforge.net \
/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.