Dave
I wanted to bring to notice two more issue that I am currently working.
One regarding changes done with kmem_cache to make it NUMA compliant.
'lists' which was earlier pointing to kmem_list3 structure, lists has
been renamed first as nodelists than it is made into an array of pointer
to kmem_list3 structures. So now we have to traverse the whole list
iteratively to get the same information.
As a result of these change kmem -s command fails. To accomodate
these changes we need to change the function do_slab_chain_percpu_v2 to
access nodelists iteratively. Still working on it to figure out how I
can accommodate these changes.
Second objectsize in kmem_cache has been changed to object_size and this
is enabled only on selecting config option CONFIG_DEBUG_SLAB in the
kernel.
Thanks
Sharyathi Nagesh
On Mon, 2006-03-27 at 13:45 -0500, Dave Anderson wrote:
Maneesh Soni wrote:
> On Mon, Mar 27, 2006 at 09:27:16AM -0500, Dave Anderson wrote:
> <snip>
> >
> > Don't really have one -- the prime function in keeping the crash utility
> > alive is to keep up with kernel data-structure changes that break
> > dependencies that crash has.
> >
>
> Yes, keeping crash up-to-date should be at the top of to-do list. But is
> it OK to change "crash" for kernel code which is still in -mm, -rc,
> -rt etc? Like current crash cannot open 2.6.16-mm1 kdump due to
> pgdat_list related changes. Also, I think developers would like to see
> crash working even with their developmental kernel. So just wondering
> if there is any way to address this issue.
>
Post a patch? As long as it doesn't break backwards-compatibility,
and it addresses kernel changes that presumably will eventually make
it into the mainstream kernel, I don't have a problem with that.
Dave
--
Crash-utility mailing list
Crash-utility(a)redhat.com
https://www.redhat.com/mailman/listinfo/crash-utility