From: George Dunlap <george.dunlap@eu.citrix.com>
To: xen-devel@lists.xensource.com
Cc: george.dunlap@eu.citrix.com
Subject: [PATCH 00 of 12] xenalyze: Lots of updates
Date: Mon, 28 Nov 2011 16:17:57 +0000 [thread overview]
Message-ID: <patchbomb.1322497077@elijah> (raw)
Updates made recently. Improved areas include:
* Handling of generic records
* Handling of VMEXITs that have multiple kinds of traces
* Handling of MMIO records for non-pagefault traces
* Handling of cr3 enumeration avlues
* Speed improvement for dump mode
next reply other threads:[~2011-11-28 16:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-28 16:17 George Dunlap [this message]
2011-11-28 16:17 ` [PATCH 01 of 12] xenalyze: Allow several summary handlers to register on a single vmexit George Dunlap
2011-11-28 16:17 ` [PATCH 02 of 12] xenalyze: Reorganize cr trace handling George Dunlap
2011-11-28 16:18 ` [PATCH 03 of 12] xenalyze: Function-ize setting of h->post_process George Dunlap
2011-11-28 16:18 ` [PATCH 04 of 12] xenalyze: Introduce generic summary functionality George Dunlap
2011-11-28 16:18 ` [PATCH 05 of 12] xenalyze: Handle new hvm_event traces George Dunlap
2011-11-28 16:18 ` [PATCH 06 of 12] xenalyze: Relocate pio and mmio enumaration structs to their own sub-struct George Dunlap
2011-11-28 16:18 ` [PATCH 07 of 12] xenalyze: Handle MMIO records from different vmexits George Dunlap
2011-11-28 16:18 ` [PATCH 08 of 12] xenalyze: Add option to skip vga range in MMIO enumeration George Dunlap
2011-11-28 16:18 ` [PATCH 09 of 12] xenalyze: Sort cr3 enumerated values by start time George Dunlap
2011-11-28 16:18 ` [PATCH 10 of 12] xenalyze: Enable more cr3 output George Dunlap
2011-11-28 16:18 ` [PATCH 11 of 12] xenalyze: Optimize pcpu_string George Dunlap
2011-11-28 16:18 ` [PATCH 12 of 12] xenalyze: Make max_active_pcpu calculation smarter George Dunlap
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=patchbomb.1322497077@elijah \
--to=george.dunlap@eu.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 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.