From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mats Petersson Subject: Re: Callbacks for domU into dom0 Date: Wed, 31 Oct 2007 19:11:15 +0000 Message-ID: <4728d2cf.03e9300a.4735.ffff97cc@mx.google.com> References: <4728B183.2050102@jikos.cz> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1"; format=flowed Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <4728B183.2050102@jikos.cz> References: <4728B183.2050102@jikos.cz> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org At 16:46 31/10/2007, Tom=E1=9A Kouba wrote: >Hello, >is there a way how to be informed (called back) in dom0, >when a specific action is taken in domU? > >I would like to react on a system call being issued in domU. >If this is impossible is there any other action in domU that I can >hook my function on? The Xen kernel doesn't know (or care) about Linux (or Windows) system=20 calls as such. Some system calls will "do things" that the Xen kernel does care=20 about, such as update page tables, which will cause an entry into the=20 Xen kernel. The only way for Xen to "know" about a system call would be if you=20 modify the system call itself to perform some sort of operation that=20 causes the Xen kernel to get involved with that. You could for=20 example fake a MSR read or write [by "fake" I mean to a unused MSR=20 number] operation inside the syscall , and then update the MSR read=20 or write function to detect your system call. Does this help you? -- Mats >Thank you very much, > >-- >Tomas Kouba > >_______________________________________________ >Xen-devel mailing list >Xen-devel@lists.xensource.com >http://lists.xensource.com/xen-devel