From mboxrd@z Thu Jan 1 00:00:00 1970 From: ravi kerur Subject: Re: event notification Date: Wed, 10 Mar 2010 15:20:43 -0800 Message-ID: References: <20100308164727.GA4568@phenom.dumpdata.com> <1268237356.11737.70451.camel@zakaz.uk.xensource.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0980643890==" Return-path: In-Reply-To: <1268237356.11737.70451.camel@zakaz.uk.xensource.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Ian Campbell Cc: "xen-devel@lists.xensource.com" , Konrad Rzeszutek Wilk List-Id: xen-devel@lists.xenproject.org --===============0980643890== Content-Type: multipart/alternative; boundary=00163630f0b131b85804817a8cc9 --00163630f0b131b85804817a8cc9 Content-Type: text/plain; charset=ISO-8859-1 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? Thanks -RK On Wed, Mar 10, 2010 at 8:09 AM, Ian Campbell 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. > > > --00163630f0b131b85804817a8cc9 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable 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 kern= el modules as well?

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 i= n dom0 can
> > register to it and when a VM(domU) is installed or deleted or sus= pend or
> > resumed kernel module in domU can send notification to its counte= rpart 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 devi= ce
> 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<= br> (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&= quot;
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.



--00163630f0b131b85804817a8cc9-- --===============0980643890== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel --===============0980643890==--