linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Michael Ellerman <michael@ellerman.id.au>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] powerpc: Add an xmon command to dump one or all pacas
Date: Fri, 14 Sep 2012 14:44:30 +1000	[thread overview]
Message-ID: <1347597870.6883.0.camel@concordia> (raw)
In-Reply-To: <1347439541.2603.100.camel@pasglop>

On Wed, 2012-09-12 at 18:45 +1000, Benjamin Herrenschmidt wrote:
> On Wed, 2012-09-12 at 17:52 +1000, Michael Ellerman wrote:
> > This was originally motivated by a desire to see the mapping between
> > logical and hardware cpu numbers.
> > 
> > But it seemed that it made more sense to just add a command to dump
> > (most of) the paca.
> > 
> > With no arguments "dp" will dump the paca for all possible cpus. If
> > there are no possible cpus, like early in boot, it will tell you that.
> 
> I'd rather "dp" dump the paca for the current active CPU in xmon.
> Shouldn't be hard to make a "dpa" that dumps them all too.

OK.

I also want to be able to dump the paca of a cpu not in xmon, so I'll
keep the "dp #" variant as well.

cheers

  reply	other threads:[~2012-09-14  4:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-12  7:52 [PATCH] powerpc: Add an xmon command to dump one or all pacas Michael Ellerman
2012-09-12  8:45 ` Benjamin Herrenschmidt
2012-09-14  4:44   ` Michael Ellerman [this message]
2012-09-14  5:45     ` Benjamin Herrenschmidt
2012-09-12 11:07 ` Stephen Rothwell
2012-09-14  4:45   ` Michael Ellerman
  -- strict thread matches above, loose matches on Subject: below --
2012-09-14  6:03 Michael Ellerman
2012-09-14  8:59 ` Michael Ellerman
2012-09-14  9:01 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=1347597870.6883.0.camel@concordia \
    --to=michael@ellerman.id.au \
    --cc=benh@kernel.crashing.org \
    --cc=linuxppc-dev@ozlabs.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).