All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: Nauzad Sadry <nauzad@gmail.com>
Cc: xen-devel@lists.sourceforge.net
Subject: Re: What is domain creation flow-chart in XEND
Date: Sat, 15 Jan 2005 17:49:01 -0600	[thread overview]
Message-ID: <41E9ABED.8050102@codemonkey.ws> (raw)
In-Reply-To: <aa7b01ec05011515214481c5dc@mail.gmail.com>

I can answer some of this.  This is what I've been able to figure out.  
It could be wrong.

Nauzad Sadry wrote:

>Hello all
>
>I am a newbie in Python & have been trying to understand the set of
>operations performed by XEND in order to create a new domain. Can
>someone answer the following questions about domain creation
>
>1. The set of Hypercalls requests made by XEND to XEN thru the privcmd driver
>  
>
It's a two step process.  First the raw domain is created, then Linux 
(or something else) is loaded.  For the first part, it's actually quite 
simple.  Xend issues a DOM0_CREATEDOMAIN hypercall.  That will create an 
empty domain with a certain amount of CPUs and visible memory.

The next part is more complicated.  For Linux, it's all pretty much done 
in the xc_linux_build() function (tools/libxc/xc_linux_build.c).  This 
code is straight foreword.

>2. What event channels get created & what entities are involved in
>setting up the event channels.
>  
>
 From what I can tell, Linux always listens on event channel 1.  So, 
Xend just binds a local port to the domains port 1.  After binding, it 
maps a shared memory region and works on a ring queue passing back and 
forth control_msg_t structures.  This is how virtual devices are setup.

I imagine each device gets it's own channel but I do not know for sure.

>3. A control channel is supposed to exist between XEND & the domain.
>If XEND listens to one end of the channel, then what entity in the
>domain listens to the other end
>  
>
The domain's kernel I believe.

>If someone can point me to some document for more details I would appreciate it
>  
>
I posted some documentation to xc.h.  This is where most of this work is 
done.  I don't know of any documentation.  The bulk of all this is done 
in libxc, xu.c (this binding implements a bunch of functionality), and 
x2d2 (this isn't used by Xend but is a bit easier to understand than Xend).

Regards,

>Thanks
>
>Nauzad
>
>
>-------------------------------------------------------
>The SF.Net email is sponsored by: Beat the post-holiday blues
>Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
>It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
>_______________________________________________
>Xen-devel mailing list
>Xen-devel@lists.sourceforge.net
>https://lists.sourceforge.net/lists/listinfo/xen-devel
>
>  
>



-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt

  reply	other threads:[~2005-01-15 23:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-15 23:21 What is domain creation flow-chart in XEND Nauzad Sadry
2005-01-15 23:49 ` Anthony Liguori [this message]
2005-01-16  1:06   ` Mark Williamson
2005-01-17  4:07     ` Nauzad Sadry
2005-01-17  5:00       ` Anthony Liguori
2005-01-17  8:16         ` Andrew Warfield

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=41E9ABED.8050102@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=nauzad@gmail.com \
    --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.