From mboxrd@z Thu Jan  1 00:00:00 1970
From: David Vrabel <david.vrabel@citrix.com>
Subject: [PATCHv4 0/3] trace: improve hypercall tracing
Date: Mon, 1 Oct 2012 18:47:06 +0100
Message-ID: <1349113629-6338-1-git-send-email-david.vrabel@citrix.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xen.org>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
To: xen-devel@lists.xensource.com
Cc: David Vrabel <david.vrabel@citrix.com>
List-Id: xen-devel@lists.xenproject.org

This series improves the usefulness of xentrace when tracing
hypercalls: some hypercall arguments are added the trace record and
the subcalls in multicalls are traced.

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

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