From: Sam Bobroff <sam.bobroff@au1.ibm.com>
To: linuxppc-dev@ozlabs.org
Cc: khandual@linux.vnet.ibm.com, mpe@ellerman.id.au
Subject: [PATCH v3 2/2] powerpc/xmon: Paginate kernel log buffer display
Date: Thu, 8 Oct 2015 11:50:24 +1100 [thread overview]
Message-ID: <aa70d3c5f38c2e4fa7be78bb926f0aa5e1b8bbcb.1444265419.git.sam.bobroff@au1.ibm.com> (raw)
In-Reply-To: <cover.1444265419.git.sam.bobroff@au1.ibm.com>
In-Reply-To: <cover.1444265419.git.sam.bobroff@au1.ibm.com>
The kernel log buffer is often much longer than the size of a terminal
so paginate it's output.
Signed-off-by: Sam Bobroff <sam.bobroff@au1.ibm.com>
---
arch/powerpc/xmon/xmon.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/arch/powerpc/xmon/xmon.c b/arch/powerpc/xmon/xmon.c
index cc070c3..8ba8ea7 100644
--- a/arch/powerpc/xmon/xmon.c
+++ b/arch/powerpc/xmon/xmon.c
@@ -242,9 +242,7 @@ Commands:\n\
" u dump TLB\n"
#endif
" ? help\n"
-#ifdef CONFIG_PPC64
-" .# limit output to # lines per page (dump paca only)\n"
-#endif
+" .# limit output to # lines per page (for dp#, dpa, dl)\n"
" zr reboot\n\
zh halt\n"
;
@@ -2333,10 +2331,12 @@ dump_log_buf(void)
sync();
kmsg_dump_rewind_nolock(&dumper);
+ xmon_start_pagination();
while (kmsg_dump_get_line_nolock(&dumper, false, buf, sizeof(buf), &len)) {
buf[len] = '\0';
printf("%s", buf);
}
+ xmon_end_pagination();
sync();
/* wait a little while to see if we get a machine check */
--
2.1.4
prev parent reply other threads:[~2015-10-08 0:51 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
2015-10-15 2:33 ` Michael Ellerman
2015-10-15 11:10 ` [v3,1/2] " Michael Ellerman
2015-10-08 0:50 ` Sam Bobroff [this message]
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=aa70d3c5f38c2e4fa7be78bb926f0aa5e1b8bbcb.1444265419.git.sam.bobroff@au1.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).