From: Ian Campbell <Ian.Campbell@citrix.com>
To: ravi kerur <rkerur@gmail.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: Re: event notification
Date: Thu, 11 Mar 2010 07:43:00 +0000 [thread overview]
Message-ID: <1268293380.11261.53.camel@localhost.localdomain> (raw)
In-Reply-To: <dfc283f41003101520n4905378s65210188e9bc0f6@mail.gmail.com>
On Wed, 2010-03-10 at 23:20 +0000, ravi kerur wrote:
> Thanks Ian and Konrad. I thought monitoring udev events or xen store
> watch can be done from user-level apps. I am wondering can they be
> used from kernel modules as well?
xenstore can. I don't think udev can.
Ian.
>
> Thanks
> -RK
>
> On Wed, Mar 10, 2010 at 8:09 AM, Ian Campbell
> <Ian.Campbell@citrix.com> wrote:
> On Mon, 2010-03-08 at 16:47 +0000, Konrad Rzeszutek Wilk
> wrote:
> > On Sat, Mar 06, 2010 at 07:12:02PM -0800, ravi kerur wrote:
> > > Hi,
> > >
> > > Is there a mechanism available in Xen such that a kernel
> module in dom0 can
> > > register to it and when a VM(domU) is installed or deleted
> or suspend or
> > > resumed kernel module in domU can send notification to its
> counterpart in
> > > dom0. I have looked into xenbus mechanism used by PV
> drivers and it won't
> > > work for us. Inputs appreciated.
> >
> > You can listen on udev events and see when a vif device has
> been added.
> > Also you can add pieces to the dom0 kernel to send uevents
> when a device
> > is suspended and do something.
> >
> > Attached is a simple program to listen to all uevents..
>
>
> Also if you are specifically interested in domain
> create/destruction
> (from the hypervisors PoV) then I think you can add a xenstore
> watch on
> "@releaseDomain" and "@introduceDomain".
>
> As far as the hypervisor is concerned things like migration or
> suspend/resume are just domain creation or destruction, the
> "illusion"
> of anything more is provided by the tools.
>
> If you are interested in the creation/suspension/migration/etc
> of
> domains at the toolstack level then it depends which toolstack
> you are
> targeting.
>
>
>
next prev parent reply other threads:[~2010-03-11 7:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-07 3:12 event notification ravi kerur
2010-03-08 16:47 ` Konrad Rzeszutek Wilk
2010-03-10 16:09 ` Ian Campbell
2010-03-10 23:20 ` ravi kerur
2010-03-11 7:43 ` Ian Campbell [this message]
2010-03-15 23:25 ` Konrad Rzeszutek Wilk
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=1268293380.11261.53.camel@localhost.localdomain \
--to=ian.campbell@citrix.com \
--cc=konrad.wilk@oracle.com \
--cc=rkerur@gmail.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 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).