xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: David Vrabel <david.vrabel@citrix.com>
To: xen-devel@lists.xen.org
Cc: David Vrabel <david.vrabel@citrix.com>,
	George Dunlap <george.dunlap@citrix.com>
Subject: [PATCHv5 0/4] trace: improve hypercall tracing
Date: Wed, 3 Oct 2012 17:32:23 +0100	[thread overview]
Message-ID: <1349281947-5009-1-git-send-email-david.vrabel@citrix.com> (raw)

xenalyze requires some patches to decode the new trace record format,
these patches will be posted shortly.

Changes since v4:
- Rename trace_hypercall() to __trace_hypercall_entry().
- Use an array for the arguments to include in the hypercall trace
  record.

Changes since v3:
- Trace arguments for a few more hypercalls (vcpu_op and sched_op).

Changes since v2:
- Changed all PV events to use a different subclass.
- Put multicall subcalls into their own subclass (so they can be
  filtered out).
- Use 12 bits to report which arguments are present in the
  PV_HYPERCALL_V2 trace record.

David

             reply	other threads:[~2012-10-03 16:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-03 16:32 David Vrabel [this message]
2012-10-03 16:32 ` [PATCH 1/4] trace: rename trace_hypercall() to __trace_hypercall_entry() David Vrabel
2012-10-03 16:32 ` [PATCH 2/4] trace: allow for different sub-classes of TRC_PV_* tracepoints David Vrabel
2012-10-03 16:32 ` [PATCH 3/4] trace: improve usefulness of hypercall trace record David Vrabel
2012-10-03 16:32 ` [PATCH 4/4] trace: trace hypercalls inside a multicall 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=1349281947-5009-1-git-send-email-david.vrabel@citrix.com \
    --to=david.vrabel@citrix.com \
    --cc=george.dunlap@citrix.com \
    --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 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).