Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit 679e2ea7 authored by Heiko Carstens's avatar Heiko Carstens Committed by Martin Schwidefsky
Browse files

[S390] Remove Kerntypes leftovers 



Remove last traces of our kerntypes patch which was always an addon
patch which never got upstream. Somehow a few bits got upstream
anyway.
Since kerntypes aren't used anymore and lcrash isn't maintained (for
s390 at least) remove the last traces of kerntypes that somehow went
upstream. Also remove the documentation that mentions lcrash.

Signed-off-by: default avatarHeiko Carstens <heiko.carstens@de.ibm.com>
Signed-off-by: default avatarMartin Schwidefsky <schwidefsky@de.ibm.com>
parent d68bddb7

Documentation/dontdiff

+0 −1
Original line number Original line Diff line number Diff line
@@ -66,7 +66,6 @@ GRTAGS 
GSYMS

GSYMS

GTAGS

GTAGS

Image

Image

Kerntypes

Module.markers

Module.markers

Module.symvers

Module.symvers

PENDING

PENDING

Documentation/s390/Debugging390.txt

+0 −34
Original line number Original line Diff line number Diff line
@@ -41,7 +41,6 @@ ldd 
Debugging modules

Debugging modules

The proc file system

The proc file system

Starting points for debugging scripting languages etc.

Starting points for debugging scripting languages etc.

Dumptool & Lcrash

SysRq

SysRq

References

References

Special Thanks

Special Thanks
@@ -2455,39 +2454,6 @@ jdb <filename> another fully interactive gdb style debugger. 












Dumptool & Lcrash ( lkcd )

==========================

Michael Holzheu & others here at IBM have a fairly mature port of 

SGI's lcrash tool which allows one to look at kernel structures in a

running kernel.



It also complements a tool called dumptool which dumps all the kernel's

memory pages & registers to either a tape or a disk.

This can be used by tech support or an ambitious end user do

post mortem debugging of a machine like gdb core dumps.



Going into how to use this tool in detail will be explained

in other documentation supplied by IBM with the patches & the 

lcrash homepage http://oss.sgi.com/projects/lkcd/ & the lcrash manpage.



How they work

-------------

Lcrash is a perfectly normal program,however, it requires 2 

additional files, Kerntypes which is built using a patch to the 

linux kernel sources in the linux root directory & the System.map.



Kerntypes is an objectfile whose sole purpose in life

is to provide stabs debug info to lcrash, to do this

Kerntypes is built from kerntypes.c which just includes the most commonly

referenced header files used when debugging, lcrash can then read the

.stabs section of this file.



Debugging a live system it uses /dev/mem

alternatively for post mortem debugging it uses the data 

collected by dumptool.







SysRq

SysRq

=====

=====

This is now supported by linux for s/390 & z/Architecture.

This is now supported by linux for s/390 & z/Architecture.

arch/s390/boot/Makefile

+1 −1
Original line number Original line Diff line number Diff line
@@ -23,4 +23,4 @@ $(obj)/compressed/vmlinux: FORCE 




install: $(CONFIGURE) $(obj)/image

install: $(CONFIGURE) $(obj)/image

	sh -x  $(srctree)/$(obj)/install.sh $(KERNELRELEASE) $(obj)/image \

	sh -x  $(srctree)/$(obj)/install.sh $(KERNELRELEASE) $(obj)/image \

	      System.map Kerntypes "$(INSTALL_PATH)"
 
	      System.map "$(INSTALL_PATH)"