On Wed, Oct 03, 2018 at 08:52:00AM -0400, Dave Anderson wrote:
>
>
> - Original Message -
> >
> ... [ cut ] ...
> >
> > How about the following layout? The following shows the sections
> > which belong to the memory block.
> >
> > crash> kmem -n
> > ...
> > NR SECTION
- Original Message -
>
... [ cut ] ...
>
> How about the following layout? The following shows the sections
> which belong to the memory block.
>
> crash> kmem -n
> ...
> NR SECTIONCODED_MEM_MAPMEM_MAP STATE PFN
> 0 88047e5d6000 ea00
Hi Dave,
Thank you for your comment.
On Tue, Oct 02, 2018 at 12:02:35PM -0400, Dave Anderson wrote:
>
>
> - Original Message -
> > From: Masayoshi Mizuma
> >
> > Update for the "kmem -n" option to also dump memory block.
> > Currently, "kmem -n" shows the memory section only. This
>
- Original Message -
> From: Masayoshi Mizuma
>
> Update for the "kmem -n" option to also dump memory block.
> Currently, "kmem -n" shows the memory section only. This
> patch gets available the memory block as well if 'memory_block'
> structure and 'memory_subsys' symbol exist.
> The
From: Masayoshi Mizuma
Update for the "kmem -n" option to also dump memory block.
Currently, "kmem -n" shows the memory section only. This
patch gets available the memory block as well if 'memory_block'
structure and 'memory_subsys' symbol exist.
The memory block information is useful to
