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 2/2] trace: trace hypercalls inside a multicall
Date: Mon, 28 May 2012 17:09:59 +0100 [thread overview]
Message-ID: <4FC3A357.6060600@citrix.com> (raw)
In-Reply-To: <7CE799CC0E4DE04B88D5FDF226E18AC2CDEB431491@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>
>>
>> Add a trace record for every hypercall inside a multicall.
>>
>> Signed-off-by: David Vrabel <david.vrabel@citrix.com>
>> ---
[...]
> Good, I'd personally add a way (subclass perhaps) to exclude such traces
> as could be very performance consuming.
Yes, that sounds like a good idea.
> I'd also add something like sub op (shadow_op or domctl operations have
> sub operations which could be useful to understand).
Patches welcome! ;)
David
prev parent reply other threads:[~2012-05-28 16:09 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
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 [this message]
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=4FC3A357.6060600@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).