From: Andrew Cooper <andrew.cooper3@citrix.com>
To: D'Mita Levy <dlevy022@fiu.edu>, xen-devel@lists.xen.org
Subject: Re: How do I print all hypercalls as they come in?
Date: Thu, 5 Feb 2015 21:20:58 +0000 [thread overview]
Message-ID: <54D3DEBA.4040706@citrix.com> (raw)
In-Reply-To: <CANiypX6nUvYJunNuPFA-hfFAQb6sg4NOuGUVhTCz=W8uLwm9jw@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 845 bytes --]
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
[-- Attachment #1.2: Type: text/html, Size: 1737 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2015-02-05 21:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-05 21:16 How do I print all hypercalls as they come in? D'Mita Levy
2015-02-05 21:20 ` Andrew Cooper [this message]
2015-02-06 15:17 ` D'Mita Levy
2015-02-06 15:23 ` Andrew Cooper
2015-02-12 18:19 ` D'Mita Levy
2015-02-12 18:35 ` Andrew Cooper
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=54D3DEBA.4040706@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=dlevy022@fiu.edu \
--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.