Announce: kdb v2.0 is available for kernel 2.4.17
We must take care that the common KDB patch (kdb-v2.0-2.4.17-common-3)
conflicts with the IA64 patch on 2.4.17(linux-2.4.17-ia64-011226.diff). (needs to merge both patches). I did not notice that first time and got a strange KDB behavior ( kdb_init()
was not called, and no way to quit kdb after breaking into it ).
Signature · 8 lines
Sinceres salutations. _____________________________________________________________________ Xavier BRU BULL ISD/R&D/INTEL office: FREC B1-422 tel : +33 (0)4 76 29 77 45 http://www-frec.bull.fr fax : +33 (0)4 76 29 77 70 mailto:[email protected] addr: BULL, 1 rue de Provence, BP 208, 38432 Echirolles Cedex, FRANCE _____________________________________________________________________
Quoted 70 lines · Keith Owens
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1Content-Type: text/plain; charset=us-ascii
ftp://oss.sgi.com/projects/kdb/download/v2.0/
kdb-v2.0-2.4.17-common-1.bz2
kdb-v2.0-2.4.17-i386-1.bz2Starting with kdb v2.0 there is a common patch against each kernel which contains all the architecture independent code plus separate architecture dependent patches. Apply the common patch for your kernel plus at least one architecture dependent patch, the architecture patches activate kdb.
The naming convention for kdb patches is :-
vx.y The version of kdb. x.y is updated as new features are added to kdb.
- -v.p.s The kernel version that the patch applies to. 's' may include -pre, -rc or whatever numbering system the kernel keepers have thought up this week.
- -common The common kdb code. Everybody needs this.- -i386 Architecture dependent code for i386. - -ia64 Architecture dependent code for ia64, etc. - -n If there are multiple kdb patches against the same kernel version thenthe last number is incremented.
To build kdb for your kernel, apply the common kdb patch which is less than or equal to the kernel v.p.s, taking the highest value of '-n' if there is more than one. Apply the relevant arch dependent patch with the same value of 'vx.y-v.p.s-', taking the highest value of '-n' if there is more than one.
For example, to use kdb v2.0 for i386 on kernel 2.4.17, apply
kdb-v2.0-2.4.17-common-1
kdb-v2.0-2.4.17-i386-1
in that order.This release is functionally equivalent to kdb v1.9-2.4.16, the only change is the reorganisation. I have a backlog of kdb changes which were on hold until the patches had been split, it was getting too messy trying to maintain at least six versions of the common kdb code and keep them in sync. I hope to clear the backlog soon.
Ethan Solomita ([email protected]) has done a port of kdb to sparc64 against 2.4.13. I will upgrade that to 2.4.17 and issue kdb-v2.0-2.4.17-sparc64-1.bz2 "soon". kdb for ia64 has to wait until the 2.4.17-ia64 kernel patch is issued.
Changelog extract.
2001-12-22 Keith Owens <[email protected]>
* Upgrade to 2.4.17.
* Clean up ifdefCONFIG_KDB.
* Add ifdefCONFIG_KDBaround includekdb.h.
* Delete dummykdb.hfiles for unsupported architectures.
* Delete arch i386 and ia64 specific files. This changelog now applies to kdb common code only.
* Release as kdb v2.0-2.4.17-common-1.-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.4 (GNU/Linux)
Comment: Exmh version 2.1.1 10/15/1999iD8DBQE8JElbi4UHNye0ZOoRArPiAKCYlVUzS3EYrE5XC8sn3Xz8L9mBeQCeLHGn Wdx2YfBSiLgCmg6nlUPr+8A > ¿tm
-----END PGP SIGNATURE-----
Quoted 4 lines · Xavier Bru
We must take care that the common KDB patch (kdb-v2.0-2.4.17-common-3)
conflicts with the IA64 patch on 2.4.17(linux-2.4.17-ia64-011226.diff). (needs to merge both patches). I did not notice that first time and got a strange KDB behavior (kdb_init()
was not called, and no way to quit kdb after breaking into it ).
That is due to the ia64 patch adding CONFIG_PERMON patches into init/main.c. AFAICT there is no reason that this patch cannot be sent to Marcelo to reduce the footprint of the ia64 patch on common code.
David, can you send these ia64 patches to Marcelo for inclusion in base kernel? If you are too busy I will package them up and send them.
Documentation/Configure.help Documentation/kernel-parameters.txt init/main.c
Makefile (second chunk only, adding AFLAGS_KERNEL) include/linux/mm.h (just to reserve the bits) include/linux/prctl.h (reserve the bits) include/linux/time.h
kernel/ksyms.c
kernel/signal.c
kernel/sys.c
The list above excludes anything that might affect other architectures. The patch to ensure that the console variables are contiguous is already in 2.4.18-pre1.
I would like to get crc32 in base as well but I believe that another person has been working on this as well. If you like I will reconcile the two versions and get one crc32 into base kernel.
RE: [Linux-ia64] Re: Announce: kdb v2.0 is available for kernel 2
In reply to Xavier BruQuoted 3 lines
I would like to get crc32 in base as well but I believe that another person has been working on this as well. If you like I will reconcile the two versions and get one crc32 into base kernel.
Jeff Garzik and I have I've been unsuccessful in getting crc32 into the base kernels. Jeff sent the patch once, I've sent the patch repeatedly. Marcelo looked at it and said he wanted to see it in 2.5.x first. Linus has been silent.
http://domsch.com/linux/patches/crc32/2.5.2-pre7/ has the current implementation, broken into several smaller parts, and provided as one big patch too. Two additional drivers (de2140x.c and sis900.c) were modified *after* the patch set was created and are also there; the drivers/net/Makefile.lib needs to be touched to add those drivers to the list - I haven't done that yet.
Keith, if you can get it in, I'd be glad for it.
Bugger is, when 2.5.x does away with fs/partitions/*, my need for the crc32 function in the kernel to support GPT dies too. Progress I guess...
Thanks,
Matt
--
Matt Domsch
Sr. Software Engineer
Dell Linux Solutions www.dell.com/linux
#1 US Linux Server provider with 24.5% (IDC Dec 2001) #2 Worldwide Linux Server provider with 18.2% (IDC Dec 2001)
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line · Keith Owens
Keith> David, can you send these ia64 patches to Marcelo for Keith> inclusion in base kernel? If you are too busy I will package Keith> them up and send them.
That would be fine with me. But could you send me the patch for a final sanity check before sending it off to Marcelo?
Also, do not send it the linux/mm.h changes. Due to the multiple memory attribute issue, I'm not sure the VM_NONCACHED and VM_WRITECOMBINED are such good ideas (besides, I don't think they're really needed anymore).
Keith> Documentation/Configure.help
Keith> Documentation/kernel-parameters.txt init/main.c Makefile Keith> (second chunk only, adding AFLAGS_KERNEL) include/linux/mm.h Keith> (just to reserve the bits) include/linux/prctl.h (reserve the Keith> bits) include/linux/time.h kernel/ksyms.c kernel/signal.c Keith> kernel/sys.c
Keith> The list above excludes anything that might affect other Keith> architectures. The patch to ensure that the console Keith> variables are contiguous is already in 2.4.18-pre1.
Keith> I would like to get crc32 in base as well but I believe that Keith> another person has been working on this as well. If you like Keith> I will reconcile the two versions and get one crc32 into base Keith> kernel.
Matt was working on this. Is that who you were referring two? Yes, there is no reason this patch shouldn't be in 2.4.xx as far as I'm concerned.
Thanks,
--david
RE: [Linux-ia64] Re: Announce: kdb v2.0 is available for kernel 2
In reply to Xavier BruQuoted 2 lines
Jeff Garzik and I have I've been unsuccessful in getting crc32 into the base kernels.
Well, what do you know, Linus applied it for 2.5.2-pre12.
As for 2.4.x, I'll give it a week or so in 2.5.x to prove to Marcelo it's stable, and then re-submit there.
Thanks,
Matt
Signature · 5 lines
Matt Domsch Sr. Software Engineer Dell Linux Solutions www.dell.com/linux #1 US Linux Server provider with 24.5% (IDC Dec 2001) #2 Worldwide Linux Server provider with 18.5% (IDC Dec 2001)