From: Jim Pick <jim@kaffe.org>
To: Adam Heath <doogie@debian.org>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
"kaffe@kaffe.org" <kaffe@kaffe.org>
Subject: Re: [kaffe] Re: java control of xen
Date: Mon, 04 Apr 2005 10:00:50 -0700 [thread overview]
Message-ID: <425172C2.2040208@kaffe.org> (raw)
In-Reply-To: <Pine.LNX.4.58.0504041121510.1953@gradall.private.brainfood.com>
Adam Heath wrote:
> On Fri, 1 Apr 2005, Jacob Gorm Hansen wrote:
>
>
>>Adam Heath wrote:
>>
>>>In an effort to push xen into more parts of the computing world, I am
>>>announcing the start of a brand new project here at Brainfood.
>>>
>>>Our plans are to port Xen to run *inside* a JVM(Kaffe), so that we can make
>>>use of the write-one-run-anywhere mantra. The magic piece of code that will
>>>enable this is Mips2Java.
>>>
>>>Unfortunately, at this time, Xen does not yet run on mips. So, we are looking
>>>for volunteers to port Xen to mips, so that then we can have Xen run under
>>>Kaffe, which will then let us run it on the final platform, mobile phones.
>>
>>I am all for that, I also think you guys should consider porting the
>>Jython Java/Python runtime to run inside Xen, so that in the longer term
>>we will be able take advantage of the Twisted libraries in Xen, for
>>instance I imagine the scheduler could be rewritten on top of Twisted's
>>excellent async programming framework. This would also make room for
>>more use of SOAP and XML, so that security policies for sHype could be
>>fetched on-demand from a centralized web-service. Talk about an agile,
>>service-oriented VMM!
>
>
> Hahaha, some people are easy.
>
> Please take a look at the date this mail was sent.
:-)
Cheers,
- Jim
prev parent reply other threads:[~2005-04-04 17:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-01 23:30 java control of xen Adam Heath
2005-04-01 23:56 ` Jim Pick
2005-04-02 0:21 ` Jacob Gorm Hansen
2005-04-02 0:26 ` Adam Heath
2005-04-04 16:22 ` [kaffe] " Adam Heath
2005-04-04 17:00 ` Jim Pick [this message]
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=425172C2.2040208@kaffe.org \
--to=jim@kaffe.org \
--cc=doogie@debian.org \
--cc=kaffe@kaffe.org \
--cc=xen-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.