xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Larry White <lmw@satx.rr.com>
Cc: xen-devel@lists.xen.org
Subject: Re: XenStore as a data transfer path?
Date: Wed, 25 Jul 2012 14:44:29 -0400	[thread overview]
Message-ID: <20120725184429.GC16360@phenom.dumpdata.com> (raw)
In-Reply-To: <C96058547A5A42DDB1A89B2F8880BCE2@LarryE6400>

On Sat, Jul 21, 2012 at 12:59:31PM -0500, Larry White wrote:
> Hi Konrad,
> 
> >On Tue, Jul 17, 2012 at 11:22:28PM -0500, LarryWhite wrote:
> >I am new to Xen and want to provide simple communication between my DomU
> >and
> >Dom0 environments.  I just need to be able to pass a few bytes of
> >information back and forth between DomU and Dom0 while using some form of
> >event management to know when an update occurs so I can act on it.  At
> >first, it appeared that using XenBus and XenStore might be the right
> >solution for this.  However, after looking over the documentation, it seems
> >that XenBus and XenStore should only be used in a PVM Xen configuration,
> >not
> >a HVM model like mine.  Is this true?  
> 
> >>It can be done in HVM.
> 
> >What would be the best way to accomplish this?  Is there any sample code
> >which demonstrates this for a HVM Xen environment?
> 
> >>libvchan is your best bet.
> 
> Have been looking at libvchan as you suggested.  An additional bit of
> information that I left out on my original post was that I would like to do
> this in a "one to many" environment.  In other words, I want to support data
> transfer from dom0 to a number of different domU's.  Would an approach such
> as libvchan allow for this or would I need a separate process in dom0 for
> each of the different domU channels?  I was really hoping to have a single
> process running in dom0 to manage this. 

You would need seperate rings for each domU. Whether you want to implement this
in a single process or multi-thread the process - or just use one process and
block on the event (signal) to receive an interrupt when data appears - that is up
to you.

> 
> Thanks,
> Larry
> 
> 

  parent reply	other threads:[~2012-07-25 18:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-21  0:58 XenStore as a data transfer path? Larry White
2012-07-21  1:43 ` James Harper
2012-07-21  1:58   ` Larry White
2012-07-21 12:01     ` James Harper
2012-07-21 15:04       ` Larry White
2012-07-21 17:59       ` Larry White
2012-07-25 10:10         ` George Dunlap
2012-07-25 18:44         ` Konrad Rzeszutek Wilk [this message]
2012-07-21 18:02       ` DomU to Dom0 Communication in Xen HVM? Larry White

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=20120725184429.GC16360@phenom.dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=lmw@satx.rr.com \
    --cc=xen-devel@lists.xen.org \
    /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).