From: Douglas Miller <dougmill@linux.vnet.ibm.com>
To: linuxppc-dev@lists.ozlabs.org
Subject: xmon memory dump does not handle LE
Date: Thu, 2 Feb 2017 08:42:30 -0600 [thread overview]
Message-ID: <2a0e256f-4947-e94d-7f79-5451b3c90f9f@linux.vnet.ibm.com> (raw)
I was hoping this would be any easy fix, but now it looks like it will
be more difficult.
The basic problem is that xmon memory commands like 'dd' do not properly
display the data on LE instances. This means that not only is it
difficult to read but one cannot copy-paste addresses from the output.
This severely encumbers debugging using xmon on LE systems.
It looks like prdump() is highly optimized but only works on BE. Have I
missed something, or will it take a significant re-write of this code to
fix the LE problem?
Thanks,
Doug
next reply other threads:[~2017-02-02 14:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-02 14:42 Douglas Miller [this message]
2017-02-03 1:46 ` xmon memory dump does not handle LE Michael Ellerman
2017-02-03 3:07 ` Douglas Miller
2017-02-03 10:31 ` Michael Ellerman
2017-02-06 13:50 ` Douglas Miller
2017-02-06 20:37 ` Douglas Miller
2017-02-07 1:00 ` 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=2a0e256f-4947-e94d-7f79-5451b3c90f9f@linux.vnet.ibm.com \
--to=dougmill@linux.vnet.ibm.com \
--cc=linuxppc-dev@lists.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).