From: Wei LIU <liuw@liuw.name>
To: xen-devel@lists.xensource.com
Subject: When does domain builder allocate/bound DomU's XenStore port?
Date: Tue, 2 Mar 2010 15:45:18 +0800 [thread overview]
Message-ID: <d6a64191003012345o5d29440cw297b2b78d49e5764@mail.gmail.com> (raw)
Hi, Xen experts
As I discover in Mini-OS, the XenStore port is allocated by Dom0's
domain builder. All that a DomU has to do is binding that port in
shared_info page to its handler, and everything works. So I'm quite
interested in how the domain builder in Dom0 allocates a XenStore port
for DomU.
In the book The Definitive Guide to The Xen Hypervisor, it says that
XenStore event channel is bound by domain builder at build time. I
looked around for related code, but the code base seems to be too
large - both userland and kernel space. I've tried looking at
"tools/python" as well as "tools/libxc", but I didn't get the point.
So, what's the procedure and, which piece of code should I pay
attention to?
Thanks in advanced!
P.S. we use Xen 3.3.0 stable code.
Wei Liu
2010-03-02
reply other threads:[~2010-03-02 7:45 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=d6a64191003012345o5d29440cw297b2b78d49e5764@mail.gmail.com \
--to=liuw@liuw.name \
--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).