From: David Vrabel <david.vrabel@citrix.com>
To: Frediano Ziglio <frediano.ziglio@citrix.com>
Cc: George Dunlap <George.Dunlap@eu.citrix.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [PATCH 1/2] trace: improve usefulness of hypercall trace record
Date: Mon, 28 May 2012 17:07:47 +0100 [thread overview]
Message-ID: <4FC3A2D3.9000606@citrix.com> (raw)
In-Reply-To: <7CE799CC0E4DE04B88D5FDF226E18AC2CDEB431490@LONPMAILBOX01.citrite.net>
On 28/05/12 17:03, Frediano Ziglio wrote:
> On Thu, 2012-05-24 at 11:37 +0100, David Vrabel wrote:
>> From: David Vrabel <david.vrabel@citrix.com>
>>
>> Trace hypercalls using a more useful trace record format.
>>
>> The EIP field is removed (it was always somewhere in the hypercall
>> page) and include selected hypercall arguments (the number of calls in
>> a multicall, and the number of PTE updates in an mmu_update).
>>
>
> I think that EIP is quite useful as it allow to understand which code in
> dom0 call that hypercall.
The EIP was always an address in the hypercall page (i.e.,
hypercall_page + op * sizeof(unsigned long)) and doesn't tell you what
made the hypercall. You would need one of the addresses off the guest
stack to find the caller.
> There is also space for an additional parameter without changing trace
> version (adding information in a record should not be a problem).
True, but George was keen on keeping the trace record size to a minimum.
I am tempted to use 5 bits of the first extra word to indicate which
parameters are present in the trace record. This might make the new
format more future-proof, perhaps.
David
next prev parent reply other threads:[~2012-05-28 16:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-24 10:37 [PATCH 0/2] trace: improve hypercall tracing David Vrabel
2012-05-24 10:37 ` [PATCH 1/2] trace: improve usefulness of hypercall trace record David Vrabel
2012-05-24 16:11 ` George Dunlap
2012-05-24 16:14 ` David Vrabel
2012-05-28 16:03 ` Frediano Ziglio
2012-05-28 16:07 ` David Vrabel [this message]
2012-05-24 10:37 ` [PATCH 2/2] trace: trace hypercalls inside a multicall David Vrabel
2012-05-28 16:03 ` Frediano Ziglio
2012-05-28 16:09 ` David Vrabel
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=4FC3A2D3.9000606@citrix.com \
--to=david.vrabel@citrix.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=frediano.ziglio@citrix.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).