From: Keir Fraser <keir.fraser@eu.citrix.com>
To: "Xia, Liangfu" <liangfu.xia@intel.com>,
Atsushi SAKAI <sakaia@jp.fujitsu.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: Question about "Hosted Xen" Status
Date: Mon, 02 Mar 2009 08:57:17 +0000 [thread overview]
Message-ID: <C5D14FED.3DC0%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <E88DD564E9DC5446A76B2B47C3BCCA154A8E47EA@pdsmsx503.ccr.corp.intel.com>
There's stuff scattered around about certain aspects: in the wiki, and in
the docs directory of the xen repo, for example. But nothing comprehensive
and diligently kept up to date, no.
-- Keir
On 02/03/2009 08:44, "Xia, Liangfu" <liangfu.xia@intel.com> wrote:
> Actually I think currently there is no good document about Xen's design. Am I
> right?
> If wrong, can anybody tell me?
>
> Thanks
>
> -----Original Message-----
> From: xen-devel-bounces@lists.xensource.com
> [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Keir Fraser
> Sent: 2009年3月2日 16:42
> To: Atsushi SAKAI; xen-devel@lists.xensource.com
> Subject: Re: [Xen-devel] Question about "Hosted Xen" Status
>
> On 02/03/2009 02:10, "Atsushi SAKAI" <sakaia@jp.fujitsu.com> wrote:
>
>> I have a question about "Hosted Xen".
>> I saw it on Ian's presentation document.
>> But It does not contain enough information.
>>
>> 1)The code is available?
>> 2)Would you show me the document URL about "Hosted Xen"?
>
> Short answer is that it's not ready for release yet and there's no document
> describing it.
>
> -- Keir
>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
prev parent reply other threads:[~2009-03-02 8:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-02 2:10 Question about "Hosted Xen" Status Atsushi SAKAI
2009-03-02 8:42 ` Keir Fraser
2009-03-02 8:44 ` Xia, Liangfu
2009-03-02 8:57 ` Keir Fraser [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=C5D14FED.3DC0%keir.fraser@eu.citrix.com \
--to=keir.fraser@eu.citrix.com \
--cc=liangfu.xia@intel.com \
--cc=sakaia@jp.fujitsu.com \
--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.