From: Razvan Cojocaru <rzvncj@gmail.com>
To: xen-devel@lists.xen.org
Subject: Hypervisor <-> dom0 userspace event channel
Date: Thu, 15 Nov 2012 00:44:22 +0200 [thread overview]
Message-ID: <50A41EC6.7010106@gmail.com> (raw)
Hello,
if the goal is establishing an event channel between the Xen HV and a
custom dom0 userspace application,
1. for the hypervisor code, would you recommend using the EVTCHNOP_*
hypercalls from xen/include/public/event_channel.h directly, or the
friendlier xen/include/xen/event.h functions? And for the userspace
tool, I'd use the xenctrl.h xc_evtchn_*() functions, correct?
2. what would be the best way of exposing the hypervisor event channel
port received from alloc_unbound_xen_event_channel() to the dom0
userspace application? Put it somewhere in the shared info page? I'm
assuming the XenStore is out of the question for this purpose, and
otherwise overkill.
3. what is the best way (most efficient, and Xen-friendly way) of
exposing HV data such as event channel ports or shared page mfns/pfns to
a custom dom0 userspace application?
Thanks,
Razvan
reply other threads:[~2012-11-14 22:44 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=50A41EC6.7010106@gmail.com \
--to=rzvncj@gmail.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).