From: Rich Persaud <rich.p@xensource.com>
To: "Ronald G. Minnich" <rminnich@lanl.gov>
Cc: maru <marudubshinki@gmail.com>, xen-devel@lists.sourceforge.net
Subject: Re: Re: ports
Date: Mon, 07 Mar 2005 06:36:09 -0500 [thread overview]
Message-ID: <422C3CA9.3080001@xensource.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0503070859570.3728@enigma.lanl.gov>
Ronald G. Minnich wrote:
>On Sun, 6 Mar 2005, maru wrote:
>
>
>
>>(and seriously, who uses Plan 9? yeah, It's got some very cool
>>features, but was it worth porting?)
>>
>>
>
>This type of question, appearing on a research list, still amazes me.
>
>Yes, the port was worth the effort.
>
>ron
>
>
This is what happens when you don't separate xen-users from
xen-developers.
Having said that, when I was compiling the index of virtualization
papers, I could not find papers on the nuances of Xen porting.
Perhaps this is not a common research topic in virtualization because
other para-virtualization efforts have not attracted as many ports as
Xen. An index of Xen porting resources could help future ports. In the
absence of papers, are there known mailing list threads or other notes
that could be compiled into an index? E.g. a comparison of the Plan 9
and NetBSD ports.
Rich
-------------------------------------------------------
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-03-07 11:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20050307032130.C195512043@sc8-sf-spam2.sourceforge.net>
2005-03-07 3:28 ` ports maru
2005-03-07 6:13 ` ports Kip Macy
2005-03-07 14:16 ` Dave Feustel
2005-03-07 16:00 ` Ronald G. Minnich
2005-03-07 11:36 ` Rich Persaud [this message]
2005-03-07 16:37 ` Ronald G. Minnich
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=422C3CA9.3080001@xensource.com \
--to=rich.p@xensource.com \
--cc=marudubshinki@gmail.com \
--cc=rminnich@lanl.gov \
--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.