From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Steven Maresca <steve@zentific.com>
Cc: Mina Jafari <ai.minajafari@gmail.com>, xen-devel@lists.xensource.com
Subject: Re: How dom0 send notifications to domu with best performance
Date: Mon, 12 Aug 2013 09:27:44 -0400 [thread overview]
Message-ID: <20130812132744.GD3318@phenom.dumpdata.com> (raw)
In-Reply-To: <CANSvah79x_fRPHLLGwf7XqM18uz1oPWWxaHCDU3RPaPyBG0QOQ@mail.gmail.com>
On Sun, Aug 11, 2013 at 10:12:08AM -0400, Steven Maresca wrote:
> Mina,
>
> Recommended checking out libvchan. Example code is not in tools/libvchan --
> see also qubes os.
.. which you can use to create a memory region that is seen by both guests
and you can create a semaphore on it. It even has the tools to advertise
that one of the bytes will cause an event - so if one of the guests
writes to it - the other end is instantly notified.
>
> Steve
> On Aug 11, 2013 1:25 AM, "Mina Jafari" <ai.minajafari@gmail.com> wrote:
>
> > Hi,
> > How can dom0 send notifications to domu as some events happens(events are
> > not hardware related). I know it can be done using event channel or through
> > networking. Is there any other way? and which has the best
> > performance?Performance really matters for my purpose.
> >
> > Thanks
> >
> > _______________________________________________
> > Xen-devel mailing list
> > Xen-devel@lists.xen.org
> > http://lists.xen.org/xen-devel
> >
> >
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
prev parent reply other threads:[~2013-08-12 13:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-11 5:24 How dom0 send notifications to domu with best performance Mina Jafari
2013-08-11 14:12 ` Steven Maresca
2013-08-12 13:27 ` Konrad Rzeszutek Wilk [this message]
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=20130812132744.GD3318@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=ai.minajafari@gmail.com \
--cc=steve@zentific.com \
--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 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.