From: Steven Maresca <steve@zentific.com>
To: Razvan Cojocaru <rzvncj@gmail.com>
Cc: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: Hypervisor to dom0 communication
Date: Thu, 15 Nov 2012 09:26:56 -0500 [thread overview]
Message-ID: <CANSvah4437FvmZe-uvcrZOvC2NJ7hZUE8y9DUFUd29BWPHRc6g@mail.gmail.com> (raw)
In-Reply-To: <50A22DD7.7020901@gmail.com>
On Tue, Nov 13, 2012 at 6:24 AM, Razvan Cojocaru <rzvncj@gmail.com> wrote:
>> Perhaps it would be useful to build on the vmitools (previously
>> xenaccess)? http://code.google.com/p/vmitools/
>
>
> Indeed, but LibVMI does not offer event-based access, and polling is not
> really a solution.
>
>
>> In general we prefer not to put stuff in the hypervisor unless
>> absolutely required.
>
>
> Me too :)
>
> Thanks,
> Razvan
FYI, vmitools (LibVMI) does have support for memory events, just not
in the main branch. The events branch works properly for 4.1.x; I have
updated it to support 4.2, but due to other more pressing matters, I
have not had time to commit it to the main branch.
If you're interested in using the memory event facilities abstracted
via LibVMI, please let me know.
Steve
next prev parent reply other threads:[~2012-11-15 14:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-12 21:12 Hypervisor to dom0 communication Razvan Cojocaru
2012-11-13 9:59 ` Ian Campbell
2012-11-13 10:26 ` Razvan Cojocaru
2012-11-13 10:36 ` Ian Campbell
2012-11-13 10:49 ` Razvan Cojocaru
2012-11-13 11:12 ` Ian Campbell
2012-11-13 11:24 ` Razvan Cojocaru
2012-11-15 14:26 ` Steven Maresca [this message]
2012-11-15 14:37 ` Razvan Cojocaru
2012-11-16 16:51 ` Razvan Cojocaru
2012-11-15 12:10 ` Tim Deegan
-- strict thread matches above, loose matches on Subject: below --
2008-07-10 12:26 Matthew Donovan
2008-07-11 14:47 ` Mark Williamson
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=CANSvah4437FvmZe-uvcrZOvC2NJ7hZUE8y9DUFUd29BWPHRc6g@mail.gmail.com \
--to=steve@zentific.com \
--cc=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).