From: George Dunlap <george.dunlap@eu.citrix.com>
To: Don Slutz <dslutz@verizon.com>, xen-devel@lists.xen.org
Cc: Don Slutz <Don@CloudSwitch.com>,
Ian Jackson <ian.jackson@eu.citrix.com>,
Ian Campbell <ian.campbell@citrix.com>,
Jan Beulich <jbeulich@suse.com>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: [PATCH v4 09/15] xenctx: Add command line option -T (--tag-call-trace)
Date: Wed, 19 Mar 2014 16:20:00 +0000 [thread overview]
Message-ID: <5329C3B0.9070909@eu.citrix.com> (raw)
In-Reply-To: <1395180940-23901-10-git-send-email-dslutz@verizon.com>
On 03/18/2014 10:15 PM, Don Slutz wrote:
> If specified, add stack addr to call trace.
>
> Here is an example:
>
> Call Trace:
> [<ffffffff8006b2b0>] default_idle+0x29 <--
> ffffffff803ddf90: [<ffffffff80048d19>] cpu_idle+0x95
> ffffffff803ddfa0: [<ffffffff803e7801>] start_kernel+0x220
> ffffffff803ddfc0: [<ffffffff803e722f>] x86_64_start_kernel+0x22f
>
> and
>
> Stack Trace:
> * [<ffffffff8006b2b0>] default_idle+0x29 <--
> ffffffff803ddf90: [<ffffffff80048d19>] cpu_idle+0x95
> ffffffff803ddf98: 0000000000200800
> ffffffff803ddfa0: [<ffffffff803e7801>] start_kernel+0x220
> ffffffff803ddfa8: 0000000000086800
> ffffffff803ddfb0: 0000000000000000
> ffffffff803ddfb8: ffffffff80430720
> ffffffff803ddfc0: [<ffffffff803e722f>] x86_64_start_kernel+0x22f
> ffffffff803ddfc8: 80008e000010019c
> ffffffff803ddfd0: 00000000ffffffff
> ffffffff803ddfd8: 0000000000000000
> ffffffff803ddfe0: 0000000000000000
> ffffffff803ddfe8: 0000000000200000
> ffffffff803ddff0: 0000000000000000
> ffffffff803ddff8: 0000000000000000
>
> Signed-off-by: Don Slutz <Don@CloudSwitch.com>
> ---
> tools/xentrace/xenctx.c | 53 ++++++++++++++++++++++++++++++++++++++++++-------
> 1 file changed, 46 insertions(+), 7 deletions(-)
>
> diff --git a/tools/xentrace/xenctx.c b/tools/xentrace/xenctx.c
> index 22a1704..e5c45df 100644
> --- a/tools/xentrace/xenctx.c
> +++ b/tools/xentrace/xenctx.c
> @@ -40,6 +40,7 @@ static struct xenctx {
> int lines;
> int decode_as_ascii;
> int tag_stack_dump;
> + int tag_call_trace;
> int all_vcpus;
> int self_paused;
> xc_dominfo_t dominfo;
> @@ -732,6 +733,8 @@ static int print_stack(vcpu_guest_context_any_t *ctx, int vcpu, int width)
> printf("Stack Trace:\n");
> else
> printf("Call Trace:\n");
> + if ( xenctx.tag_call_trace )
> + printf(" %*s", width*2, "");
> printf("%c [<", xenctx.stack_trace ? '*' : ' ');
> print_stack_word(instr_pointer(ctx), width);
> printf(">]");
> @@ -747,9 +750,15 @@ static int print_stack(vcpu_guest_context_any_t *ctx, int vcpu, int width)
> p = map_page(ctx, vcpu, stack);
> if (!p)
> return -1;
> - printf("| ");
> + if ( xenctx.tag_call_trace )
> + {
> + print_stack_word(stack, width);
> + printf(": | ");
> + } else {
> + printf("| ");
> + }
> print_stack_word(read_stack_word(p, width), width);
> - printf(" \n");
> + printf("\n");
> stack += width;
> }
> } else {
> @@ -761,7 +770,13 @@ static int print_stack(vcpu_guest_context_any_t *ctx, int vcpu, int width)
> return -1;
> frame = read_stack_word(p, width);
> if (xenctx.stack_trace) {
> - printf("|-- ");
> + if ( xenctx.tag_call_trace )
> + {
> + print_stack_word(stack, width);
> + printf(": |-- ");
> + } else {
> + printf("|-- ");
> + }
> print_stack_word(read_stack_word(p, width), width);
> printf("\n");
> }
> @@ -772,7 +787,13 @@ static int print_stack(vcpu_guest_context_any_t *ctx, int vcpu, int width)
> if (!p)
> return -1;
> word = read_stack_word(p, width);
> - printf("%c [<", xenctx.stack_trace ? '|' : ' ');
> + if ( xenctx.tag_call_trace )
> + {
> + print_stack_word(stack, width);
> + printf(": %c [<", xenctx.stack_trace ? '|' : ' ');
> + } else {
> + printf("%c [<", xenctx.stack_trace ? '|' : ' ');
> + }
> print_stack_word(word, width);
> printf(">]");
> print_symbol(word);
> @@ -788,13 +809,25 @@ static int print_stack(vcpu_guest_context_any_t *ctx, int vcpu, int width)
> return -1;
> word = read_stack_word(p, width);
> if (is_kernel_text(word)) {
> - printf(" [<");
> + if ( xenctx.tag_call_trace )
> + {
> + print_stack_word(stack, width);
> + printf(": [<");
> + } else {
> + printf(" [<");
> + }
> print_stack_word(word, width);
> printf(">]");
> print_symbol(word);
> printf("\n");
> } else if (xenctx.stack_trace) {
> - printf(" ");
> + if ( xenctx.tag_call_trace )
> + {
> + print_stack_word(stack, width);
> + printf(": ");
> + } else {
> + printf(" ");
> + }
> print_stack_word(word, width);
> printf("\n");
> }
> @@ -893,13 +926,15 @@ static void usage(void)
> printf(" add a decode of Stack dump as ascii.\n");
> printf(" -t, --tag-stack-dump\n");
> printf(" add address on each line of Stack dump.\n");
> + printf(" -T, --tag-call-trace\n");
> + printf(" add address on each line of Call trace.\n");
Since this happens for either a call trace or a stack trace, would it
make more sense to make the long version "--tag-trace", and the
description say something like "add address on each line of the call or
stack trace"?
-George
next prev parent reply other threads:[~2014-03-19 16:20 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-18 22:15 [PATCH v4 00/15] xenctx: Many changes Don Slutz
2014-03-18 22:15 ` [PATCH v4 01/15] xenctx: clean up usage output Don Slutz
2014-03-19 15:16 ` George Dunlap
2014-03-18 22:15 ` [PATCH v4 02/15] xenctx: Clean up stack trace when hypercall_page not in symbol table Don Slutz
2014-03-19 15:18 ` George Dunlap
2014-03-18 22:15 ` [PATCH v4 03/15] xenctx: Add -m (--multiple_pages) option to output larger stack Don Slutz
2014-03-19 15:34 ` George Dunlap
2014-03-20 1:19 ` Don Slutz
2014-03-20 10:52 ` George Dunlap
2014-03-18 22:15 ` [PATCH v4 04/15] xenctx: Add command line options -b and -l Don Slutz
2014-03-19 15:48 ` George Dunlap
2014-03-20 1:03 ` Don Slutz
2014-03-18 22:15 ` [PATCH v4 05/15] xenctx: Add command line option -D (--decode-as-ascii) Don Slutz
2014-03-19 16:09 ` George Dunlap
2014-03-20 0:57 ` Don Slutz
2014-03-18 22:15 ` [PATCH v4 06/15] xenctx: Add command line option -t (--tag-stack-dump) Don Slutz
2014-03-19 16:10 ` George Dunlap
2014-03-18 22:15 ` [PATCH v4 07/15] xenctx: Change print_symbol to do the space before Don Slutz
2014-03-19 16:12 ` George Dunlap
2014-03-18 22:15 ` [PATCH v4 08/15] xenctx: More info on failed to map page Don Slutz
2014-03-19 16:16 ` George Dunlap
2014-03-18 22:15 ` [PATCH v4 09/15] xenctx: Add command line option -T (--tag-call-trace) Don Slutz
2014-03-19 16:20 ` George Dunlap [this message]
2014-03-20 0:55 ` Don Slutz
2014-03-18 22:15 ` [PATCH v4 10/15] xenctx: Add -M <maddr> option to dump memory at maddr Don Slutz
2014-03-19 17:08 ` George Dunlap
2014-03-20 1:36 ` Don Slutz
2014-03-18 22:15 ` [PATCH v4 11/15] xenctx: Add -d <daddr> option to dump memory at daddr as a stack Don Slutz
2014-03-18 22:15 ` [PATCH v4 12/15] xenctx: change is_kernel_text() into kernel_addr() Don Slutz
2014-03-18 22:15 ` [PATCH v4 13/15] xenctx: Add convert of more registers to symbols Don Slutz
2014-03-19 8:30 ` Jan Beulich
2014-03-19 13:54 ` Don Slutz
2014-03-18 22:15 ` [PATCH v4 14/15] xenctx: Add output of vcpu value and state for --all-vcpus Don Slutz
2014-03-19 8:32 ` Jan Beulich
2014-03-19 13:36 ` Don Slutz
2014-03-18 22:15 ` [PATCH v4 15/15] xenctx: Fix handling of !guest_protected_mode Don Slutz
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=5329C3B0.9070909@eu.citrix.com \
--to=george.dunlap@eu.citrix.com \
--cc=Don@CloudSwitch.com \
--cc=dslutz@verizon.com \
--cc=ian.campbell@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=jbeulich@suse.com \
--cc=stefano.stabellini@eu.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).