From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Cooper Subject: Re: How do I print all hypercalls as they come in? Date: Thu, 5 Feb 2015 21:20:58 +0000 Message-ID: <54D3DEBA.4040706@citrix.com> References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============8539005961725837379==" Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: D'Mita Levy , xen-devel@lists.xen.org List-Id: xen-devel@lists.xenproject.org --===============8539005961725837379== Content-Type: multipart/alternative; boundary="------------050206070108010909040308" --------------050206070108010909040308 Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: 7bit On 05/02/15 21:16, D'Mita Levy wrote: > Hello, > > I am trying to compile a xen build that will simply print all the > hypercalls as they come into the hypervisor. Specifically, I'm looking > for the hypercall handler function so that I can insert a simple > printk statement. The logging rate will easily overwhelm your serial connection. What is the actual piece of information you are after? > I'm having trouble because I can't find a doc that describes what most > of the modules found in xen/arch/x86 and x86_64 do...am I right in > thinking that the do_platform_op function in platform_hypercall.c > serves as the entry point for all hypercalls? do_platform_op() is the handler for __HYPERCALL_platform_op which is one single hypercall. The actual hypercall root handler is the 'hypercall' symbol in arch/x86/x86_64/entry.S ~Andrew --------------050206070108010909040308 Content-Type: text/html; charset="windows-1252" Content-Length: 1779 Content-Transfer-Encoding: quoted-printable
On 05/02/15 21:16, D'Mita Levy wrote:
Hello,

I am trying to compile a xen build that will simply print all the hypercalls as they come into the hypervisor. Specifically, I'm looking for the hypercall handler function so that I can insert a simple printk statement.

The logging rate will easily overwhelm your serial connection.=A0 What is the actual piece of information you are after=3F

I'm having trouble because I can't find a doc that describes what most of the modules found in xen/arch/x86 and x86_64 do...am I right in thinking that the do_platform_op function in platform_hypercall.c serves as the entry point for all hypercalls=3F

do_platform_op() is the handler for __HYPERCALL_platform_op which is one single hypercall.

The actual hypercall root handler is the 'hypercall' symbol in arch/x86/x86_64/entry.S

~Andrew
--------------050206070108010909040308-- --===============8539005961725837379== 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.xen.org http://lists.xen.org/xen-devel --===============8539005961725837379==--