Dave Anderson wrote:
The patch tests OK, and I don't believe any other vtop-related
changes are required, but given that the ppc64.c was contributed
by IBM, can I get an ACK from the IBM brain-trust out there?
Heh, Dave you beat me by few mins. I drafted a mail with a
patch to fix this issue and was about to post it.
I ack that the patch works well. Infact this patch is also
required as it fixes a problem with kmem -s command.
Without this patch the o/p looks like:
crash> kmem -s
CACHE NAME OBJSIZE ALLOCATED TOTAL SLABS SSIZE
c000000001542900 jbd_1k 1024 0 0 0 64k
c000000001542e00 jbd_4k 4096 9 15 1 64k
c000000001549200 <C0> 112 128 564 1
64k
kmem: cannot read kmem_cache_s.name string at d000000000123a18
crash>
With the shift value changed to 30 the above command works fine.
crash> kmem -s
CACHE NAME OBJSIZE ALLOCATED TOTAL SLABS SSIZE
c000000001542900 jbd_1k 1024 0 0 0 64k
c000000001542e00 jbd_4k 4096 0 15 1 64k
c000000001549200 dm_snap_pending_exception 112 128 564 1 64k
c000000001549700 dm_snap_exception 32 0 0 0 64k
c000000001545b00 rpc_buffers 2048 8 31 1 64k
c000000273dd5600 rpc_tasks 384 8 168 1 64k
................
...............
Thanks
-Sachin