All of lore.kernel.org
 help / color / mirror / Atom feed
From: Derrik Pates <dpates@dsdk12.net>
To: Chotu Ram <chotwo@hotmail.com>
Cc: xen-devel@lists.sourceforge.net
Subject: Re: Xen newbie: inter-domain communication
Date: Fri, 07 Jan 2005 21:59:27 -0500	[thread overview]
Message-ID: <41DF4C8F.8020107@dsdk12.net> (raw)
In-Reply-To: <BAY13-F37EED4250F8FC77CD853BC7940@phx.gbl>

Chotu Ram wrote:
> 1. As far as I can understand (and I might be wrong) Xen maintains two 
> domains dom0 (control domain) and dom1 (the other guest OSes). When the 
> documentation says inter-domain communication, is it only referring to 
> the communication between the dom0 and dom1, or it can also be applied 
> to the communication among the guest OSes (unprivileged that is).

A "domain" is a single virtual execution space, more or less. Each 
"virtual machine" is a separate domain. (When you do "xm list", the "Id" 
field is the "domain ID".) So yes, an inter-domain commmunication 
channel can exist between domain 0 and any other domain (running virtual 
machine).

> 2. What are the capabilities of the inter-domain communication method. 
> Specifically: what protocol is used to communicate?, what kind of 
> information can be communicated? Can this communication be used for 
> logging/auditing? Does anybody has any experience using this method or 
> has any working example?

As I understand, the "protocol" is basically just a per-channel 
"interrupt" (to get the other side's attention as needed), and a shared 
page, which is exchanged between the two domains as needed (only one can 
be interacting with it at a time, I think). The virtual block device 
driver and virtual network interface driver, as I understand it, 
structure it as a big ring buffer, and encode messages (and assign pages 
of their allocated memory to the other side of the channel for a 
DMA-like exchange method) in that ring buffer. Look at the developer 
documentation for a better explanation.

-- 
Derrik Pates
dpates@dsdk12.net


-------------------------------------------------------
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-08  2:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-07 10:42 Xen newbie: inter-domain communication Chotu Ram
2005-01-08  2:59 ` Derrik Pates [this message]
2005-01-08  3:25 ` Mark Williamson
2005-01-08  3:52   ` Kip Macy
2005-01-08  3:56     ` Mark Williamson
2005-01-08  4:07       ` Kip Macy

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=41DF4C8F.8020107@dsdk12.net \
    --to=dpates@dsdk12.net \
    --cc=chotwo@hotmail.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.