From: Douglas Miller <hidden> Date: 2017-02-07 13:40:50
Extend dump command to allow display of 2, 4, and 8 byte words in native
endian format. Also adds dump command for "1 byte words" for the sake
of symmetry. New commands are:
d1 dump 8 bit values
d2 dump 16 bit values
d4 dump 32 bit values
d8 dump 64 bit values
Signed-off-by: Douglas Miller <redacted>
---
arch/powerpc/xmon/xmon.c | 65 +++++++++++++++++++++++++++++++++++++++++++--
1 files changed, 62 insertions(+), 3 deletions(-)
On Tue, Feb 07, 2017 at 07:40:44AM -0600, Douglas Miller wrote:
quoted hunk
Extend dump command to allow display of 2, 4, and 8 byte words in native
endian format. Also adds dump command for "1 byte words" for the sake
of symmetry. New commands are:
d1 dump 8 bit values
d2 dump 16 bit values
d4 dump 32 bit values
d8 dump 64 bit values
Signed-off-by: Douglas Miller <redacted>
---
arch/powerpc/xmon/xmon.c | 65 +++++++++++++++++++++++++++++++++++++++++++--
1 files changed, 62 insertions(+), 3 deletions(-)
We have a method of printing a special character for faults.
Please see fault_chars[]
Otherwise looks good
Acked-by: Balbir Singh <bsingharora@gmail.com>
From: Michael Ellerman <mpe@ellerman.id.au> Date: 2017-02-08 09:18:11
Balbir Singh [off-list ref] writes:
On Tue, Feb 07, 2017 at 07:40:44AM -0600, Douglas Miller wrote:
quoted
Extend dump command to allow display of 2, 4, and 8 byte words in native
endian format. Also adds dump command for "1 byte words" for the sake
of symmetry. New commands are:
d1 dump 8 bit values
d2 dump 16 bit values
d4 dump 32 bit values
d8 dump 64 bit values
Signed-off-by: Douglas Miller <redacted>
On Wed, Feb 08, 2017 at 08:18:07PM +1100, Michael Ellerman wrote:
Balbir Singh [off-list ref] writes:
quoted
quoted
+ printf("Faulted reading %d bytes from 0x"REG"\n", 16, addr);
We have a method of printing a special character for faults.
Please see fault_chars[]
Yeah but it's not worth the complication IMO. In practice you usually
fault on everything you tried to print or nothing.
Fair enough, I was worried about consistency across commands and its
quite possible that on crossing a page boundary we see inconsistent
output. I'm OK with it, one can always retry the command with smaller
number of bytes.
Balbir Singh.
I know the ascii dump looks nice, but I think it's misleading. Which is
why I omitted it from my version.
eg.
0:mon> d $__kstrtab_init_task
c000000000c03ebe 696e69745f746173 6b006d6d755f6665 |init_task.mmu_fe|
c000000000c03ece 61747572655f6b65 7973006370755f66 |ature_keys.cpu_f|
c000000000c03ede 6561747572655f6b 657973006375725f |eature_keys.cur_|
c000000000c03eee 6370755f73706563 00766972715f746f |cpu_spec.virq_to|
0:mon> d8 $__kstrtab_init_task
c000000000c03ebe 7361745f74696e69 65665f756d6d006b |init_task.mmu_fe|
c000000000c03ece 656b5f6572757461 665f757063007379 |ature_keys.cpu_f|
c000000000c03ede 6b5f657275746165 5f72756300737965 |eature_keys.cur_|
c000000000c03eee 636570735f757063 6f745f7172697600 |cpu_spec.virq_to|
That second dump says at c000000000c03ebe there is a byte with the value
0x73, which prints as 'i' - but that's false.
So I've dropped the ascii printing for now because I want to sneak this
in to v4.11.
If you want to send a follow-up patch to do the ascii byte reversed that
would be nice.
cheers
I know the ascii dump looks nice, but I think it's misleading. Which is
why I omitted it from my version.
eg.
0:mon> d $__kstrtab_init_task
c000000000c03ebe 696e69745f746173 6b006d6d755f6665 |init_task.mmu_fe|
c000000000c03ece 61747572655f6b65 7973006370755f66 |ature_keys.cpu_f|
c000000000c03ede 6561747572655f6b 657973006375725f |eature_keys.cur_|
c000000000c03eee 6370755f73706563 00766972715f746f |cpu_spec.virq_to|
0:mon> d8 $__kstrtab_init_task
c000000000c03ebe 7361745f74696e69 65665f756d6d006b |init_task.mmu_fe|
c000000000c03ece 656b5f6572757461 665f757063007379 |ature_keys.cpu_f|
c000000000c03ede 6b5f657275746165 5f72756300737965 |eature_keys.cur_|
c000000000c03eee 636570735f757063 6f745f7172697600 |cpu_spec.virq_to|
That second dump says at c000000000c03ebe there is a byte with the value
0x73, which prints as 'i' - but that's false.
So I've dropped the ascii printing for now because I want to sneak this
in to v4.11.
If you want to send a follow-up patch to do the ascii byte reversed that
would be nice.
cheers
I would disagree, anything printed as bytes should be in only one order
- the order it exists in memory. I maintain that the ascii dump is
correctly printed. The purpose of an ascii dump like this is to show
what is in memory. ASCII in memory has only one order.
Thanks,
Doug
From: Michael Ellerman <hidden> Date: 2017-02-27 10:11:03
On Tue, 2017-02-07 at 13:40:44 UTC, Douglas Miller wrote:
Extend dump command to allow display of 2, 4, and 8 byte words in native
endian format. Also adds dump command for "1 byte words" for the sake
of symmetry. New commands are:
Signed-off-by: Douglas Miller <redacted>
Acked-by: Balbir Singh <bsingharora@gmail.com>