xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Don Slutz <dslutz@verizon.com>
To: George Dunlap <george.dunlap@eu.citrix.com>
Cc: Ian Campbell <ian.campbell@citrix.com>,
	Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
	Don Slutz <Don@CloudSwitch.com>,
	Ian Jackson <ian.jackson@eu.citrix.com>,
	Don Slutz <dslutz@verizon.com>,
	xen-devel@lists.xen.org, Jan Beulich <jbeulich@suse.com>
Subject: Re: [PATCH v4 03/15] xenctx: Add -m (--multiple_pages) option to output larger stack
Date: Wed, 19 Mar 2014 21:19:50 -0400	[thread overview]
Message-ID: <532A4236.8060704@terremark.com> (raw)
In-Reply-To: <5329B8EF.2080000@eu.citrix.com>

On 03/19/14 11:34, George Dunlap wrote:
> On 03/18/2014 10:15 PM, Don Slutz wrote:
>> From: Don Slutz <Don@CloudSwitch.com>
>>
>> Important: This is the stack size to display not the configured
>> stack size.
>>
>> Using pictures (for a 3 page configured system):
>>
>>         +------------------+
>>         |                  |
>>         |                  |
>>         |                  |
>>         |                  |
>>         |                  |
>>         +------------------+
>>         |                  |
>>         |                  |
>>         |                  |
>>         |                  |
>>         |                  |
>>         +------------------+
>>         |                  |
>>         |                  |
>>         |                  |
>> SP --> |                  |
>>         |                  |
>>         +------------------+
>
> Sorry, what is this a picture of?  I can't make any sense out of it.  
> Shouldn't this have only one box, the next have two, and the bottom 
> one have three?
>

This is various pictures of a 3 page stack, and where the SP currently 
is.  Each box is a page.  So here the "stack limit" is the end of 1 
page.  In the sense of how much stack is used, you are right it is 1, 2 
and then 3.  This tracks with the value passed for "-m" (see next line).


>>
>> Display using "-m 1" since the used stack pages is 1.
>>
>>         +------------------+
>>         |                  |
>>         |                  |
>>         |                  |
>>         |                  |
>>         |                  |
>>         +------------------+
>>         |                  |
>> SP --> |                  |
>>         |                  |
>>         |                  |
>>         |                  |
>>         +------------------+
>>         |                  |
>>         |                  |
>>         |                  |
>>         |                  |
>>         |                  |
>>         +------------------+
>>

Here the stack limit is end of  page + 1 full page.

>> Display using "-m 2" since the used stack pages is 2.
>>
>>         +------------------+
>>         |                  |
>>         |                  |
>>         |                  |
>>         |                  |
>> SP --> |                  |
>>         +------------------+
>>         |                  |
>>         |                  |
>>         |                  |
>>         |                  |
>>         |                  |
>>         +------------------+
>>         |                  |
>>         |                  |
>>         |                  |
>>         |                  |
>>         |                  |
>>         +------------------+
>>
>> Display using "-m 3" since the used stack pages is 3.
>>

Here the stack limit is end of  page + 2 full pages.


>> Signed-off-by: Don Slutz <Don@CloudSwitch.com>
>> ---
>> v4 Converted from xenctx: Add -2 (--two-pages) option to switch stack 
>> size to 8KiB
>>
>>   tools/xentrace/xenctx.c | 11 ++++++++++-
>>   1 file changed, 10 insertions(+), 1 deletion(-)
>>
>> diff --git a/tools/xentrace/xenctx.c b/tools/xentrace/xenctx.c
>> index 42a47f3..6da38cc 100644
>> --- a/tools/xentrace/xenctx.c
>> +++ b/tools/xentrace/xenctx.c
>> @@ -35,6 +35,7 @@ static struct xenctx {
>>       int frame_ptrs;
>>       int stack_trace;
>>       int disp_all;
>> +    int multiple_pages;
>>       int all_vcpus;
>>       int self_paused;
>>       xc_dominfo_t dominfo;
>> @@ -664,6 +665,8 @@ static int print_stack(vcpu_guest_context_any_t 
>> *ctx, int vcpu, int width)
>>         stack_limit = ((stack_pointer(ctx) + XC_PAGE_SIZE)
>>                      & ~((guest_word_t) XC_PAGE_SIZE - 1));
>> +    if ( xenctx.multiple_pages > 1 )
>> +        stack_limit += (xenctx.multiple_pages - 1) * XC_PAGE_SIZE;
>>       printf("\n");
>>       printf("Stack:\n");
>>       for (i=1; i<5 && stack < stack_limit; i++) {
>> @@ -834,18 +837,21 @@ static void usage(void)
>>           kernel_start);
>>       printf("  -a, --all          display more registers\n");
>>       printf("  -C, --all-vcpus    print info for all vcpus\n");
>> +    printf("  -m PAGES, --multiple-pages=PAGES\n");
>> +    printf("                     assume the kernel was compiled with 
>> PAGES (default 1) of stacks.\n");
>>   }

Opps, this needs fixing.


>>     int main(int argc, char **argv)
>>   {
>>       int ch;
>>       int ret;
>> -    static const char *sopts = "fs:hak:SC";
>> +    static const char *sopts = "fs:hak:SCm:";
>>       static const struct option lopts[] = {
>>           {"stack-trace", 0, NULL, 'S'},
>>           {"symbol-table", 1, NULL, 's'},
>>           {"frame-pointers", 0, NULL, 'f'},
>>           {"kernel-start", 1, NULL, 'k'},
>> +        {"multiple-pages", 0, NULL, 'm'},
>
> I think I would call the long option "kernel-stack-pages" or something 
> like that.  "Multiple pages" doesn't really convey much meaning.  -m 
> is probably a fine short option, but -n might be more memorable.
>

The issue with "kernel-stack-pages" is that it leads to configured 
kernel stack pages (which for the pictures above is 3).  3 is most 
likely not the number to use here.

A big part of this is that how a "kernel" knows where it is in the stack 
can be simple like for a 2 page stack, 1 page is odd, 2nd page is even.  
(3 pages is most likely more complex, but fence page(s) may help here.)

Maybe stack-limit-in-pages is better?

    -Don Slutz

>  -George
>

  reply	other threads:[~2014-03-20  1:19 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 [this message]
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
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=532A4236.8060704@terremark.com \
    --to=dslutz@verizon.com \
    --cc=Don@CloudSwitch.com \
    --cc=george.dunlap@eu.citrix.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).