From: Sam Bobroff <sam.bobroff@au1.ibm.com>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: linuxppc-dev@ozlabs.org, khandual@linux.vnet.ibm.com
Subject: Re: [PATCH v3 1/2] powerpc/xmon: Paged output for paca display
Date: Thu, 15 Oct 2015 09:24:38 +1100 [thread overview]
Message-ID: <20151014222438.GA1900@tungsten.ozlabs.ibm.com> (raw)
In-Reply-To: <1444815549.1843.4.camel@ellerman.id.au>
On Wed, Oct 14, 2015 at 08:39:09PM +1100, Michael Ellerman wrote:
> On Thu, 2015-10-08 at 11:50 +1100, Sam Bobroff wrote:
> > The paca display is already more than 24 lines, which can be problematic
> > if you have an old school 80x24 terminal, or more likely you are on a
> > virtual terminal which does not scroll for whatever reason.
> >
> > This patch adds a new command ".", which takes a single (hex) numeric
> > argument: lines per page. It will cause the output of "dp" and "dpa"
> > to be broken into pages, if necessary.
> >
> > Sample output:
> >
> > 0:mon> .10
>
> So what about making it "#" rather than "." ?
>
> cheers
Sure, although we'll have to do a better job than the other commands in the help text ;-)
(They use "#" to indicate a hex number and "##" is just going to be confusing.)
Do you want me to respin? (I'm happy for you to just adjust the patch.)
Cheers,
Sam.
next prev parent reply other threads:[~2015-10-14 22:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-08 0:50 [PATCH v3 0/2] powerpc/xmon: Paged output for paca display Sam Bobroff
2015-10-08 0:50 ` [PATCH v3 1/2] " Sam Bobroff
2015-10-14 9:39 ` Michael Ellerman
2015-10-14 22:24 ` Sam Bobroff [this message]
2015-10-15 2:33 ` Michael Ellerman
2015-10-15 11:10 ` [v3,1/2] " Michael Ellerman
2015-10-08 0:50 ` [PATCH v3 2/2] powerpc/xmon: Paginate kernel log buffer display Sam Bobroff
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=20151014222438.GA1900@tungsten.ozlabs.ibm.com \
--to=sam.bobroff@au1.ibm.com \
--cc=khandual@linux.vnet.ibm.com \
--cc=linuxppc-dev@ozlabs.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).