[opensuse-kernel] HEAD rebased to 2.6.23.1
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all - I've just completed the rebase of the HEAD tree against 2.6.23.1. I removed around 180 patches that were backports from 2.6.23-rc or accepted upstream. Here are a few notes on the update: 1) OCFS2 Userspace Clustering is temporarily disabled. There was some rework of how heartbeat reference counting was handled that conflicts with the way my patches do it. I hope to have these updated this week. 2) Xen is temporarily disabled - but for a good reason. 2.6.23 saw the acceptance of Xen into mainline! The version in mainline is slightly different than our local patches, which causes some conflicts. One of the big issues is that the mainline version of Xen allows a whole lot more compile-time CONFIG_* options than ours did, so the config files need to be updated. When Xen is working again, uncomment the appropriate entries in config.conf to re-enable the build. 3) patches.arch/acpi_gpe_suspend_cleanup.patch is currently disabled. Alexey, when you get some free time, could you take a look at that one? If it's obsolete, just remove it. 4) I also merged 2.6.23-rt1, so the realtime kernels will build as well. Sven, since this is your playground, would you mind reviewing the HPET changes between patches.rt/patch-2.6.23-rt1 and patches.fixes/hpet_patches_45.patch? I expect that the ones in -rt are a newer version of the one in the hpet patch. If that's the case, I'd like to factor that out of the RT patch and replace the hpet patch with that code. The tree is now open for commits again. - -Jeff - -- Jeff Mahoney SUSE Labs -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFHEVQwLPWxlyuTD7IRAv5oAJ9nA1J2dBNZ1q5PLycWBC9VRPGKxwCgpS6C eT2gmIdtKqdl+FTf9E86k0o= =aSMn -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org
>>> Jeff Mahoney14.10.07 01:26 >>> >... >2) Xen is temporarily disabled - but for a good reason. 2.6.23 saw the >acceptance of Xen into mainline! The version in mainline is slightly >different than our local patches, which causes some conflicts. One of >the big issues is that the mainline version of Xen allows a whole lot >more compile-time CONFIG_* options than ours did, so the config files >need to be updated. When Xen is working again, uncomment the appropriate >entries in config.conf to re-enable the build. At least in the first step I'm likely not going to honor the mainline Xen bits - they don't really buy us much as long as they only support domUs. So after the first merge step, I expect things to be the same as we had them before for the -xen* flavors. We may then want/need to decide whether we want domU support leverage the paravirt ops bits, and utilize the -xen* kernels only for dom0 going forward. Jan -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Jan Beulich wrote: >>>> Jeff Mahoney14.10.07 01:26 >>> >> ... >> 2) Xen is temporarily disabled - but for a good reason. 2.6.23 saw the >> acceptance of Xen into mainline! The version in mainline is slightly >> different than our local patches, which causes some conflicts. One of >> the big issues is that the mainline version of Xen allows a whole lot >> more compile-time CONFIG_* options than ours did, so the config files >> need to be updated. When Xen is working again, uncomment the appropriate >> entries in config.conf to re-enable the build. > > At least in the first step I'm likely not going to honor the mainline Xen bits - > they don't really buy us much as long as they only support domUs. So after > the first merge step, I expect things to be the same as we had them before > for the -xen* flavors. We may then want/need to decide whether we want > domU support leverage the paravirt ops bits, and utilize the -xen* kernels > only for dom0 going forward. Huh, well that's pretty useless for us. What bits actually got merged? Only the arch support? I'm not seeing any of the Xen drivers in there either. - -Jeff - -- Jeff Mahoney SUSE Labs -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFHE4NCLPWxlyuTD7IRAoXEAJ4rCbHC+LKU4dnD3GD3NGHo3rGP6QCfcZvH d9xEjG9852SC+jBE4+Y6hHc= =09F7 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org
At least in the first step I'm likely not going to honor the mainline Xen bits - they don't really buy us much as long as they only support domUs. So after the first merge step, I expect things to be the same as we had them before for the -xen* flavors. We may then want/need to decide whether we want domU support leverage the paravirt ops bits, and utilize the -xen* kernels only for dom0 going forward.
Huh, well that's pretty useless for us. What bits actually got merged? Only the arch support? I'm not seeing any of the Xen drivers in there either.
DomU (i.e. unprivileged guest) support. There are (frontend) drivers in drivers/block/ and drivers/net/, but I'll probably rename kernel.org's CONFIG_XEN to something different, so that the symbol will retain its original (from our perspective) meaning, which will make these drivers not getting picked up for the -xen* flavors (i.e. they'll continue to use the drivers/xen/ tree). Jan -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org
participants (2)
-
Jan Beulich
-
Jeff Mahoney