linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Anshuman Khandual <khandual@linux.vnet.ibm.com>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: linuxppc-dev@ozlabs.org, mikey@neuling.org
Subject: Re: [PATCH 8/8] powerpc/xmon: Add some more elements to the existing PACA dump list
Date: Wed, 12 Aug 2015 11:57:31 +0530	[thread overview]
Message-ID: <55CAE753.8000807@linux.vnet.ibm.com> (raw)
In-Reply-To: <1439359555.27815.1.camel@ellerman.id.au>

On 08/12/2015 11:35 AM, Michael Ellerman wrote:
> On Wed, 2015-07-29 at 12:40 +0530, Anshuman Khandual wrote:
>> This patch adds a set of new elements to the existing PACA dump list
>> inside an xmon session which can be listed below improving the overall
>> xmon debug support.
>>
>> (1) hmi_event_available
>> (2) dscr_default
>> (3) vmalloc_sllp
>> (4) slb_cache_ptr
>> (5) sprg_vdso
>> (6) tm_scratch
>> (7) core_idle_state_ptr
>> (8) thread_idle_state
>> (9) thread_mask
>> (10) slb_shadow
>> (11) pgd
>> (12) kernel_pgd
>> (13) tcd_ptr
>> (14) mc_kstack
>> (15) crit_kstack
>> (16) dbg_kstack
>> (17) user_time
>> (18) system_time
>> (19) user_time_scaled
>> (20) starttime
>> (21) starttime_user
>> (22) startspurr
>> (23) utime_sspurr
>> (24) stolen_time
> 
> Adding these makes the paca display much longer than 24 lines. I know in
> general we don't worry too much about folks on 80x24 green screens, but it's
> nice if xmon works OK on those. Or on virtual consoles that don't scroll for
> whatever reason.
> 
> So I'm going to hold off on this one until we have a way to display some of the
> paca. I have an idea for that and will send a patch if it works.
> 

Sure, if you believe that is the best thing to do at the moment.

  reply	other threads:[~2015-08-12  6:28 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-29  7:09 [PATCH 1/8] powerpc/slb: Remove a duplicate extern variable Anshuman Khandual
2015-07-29  7:09 ` [PATCH 2/8] powerpc/slb: Rename all the 'slot' occurrences to 'entry' Anshuman Khandual
2015-08-13  1:44   ` [2/8] " Michael Ellerman
2015-07-29  7:10 ` [PATCH 3/8] powerpc/slb: Define macros for the bolted slots Anshuman Khandual
2015-07-29  7:10 ` [PATCH 4/8] powerpc/slb: Add some helper functions to improve modularization Anshuman Khandual
2015-08-12  4:11   ` [4/8] " Michael Ellerman
2015-08-12  6:36     ` Anshuman Khandual
2015-07-29  7:10 ` [PATCH 5/8] powerpc/slb: Add documentation to runtime patching of SLB encoding Anshuman Khandual
2015-08-12  5:12   ` [5/8] " Michael Ellerman
2015-08-13  1:44   ` Michael Ellerman
2015-07-29  7:10 ` [PATCH 6/8] powerpc/prom: Simplify the logic while fetching SLB size Anshuman Khandual
2015-08-13  1:44   ` [6/8] " Michael Ellerman
2015-07-29  7:10 ` [PATCH 7/8] powerpc/xmon: Drop the 'valid' variable completely in 'dump_segments' Anshuman Khandual
2015-08-13  1:44   ` [7/8] " Michael Ellerman
2015-07-29  7:10 ` [PATCH 8/8] powerpc/xmon: Add some more elements to the existing PACA dump list Anshuman Khandual
2015-08-12  6:05   ` Michael Ellerman
2015-08-12  6:27     ` Anshuman Khandual [this message]
2015-08-13  1:44 ` [1/8] powerpc/slb: Remove a duplicate extern variable Michael Ellerman

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=55CAE753.8000807@linux.vnet.ibm.com \
    --to=khandual@linux.vnet.ibm.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=mikey@neuling.org \
    --cc=mpe@ellerman.id.au \
    /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).