xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Jiageng Yu <yujiageng734@gmail.com>
To: Steven Harp <steven.harp@adventiumlabs.org>
Cc: Samuel Thibault <samuel.thibault@ens-lyon.org>,
	xen-devel@lists.xensource.com,
	Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: Introduction to Linux based stubdom (GSoC 2011)
Date: Wed, 11 May 2011 00:19:05 +0800	[thread overview]
Message-ID: <BANLkTi=mNiZPoDzAOoJYgUA3nQiULGxpAQ@mail.gmail.com> (raw)
In-Reply-To: <4DC4271A.3090001@adventiumlabs.org>

On Sat, May 7, 2011 at 12:51 AM, Steven Harp
<steven.harp@adventiumlabs.org> wrote:
>
>
> On 05/05/2011 11:31 AM, Jiageng Yu wrote:
>>
>>
>>     Stubdoms are very small Xen PV guests used to run some software
>> components that otherwise live in dom0. We plan to implement a linux
>> based stubdom, which provides devices emulation to a particular HVM
>> guest. The major tasks of this project are described below.
>>
>>      1. We have to establish the environment of linux based stubdom
>> with minimal linux kernel and shared libraries, which could contain
>> the upstream qemu exactly. We also maintain a minimal upstream qemu by
>> cutting unnecessary objs in its configuration phase. The minimal linux
>> kernel, shared libraries and the upstream qemu are packed into the
>> ramdisk, which is the real body of stubdom we need.
>>
> ...
>>     This is a brief introduction to the project. Any suggestion or
>> question will be Thankful!
>>
>
> This is an excellent project.
>
> One suggestion regarding the minimal Linux is to make allowances
> in the build process for different kernel compilation options and
> supplemental files in the stubdom image.   Possibly worth thinking
> about different options for ramdisk, e.g. ramfs versus a compressed
> ext* filesystem. The former is lighter weight, but the latter
> offers more control, e.g. extended attributes.
>
> Best of luck,
>  Steve Harp
>
>
>
>

Hi Steven,

    Thanks very much for the advice. Honestly, until now, I have no
idea about the performance of Linux based stubdoms. So I try to make
it minimal first. Additionally, though a compressed ext* filesystem
could offer more control, stubdoms have little chance of accessing the
local filesystem in our current implementment plan.

    I will confirm with my mentor whether stubdoms need more
functional requirements. Thank you a lot.

    Regards!

Jiageng Yu.

  reply	other threads:[~2011-05-10 16:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20110505163119363@spamfilter-21.visi.com>
2011-05-06 16:51 ` Introduction to Linux based stubdom (GSoC 2011) Steven Harp
2011-05-10 16:19   ` Jiageng Yu [this message]
2011-05-05 15:45 于佳耕
2011-05-05 16:12 ` Samuel Thibault
2011-05-06  2:47   ` Jiageng Yu

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='BANLkTi=mNiZPoDzAOoJYgUA3nQiULGxpAQ@mail.gmail.com' \
    --to=yujiageng734@gmail.com \
    --cc=samuel.thibault@ens-lyon.org \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=steven.harp@adventiumlabs.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).