From: Andreas H. <AHE...@de...> - 2002-07-10 13:06:18
|
Hi, yes, the my changes should also be made in the 2.5 tree. For both kernel versions the same headers should be written to the dump file. So, what do you want me to do? I should wait for my 2.5 tree updates until you have checked in your stuff? Would be alright with me. Andreas BTW: Before I have checked in/merged the cross-system-lcrash stuff, I have tagged both the 2.4 and the lkcdutils tree with the tag "before_xlcrash_support". -- Linux for eServer Development Tel : +49-7031-16-4640 Notes mail : Andreas Herrmann/GERMANY/IBM@IBMDE email : ahe...@de... |---------+----------------------------------------> | | "Tom Morano" <tj...@sg...> | | | Sent by: | | | lkc...@li...ur| | | ceforge.net | | | | | | | | | 07/09/02 11:47 PM | | | Please respond to "Tom | | | Morano" | | | | |---------+----------------------------------------> >------------------------------------------------------------------------------------------------------------------------| | | | To: <lkc...@li...>, <lkc...@li...>, Andreas | | Herrmann/Germany/IBM@IBMDE | | cc: "Tom Morano" <tj...@sg...> | | Subject: Re: [lkcd-general] cross-system-lcrash | | | | | >------------------------------------------------------------------------------------------------------------------------| Hi Andreas, Are you planning on making these changes to the kernel files in the 2.5 tree? The reason I ask is that, I need to apply some changes made by Piet Delaney in the 2.5 tree back into the 2.4 tree. Several of the files that Piet modified also are ones you modified with your last checkin. Here is a list of the files with overlapping changes: drivers/dump/dump_base.c drivers/dump/dump_ia64.c include/asm-ia64/dump.h include/linux/dump.h I can change the effected 2.4 files and add Piet's changes to the ones you've already made (they appear to merge cleanly). This does cause us to be slightly out of sync with what we are using at SGI (where I need the changes Piet made but cannot take the ones you have made). It would have been cleaner if we had gotten our changes into both trees before you did your update (it's our falut this did not happen). Do you see any problem with this approach? Thanks, Tom ----- Original Message ----- From: "Andreas Herrmann" <AHE...@de...> To: <lkc...@li...>; <lkc...@li...> Sent: Tuesday, July 09, 2002 9:51 AM Subject: [lkcd-general] cross-system-lcrash > > Hi, > > as announced at lkcd-devel before, I have merged the > branch cross_arch_support of lkcdutils into the HEAD > of the repository > > With special binutils-libraries (libopcodes.a and libbfd.a) > with support for multiple targets it is now possible to build > one lcrash version to fit all supported dump architectures at > once. > > Furthermore I have slightly changed the struct > dump_header_t, dump_header_asm_t in the 2.4 > tree of lkcd. > > Those structures do not contain any long values or > pointers anymore and now they have the attribute packed. > So they should be of the same size regardless on which > architecture they are compiled. > > I think there are still some adaptions needed to make > this code as stable as the 4.1 release. > At least s390, s390x and i386 support were tested. > For ia64 support I cannot say much, except that it > compiles. > > If you are contributing code for lkcdutils be aware that > code has changed a lot. Some explanation about this > can be found in previous mails of mine (see mail > archive of lkcd-devel and topics like cross-lcrash or > cross-system-lcrash) > > > Regards, > > > Andreas > > PS: Last not least here is the content of > README.xlcrash of the source tree: > > -------------------------------------------- > OVERVIEW > ======== > > This version of lcrash supports multiple dump architectures at once. > Dumps of stand alone dump tools for s390/x, livedumps/livsystems > and lkcd dumps of i386 should run with this version of lcrash. > ia64 support is currently untested. > alpha support is not fully implemented at all. > > For help type 'lcrash --help' or 'lcrash -h' > > To start lcrash you can use one of the following: > > # will use defaults (boot/System.map, /dev/mem, /boot/Kerntypes) > $>lcrash > > # old style parameter passing > $>lcrash map dump kerntypes > > # old style parameter passing with specification of architecture of the > dump > $>lcrash -a arch map dump kerntypes > > # new style parameter passing > $>lcrash -m System.map -t Kerntypes -d dump -a arch > > # will use defaults /boot/System.map and /boot/Kerntypes with > # dumpfile dump and specified dump architecture > $>lcrash -d dump -a arch > > > INSTALLATION steps for lcrash with cross arch support > ===================================================== > > 1) install binutils src.rpm > (e.g. rpm -i binutils...src.rpm && cd /usr/src/redhat/SPECS > && rpm -bp binutils.spec) > > 2) install xlcrash source tree > (e.g. from sourceforge cvs ...) > > 3) change to binutils src dir: > > $>./configure --prefix=/usr --exec-prefix=/usr --enable-64-bit-bfd \ > --enable-targets=i386-elf,s390-linux,s390x-linux,alpha-linux,ia64-elf > > 4) change to bfd dir: > > $>make > > 5) change to opcodes dir: > > $>make > > 6) Either install libbfd.a, bfd.h, symcat.h and libopcodes.a and dis-asm.h > using "make install" in steps 4) and 5) or copy the stuff into the > lcrash > source tree (e.g. libs into libklib/ and headers into libklib/include). > WARNING: > If using "make install" to install the binutils stuff it would happen > that > bfd.h doesn't match libbfd.so on your system anymore, because if > multiple > targets are selected for libbfd it is only statically built. > (I have done so without any harm to my system, but who knows? ;-) > > 7) change to lcrash source dir: > > $>./configure --enable-targets=all && make && make install > > > Have fun! > > Andreas > ------------------------------------------------------ > > -- > Linux for eServer Development > Tel : +49-7031-16-4640 > Notes mail : Andreas Herrmann/GERMANY/IBM@IBMDE > email : ahe...@de... > > > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Stuff, things, and much much more. > http://thinkgeek.com/sf > _______________________________________________ > Lkcd-general mailing list > Lkc...@li... > https://lists.sourceforge.net/lists/listinfo/lkcd-general > ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Stuff, things, and much much more. http://thinkgeek.com/sf _______________________________________________ Lkcd-general mailing list Lkc...@li... https://lists.sourceforge.net/lists/listinfo/lkcd-general |
From: Andreas H. <AHE...@de...> - 2002-07-11 12:48:32
|
Hi Tom, I have just updated the 2.5 tree. But I did not change the definition of DUMP_PAGE_SIZE in asm-ia64/dump.h. (neither in 2.4 nor in 2.5 tree) I don't know what you need all the DUMP_PAGE_MIN_XXX and DUMP_PAGE_MAX_XXX macros for. Hence you should decide whether or not to redefine DUMP_PAGE_SIZE here. As you might know I suggested to use a fixed DUMP_PAGE_SIZE of 4K and to store the value of PAGE_SIZE in the member page_size of dump_header_t. Then lcrash can read the size of a system page of the dumped Linux system from the dump header at startup. Currently I know no disadvantages having a fixed DUMP_PAGE_SIZE. The only concern is that the system page size must be a multiple of DUMP_PAGE_SIZE. This is fulfilled when 4K is chosen as DUMP_PAGE_SIZE. Regards, Andreas -- Linux for eServer Development Tel : +49-7031-16-4640 Notes mail : Andreas Herrmann/GERMANY/IBM@IBMDE email : ahe...@de... |
From: Tom M. <tj...@sg...> - 2002-07-10 18:45:48
|
Hi Andreas, Actually, our stuff is already in the 2.5 tree. If you merge your stuff in, I will then update the 2.4 tree with our stuff. Actually, it would be best for me to wait for your 2.5 merge. I can then use your common files (the ones containing both of our changes) when I update 2.4 with our stuff. This will ensure that the commonly modified files will be the same. How does that sound? Thanks, Tom . ----- Original Message ----- From: "Andreas Herrmann" <AHE...@de...> To: "Tom Morano" <tj...@sg...> Cc: <lkc...@li...>; <lkc...@li...> Sent: Wednesday, July 10, 2002 6:05 AM Subject: Re: [lkcd-general] cross-system-lcrash > Hi, > > yes, the my changes should also be made in the 2.5 tree. > For both kernel versions the same headers should be written to > the dump file. > > So, what do you want me to do? > I should wait for my 2.5 tree updates until you have checked > in your stuff? > > Would be alright with me. > > > Andreas > > > BTW: Before I have checked in/merged the cross-system-lcrash stuff, > I have tagged both the 2.4 and the lkcdutils tree with the tag > "before_xlcrash_support". > > > -- > Linux for eServer Development > Tel : +49-7031-16-4640 > Notes mail : Andreas Herrmann/GERMANY/IBM@IBMDE > email : ahe...@de... > > > > |---------+----------------------------------------> > | | "Tom Morano" <tj...@sg...> | > | | Sent by: | > | | lkc...@li...ur| > | | ceforge.net | > | | | > | | | > | | 07/09/02 11:47 PM | > | | Please respond to "Tom | > | | Morano" | > | | | > |---------+----------------------------------------> > >--------------------------------------------------------------------------- ---------------------------------------------| > | | > | To: <lkc...@li...>, <lkc...@li...>, Andreas | > | Herrmann/Germany/IBM@IBMDE | > | cc: "Tom Morano" <tj...@sg...> | > | Subject: Re: [lkcd-general] cross-system-lcrash | > | | > | | > >--------------------------------------------------------------------------- ---------------------------------------------| > > > > Hi Andreas, > > Are you planning on making these changes to the kernel files in the 2.5 > tree? The reason I ask is that, I need to apply some changes made by Piet > Delaney in the 2.5 tree back into the 2.4 tree. Several of the files that > Piet modified also are ones you modified with your last checkin. Here is a > list of the files with overlapping changes: > > drivers/dump/dump_base.c > drivers/dump/dump_ia64.c > include/asm-ia64/dump.h > include/linux/dump.h > > I can change the effected 2.4 files and add Piet's changes to the ones > you've already made (they appear to merge cleanly). This does cause us to > be > slightly out of sync with what we are using at SGI (where I need the > changes > Piet made but cannot take the ones you have made). It would have been > cleaner if we had gotten our changes into both trees before you did your > update (it's our falut this did not happen). > > Do you see any problem with this approach? > > Thanks, > > Tom > > ----- Original Message ----- > From: "Andreas Herrmann" <AHE...@de...> > To: <lkc...@li...>; > <lkc...@li...> > Sent: Tuesday, July 09, 2002 9:51 AM > Subject: [lkcd-general] cross-system-lcrash > > > > > > Hi, > > > > as announced at lkcd-devel before, I have merged the > > branch cross_arch_support of lkcdutils into the HEAD > > of the repository > > > > With special binutils-libraries (libopcodes.a and libbfd.a) > > with support for multiple targets it is now possible to build > > one lcrash version to fit all supported dump architectures at > > once. > > > > Furthermore I have slightly changed the struct > > dump_header_t, dump_header_asm_t in the 2.4 > > tree of lkcd. > > > > Those structures do not contain any long values or > > pointers anymore and now they have the attribute packed. > > So they should be of the same size regardless on which > > architecture they are compiled. > > > > I think there are still some adaptions needed to make > > this code as stable as the 4.1 release. > > At least s390, s390x and i386 support were tested. > > For ia64 support I cannot say much, except that it > > compiles. > > > > If you are contributing code for lkcdutils be aware that > > code has changed a lot. Some explanation about this > > can be found in previous mails of mine (see mail > > archive of lkcd-devel and topics like cross-lcrash or > > cross-system-lcrash) > > > > > > Regards, > > > > > > Andreas > > > > PS: Last not least here is the content of > > README.xlcrash of the source tree: > > > > -------------------------------------------- > > OVERVIEW > > ======== > > > > This version of lcrash supports multiple dump architectures at once. > > Dumps of stand alone dump tools for s390/x, livedumps/livsystems > > and lkcd dumps of i386 should run with this version of lcrash. > > ia64 support is currently untested. > > alpha support is not fully implemented at all. > > > > For help type 'lcrash --help' or 'lcrash -h' > > > > To start lcrash you can use one of the following: > > > > # will use defaults (boot/System.map, /dev/mem, /boot/Kerntypes) > > $>lcrash > > > > # old style parameter passing > > $>lcrash map dump kerntypes > > > > # old style parameter passing with specification of architecture of the > > dump > > $>lcrash -a arch map dump kerntypes > > > > # new style parameter passing > > $>lcrash -m System.map -t Kerntypes -d dump -a arch > > > > # will use defaults /boot/System.map and /boot/Kerntypes with > > # dumpfile dump and specified dump architecture > > $>lcrash -d dump -a arch > > > > > > INSTALLATION steps for lcrash with cross arch support > > ===================================================== > > > > 1) install binutils src.rpm > > (e.g. rpm -i binutils...src.rpm && cd /usr/src/redhat/SPECS > > && rpm -bp binutils.spec) > > > > 2) install xlcrash source tree > > (e.g. from sourceforge cvs ...) > > > > 3) change to binutils src dir: > > > > $>./configure --prefix=/usr --exec-prefix=/usr --enable-64-bit-bfd \ > > > --enable-targets=i386-elf,s390-linux,s390x-linux,alpha-linux,ia64-elf > > > > 4) change to bfd dir: > > > > $>make > > > > 5) change to opcodes dir: > > > > $>make > > > > 6) Either install libbfd.a, bfd.h, symcat.h and libopcodes.a and > dis-asm.h > > using "make install" in steps 4) and 5) or copy the stuff into the > > lcrash > > source tree (e.g. libs into libklib/ and headers into > libklib/include). > > WARNING: > > If using "make install" to install the binutils stuff it would happen > > that > > bfd.h doesn't match libbfd.so on your system anymore, because if > > multiple > > targets are selected for libbfd it is only statically built. > > (I have done so without any harm to my system, but who knows? ;-) > > > > 7) change to lcrash source dir: > > > > $>./configure --enable-targets=all && make && make install > > > > > > Have fun! > > > > Andreas > > ------------------------------------------------------ > > > > -- > > Linux for eServer Development > > Tel : +49-7031-16-4640 > > Notes mail : Andreas Herrmann/GERMANY/IBM@IBMDE > > email : ahe...@de... > > > > > > > > > > ------------------------------------------------------- > > This sf.net email is sponsored by:ThinkGeek > > Stuff, things, and much much more. > > http://thinkgeek.com/sf > > _______________________________________________ > > Lkcd-general mailing list > > Lkc...@li... > > https://lists.sourceforge.net/lists/listinfo/lkcd-general > > > > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Stuff, things, and much much more. > http://thinkgeek.com/sf > _______________________________________________ > Lkcd-general mailing list > Lkc...@li... > https://lists.sourceforge.net/lists/listinfo/lkcd-general > > > > |