All of lore.kernel.org
 help / color / mirror / Atom feed
From: Razvan Cojocaru <rzvncj@gmail.com>
To: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: Hypervisor to dom0 communication
Date: Tue, 13 Nov 2012 12:49:46 +0200	[thread overview]
Message-ID: <50A225CA.2080705@gmail.com> (raw)
In-Reply-To: <1352802973.7491.40.camel@zakaz.uk.xensource.com>

>> OK, my immediate end-goal is real-time logging of hypervisor events via
>> a dom0 userspace application. These events are always about a currently
>> running virtual machine, and said virtual machine is paused at the time.
>> The userspace tool should be immediately notified, so no polling.
>
> This is very like the ioreq model, where the domain (or maybe just the
> vcpu, I'm not sure) is paused while qemu does its thing.
>
> What sort of events are we talking about here?

A list of interesting registers that changed, that a page fault occured, 
things like that, occasionally containing some small string messages 
with extra information. Should be around 64 bytes or so.

> The right thing to do here is for the userspace tool to communicate with
> the toolstack (by whatever means) rather the hypervisor in order to
> control the domains.

That's what I was thinking too.

> You might also find some inspiration for this sort of model in the
> xenpaging and memshare code.

Will look those things up, I appreciate the replies.

Thanks,
Razvan

  reply	other threads:[~2012-11-13 10:49 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 [this message]
2012-11-13 11:12         ` Ian Campbell
2012-11-13 11:24           ` Razvan Cojocaru
2012-11-15 14:26             ` Steven Maresca
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=50A225CA.2080705@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 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.