Re: module-init-tools v3.6 released
On Thu, 2009-02-05 at 11:56 +0100, Phil Knirsch wrote: Jon Masters wrote: This works fine, but means that, if we upgrade module-init-tools and there is a binary format change, then the system will be slow booting before depmod has been re-run again. I'm thinking about just doing a depmod -a on upgrade in such cases in the future...is there a problem with that idea? Imho in case of an update of module-init-tools that sounds absolutely reasonable. Users are much more likely to reboot their machines then get updates for module-init-tools, so the little overhead introduced with running depmod -a during an update should in general be significantly lower than the gains in subsequent bootups. Interestingly, I was expecting a lot more oh nos! Don't do that because it breaks some weirdly random preconceived notion but for once, nothing. Cool. Jon. ___ Fedora-kernel-list mailing list Fedora-kernel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-kernel-list
Re: module-init-tools v3.6 released
Jon Masters (j...@redhat.com) said: This works fine, but means that, if we upgrade module-init-tools and there is a binary format change, then the system will be slow booting before depmod has been re-run again. I'm thinking about just doing a depmod -a on upgrade in such cases in the future...is there a problem with that idea? Given the (presumable) infreqeuency of file format updates, especially compared to kernel updates, I wouldn't necessarily bother with it. Bill ___ Fedora-kernel-list mailing list Fedora-kernel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-kernel-list
Re: module-init-tools v3.6 released
On Thu, 2009-02-05 at 09:52 -0500, Bill Nottingham wrote: Jon Masters (j...@redhat.com) said: This works fine, but means that, if we upgrade module-init-tools and there is a binary format change, then the system will be slow booting before depmod has been re-run again. I'm thinking about just doing a depmod -a on upgrade in such cases in the future...is there a problem with that idea? Given the (presumable) infreqeuency of file format updates, especially compared to kernel updates, I wouldn't necessarily bother with it. Neither would I, but the difference in boot time is fairly dramatic and people might whine ;) Jon. ___ Fedora-kernel-list mailing list Fedora-kernel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-kernel-list
Re: module-init-tools v3.6 released
Jon Masters wrote: On Wed, 2009-02-04 at 18:19 -0500, Jon Masters wrote: On Wed, 2009-02-04 at 03:47 -0500, Jon Masters wrote: I'm considering pushing an update to F-9 since v3.5+ is so much faster than previous releases - and it impacts boot time, but I have to admit that I was more concerned about F10 and rawhide until now. Oh, there's a slight issue with the handling of modules.order still for the binary tries in newer module-init-tools. This might manifest in a switch of e.g. module used in initrd for storage devices with multiple modaliases. So...one question... We now have binary versions of files like modules.dep, modules.alias and modules.symbols. These end in .bin and *augment* but do not replace the textual versions of these files. If we find the binary files, we are *much* faster at loading modules - boot overhead is e.g. under one second. But we need to be able to make changes to these binary files in order to add ordering support, and also just for the future. Our plan is to freeze the old text file format (the last change will be the one made recently in which modules.dep can now have relative paths to save space) and to fallback to it whenever the binary format changes and modprobe finds older binary files. This works fine, but means that, if we upgrade module-init-tools and there is a binary format change, then the system will be slow booting before depmod has been re-run again. I'm thinking about just doing a depmod -a on upgrade in such cases in the future...is there a problem with that idea? Jon. Imho in case of an update of module-init-tools that sounds absolutely reasonable. Users are much more likely to reboot their machines then get updates for module-init-tools, so the little overhead introduced with running depmod -a during an update should in general be significantly lower than the gains in subsequent bootups. Jusy my $0.02. Regards, Phil -- Philipp Knirsch | Tel.: +49-711-96437-470 Team Lead Core Services | Fax.: +49-711-96437-111 Red Hat GmbH | Email: Phil Knirsch pknir...@redhat.com Hauptstaetterstr. 58 | Web: http://www.redhat.com/ D-70178 Stuttgart, Germany Motd: You're only jealous cos the little penguins are talking to me. ___ Fedora-kernel-list mailing list Fedora-kernel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-kernel-list
arch fun.
As per the discussion in #fedora-meeting today,
we're killing off kernel-i686, and just shipping..
* kernel.i586
* kernel-PAE.686
Patch below seems to dtrt.. comments?
Looking at the generated config files, the biggest difference
seems to be that kernel-PAE enables Xen and all it's related
dependancies.
Dave
Index: Makefile.config
===
RCS file: /cvs/pkgs/rpms/kernel/devel/Makefile.config,v
retrieving revision 1.69
diff -u -p -r1.69 Makefile.config
--- Makefile.config 26 Jan 2009 07:19:13 - 1.69
+++ Makefile.config 5 Feb 2009 20:09:20 -
@@ -6,7 +6,7 @@ CFG = kernel-$(VERSION)
CONFIGFILES= \
$(CFG)-i586.config \
- $(CFG)-i686.config $(CFG)-i686-PAE.config \
+ $(CFG)-i686-PAE.config \
$(CFG)-i686-debug.config $(CFG)-i686-PAEdebug.config \
$(CFG)-x86_64.config $(CFG)-x86_64-debug.config \
$(CFG)-s390x.config $(CFG)-arm.config \
@@ -63,9 +63,6 @@ temp-s390-generic: config-s390x temp-gen
temp-ia64-generic: config-ia64-generic temp-generic
perl merge.pl $^ $@
-kernel-$(VERSION)-i686.config: config-i686 temp-x86-generic
- perl merge.pl $^ i386 $@
-
kernel-$(VERSION)-i686-debug.config: config-i686 temp-x86-debug-generic
perl merge.pl $^ i386 $@
Index: config-i586
===
RCS file: /cvs/pkgs/rpms/kernel/devel/config-i586,v
retrieving revision 1.5
diff -u -p -r1.5 config-i586
--- config-i586 14 Feb 2008 19:56:06 - 1.5
+++ config-i586 5 Feb 2009 20:09:20 -
@@ -6,4 +6,3 @@ CONFIG_HIGHMEM4G=y
CONFIG_X86_POWERNOW_K6=m
-# CONFIG_KVM is not set
Index: config-i686
===
RCS file: config-i686
diff -N config-i686
--- config-i686 12 Jul 2007 19:15:37 - 1.1
+++ /dev/null 1 Jan 1970 00:00:00 -
@@ -1,8 +0,0 @@
-CONFIG_M686=y
-# CONFIG_NOHIGHMEM is not set
-CONFIG_HIGHMEM4G=y
-# CONFIG_HIGHMEM64G is not set
-
-CONFIG_CRYPTO_DEV_PADLOCK=m
-CONFIG_CRYPTO_DEV_PADLOCK_AES=m
-CONFIG_CRYPTO_DEV_PADLOCK_SHA=m
Index: config-x86-generic
===
RCS file: /cvs/pkgs/rpms/kernel/devel/config-x86-generic,v
retrieving revision 1.63
diff -u -p -r1.63 config-x86-generic
--- config-x86-generic 30 Jan 2009 00:08:01 - 1.63
+++ config-x86-generic 5 Feb 2009 20:09:20 -
@@ -205,9 +205,9 @@ CONFIG_NVRAM=y
CONFIG_IBM_ASM=m
CONFIG_CRYPTO_AES_586=m
CONFIG_CRYPTO_TWOFISH_586=m
-# CONFIG_CRYPTO_DEV_PADLOCK is not set
-# CONFIG_CRYPTO_DEV_PADLOCK_AES is not set
-# CONFIG_CRYPTO_DEV_PADLOCK_SHA is not set
+CONFIG_CRYPTO_DEV_PADLOCK=m
+CONFIG_CRYPTO_DEV_PADLOCK_AES=m
+CONFIG_CRYPTO_DEV_PADLOCK_SHA=m
CONFIG_GENERIC_ISA_DMA=y
CONFIG_SCHED_SMT=y
Index: kernel.spec
===
RCS file: /cvs/pkgs/rpms/kernel/devel/kernel.spec,v
retrieving revision 1.1263
diff -u -p -r1.1263 kernel.spec
--- kernel.spec 5 Feb 2009 18:55:52 - 1.1263
+++ kernel.spec 5 Feb 2009 20:09:20 -
@@ -241,6 +241,11 @@ Summary: The Linux kernel
%define with_kdump 0
#endif
+# We only build -PAE for 686 as of Fedora 11.
+%ifarch i686
+%define with_up 0
+%endif
+
# don't do debug builds on anything but i686 and x86_64
%ifnarch i686 x86_64
%define with_debug 0
@@ -522,8 +527,7 @@ Source24: config-rhel-generic
Source30: config-x86-generic
Source31: config-i586
-Source32: config-i686
-Source33: config-i686-PAE
+Source32: config-i686-PAE
Source40: config-x86_64-generic
@@ -1477,7 +1481,9 @@ mkdir -p $RPM_BUILD_ROOT/boot
cd linux-%{kversion}.%{_target_cpu}
%if %{with_debug}
+%ifnarch i686
BuildKernel %make_target %kernel_image debug
+%endif
%if %{with_pae}
BuildKernel %make_target %kernel_image PAEdebug
%endif
--
http://www.codemonkey.org.uk
___
Fedora-kernel-list mailing list
Fedora-kernel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-kernel-list
Re: arch fun.
Dave Jones wrote: As per the discussion in #fedora-meeting today, we're killing off kernel-i686, and just shipping.. * kernel.i586 * kernel-PAE.686 Patch below seems to dtrt.. comments? Two quick questions Dave. 1. This is for F11? 2. Will we eventually rename kernel-PAE.686 to kernel.686? P. ___ Fedora-kernel-list mailing list Fedora-kernel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-kernel-list
Re: arch fun.
Patch below seems to dtrt.. comments?
Why kill the configs, instead of just changing the spec settings?
@@ -1477,7 +1481,9 @@ mkdir -p $RPM_BUILD_ROOT/boot
cd linux-%{kversion}.%{_target_cpu}
%if %{with_debug}
+%ifnarch i686
BuildKernel %make_target %kernel_image debug
+%endif
%if %{with_pae}
BuildKernel %make_target %kernel_image PAEdebug
%endif
Why not %if !%{with_up} here?
___
Fedora-kernel-list mailing list
Fedora-kernel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-kernel-list
Re: arch fun.
On Thu, Feb 05, 2009 at 03:11:40PM -0500, Dave Jones wrote: As per the discussion in #fedora-meeting today, we're killing off kernel-i686, and just shipping.. * kernel.i586 * kernel-PAE.686 Patch below seems to dtrt.. comments? Looking at the generated config files, the biggest difference seems to be that kernel-PAE enables Xen and all it's related dependancies. Better version of the Makefile.config with changes Josh pointed out.. Dave Index: Makefile.config === RCS file: /cvs/pkgs/rpms/kernel/devel/Makefile.config,v retrieving revision 1.69 diff -u -p -r1.69 Makefile.config --- Makefile.config 26 Jan 2009 07:19:13 - 1.69 +++ Makefile.config 5 Feb 2009 20:27:40 - @@ -5,9 +5,8 @@ CFG= kernel-$(VERSION) CONFIGFILES= \ - $(CFG)-i586.config \ - $(CFG)-i686.config $(CFG)-i686-PAE.config \ - $(CFG)-i686-debug.config $(CFG)-i686-PAEdebug.config \ + $(CFG)-i586.config $(CFG)-i586-debug.config \ + $(CFG)-i686-PAE.config $(CFG)-i686-PAEdebug.config \ $(CFG)-x86_64.config $(CFG)-x86_64-debug.config \ $(CFG)-s390x.config $(CFG)-arm.config \ $(CFG)-ppc.config $(CFG)-ppc-smp.config \ @@ -63,12 +62,6 @@ temp-s390-generic: config-s390x temp-gen temp-ia64-generic: config-ia64-generic temp-generic perl merge.pl $^ $@ -kernel-$(VERSION)-i686.config: config-i686 temp-x86-generic - perl merge.pl $^ i386 $@ - -kernel-$(VERSION)-i686-debug.config: config-i686 temp-x86-debug-generic - perl merge.pl $^ i386 $@ - kernel-$(VERSION)-i686-PAE.config: config-i686-PAE temp-x86-generic perl merge.pl $^ i386 $@ @@ -78,6 +71,9 @@ kernel-$(VERSION)-i686-PAEdebug.config: kernel-$(VERSION)-i586.config: config-i586 temp-x86-generic perl merge.pl $^ i386 $@ +kernel-$(VERSION)-i586-debug.config: config-i586 temp-x86-debug-generic + perl merge.pl $^ i386 $@ + kernel-$(VERSION)-x86_64.config: /dev/null temp-x86_64-generic perl merge.pl $^ x86_64 $@ -- http://www.codemonkey.org.uk ___ Fedora-kernel-list mailing list Fedora-kernel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-kernel-list
Re: arch fun.
On Thu, Feb 05, 2009 at 03:22:55PM -0500, Prarit Bhargava wrote: Two quick questions Dave. 1. This is for F11? yes 2. Will we eventually rename kernel-PAE.686 to kernel.686? I don't think we can, otherwise someone with non-PAE 686's who does an update will suddenly find themselves unable to boot. Dave -- http://www.codemonkey.org.uk ___ Fedora-kernel-list mailing list Fedora-kernel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-kernel-list
Re: arch fun.
On Thu, Feb 05, 2009 at 12:23:07PM -0800, Roland McGrath wrote:
Patch below seems to dtrt.. comments?
Why kill the configs, instead of just changing the spec settings?
@@ -1477,7 +1481,9 @@ mkdir -p $RPM_BUILD_ROOT/boot
cd linux-%{kversion}.%{_target_cpu}
%if %{with_debug}
+%ifnarch i686
BuildKernel %make_target %kernel_image debug
+%endif
%if %{with_pae}
BuildKernel %make_target %kernel_image PAEdebug
%endif
Why not %if !%{with_up} here?
that works too.
Dave
--
http://www.codemonkey.org.uk
___
Fedora-kernel-list mailing list
Fedora-kernel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-kernel-list
Re: arch fun.
On Thu, 2009-02-05 at 15:11 -0500, Dave Jones wrote:
As per the discussion in #fedora-meeting today,
we're killing off kernel-i686, and just shipping..
* kernel.i586
* kernel-PAE.686
Patch below seems to dtrt.. comments?
This should prove interesting for GEM, as Intel still haven't resolved
GEM on PAE.
However I'm quite happy for this change to happen, Arjan want to try and
fix this or no GEM/KMS for F11.
Dave.
Looking at the generated config files, the biggest difference
seems to be that kernel-PAE enables Xen and all it's related
dependancies.
Dave
Index: Makefile.config
===
RCS file: /cvs/pkgs/rpms/kernel/devel/Makefile.config,v
retrieving revision 1.69
diff -u -p -r1.69 Makefile.config
--- Makefile.config 26 Jan 2009 07:19:13 - 1.69
+++ Makefile.config 5 Feb 2009 20:09:20 -
@@ -6,7 +6,7 @@ CFG = kernel-$(VERSION)
CONFIGFILES = \
$(CFG)-i586.config \
- $(CFG)-i686.config $(CFG)-i686-PAE.config \
+ $(CFG)-i686-PAE.config \
$(CFG)-i686-debug.config $(CFG)-i686-PAEdebug.config \
$(CFG)-x86_64.config $(CFG)-x86_64-debug.config \
$(CFG)-s390x.config $(CFG)-arm.config \
@@ -63,9 +63,6 @@ temp-s390-generic: config-s390x temp-gen
temp-ia64-generic: config-ia64-generic temp-generic
perl merge.pl $^ $@
-kernel-$(VERSION)-i686.config: config-i686 temp-x86-generic
- perl merge.pl $^ i386 $@
-
kernel-$(VERSION)-i686-debug.config: config-i686 temp-x86-debug-generic
perl merge.pl $^ i386 $@
Index: config-i586
===
RCS file: /cvs/pkgs/rpms/kernel/devel/config-i586,v
retrieving revision 1.5
diff -u -p -r1.5 config-i586
--- config-i586 14 Feb 2008 19:56:06 - 1.5
+++ config-i586 5 Feb 2009 20:09:20 -
@@ -6,4 +6,3 @@ CONFIG_HIGHMEM4G=y
CONFIG_X86_POWERNOW_K6=m
-# CONFIG_KVM is not set
Index: config-i686
===
RCS file: config-i686
diff -N config-i686
--- config-i686 12 Jul 2007 19:15:37 - 1.1
+++ /dev/null 1 Jan 1970 00:00:00 -
@@ -1,8 +0,0 @@
-CONFIG_M686=y
-# CONFIG_NOHIGHMEM is not set
-CONFIG_HIGHMEM4G=y
-# CONFIG_HIGHMEM64G is not set
-
-CONFIG_CRYPTO_DEV_PADLOCK=m
-CONFIG_CRYPTO_DEV_PADLOCK_AES=m
-CONFIG_CRYPTO_DEV_PADLOCK_SHA=m
Index: config-x86-generic
===
RCS file: /cvs/pkgs/rpms/kernel/devel/config-x86-generic,v
retrieving revision 1.63
diff -u -p -r1.63 config-x86-generic
--- config-x86-generic30 Jan 2009 00:08:01 - 1.63
+++ config-x86-generic5 Feb 2009 20:09:20 -
@@ -205,9 +205,9 @@ CONFIG_NVRAM=y
CONFIG_IBM_ASM=m
CONFIG_CRYPTO_AES_586=m
CONFIG_CRYPTO_TWOFISH_586=m
-# CONFIG_CRYPTO_DEV_PADLOCK is not set
-# CONFIG_CRYPTO_DEV_PADLOCK_AES is not set
-# CONFIG_CRYPTO_DEV_PADLOCK_SHA is not set
+CONFIG_CRYPTO_DEV_PADLOCK=m
+CONFIG_CRYPTO_DEV_PADLOCK_AES=m
+CONFIG_CRYPTO_DEV_PADLOCK_SHA=m
CONFIG_GENERIC_ISA_DMA=y
CONFIG_SCHED_SMT=y
Index: kernel.spec
===
RCS file: /cvs/pkgs/rpms/kernel/devel/kernel.spec,v
retrieving revision 1.1263
diff -u -p -r1.1263 kernel.spec
--- kernel.spec 5 Feb 2009 18:55:52 - 1.1263
+++ kernel.spec 5 Feb 2009 20:09:20 -
@@ -241,6 +241,11 @@ Summary: The Linux kernel
%define with_kdump 0
#endif
+# We only build -PAE for 686 as of Fedora 11.
+%ifarch i686
+%define with_up 0
+%endif
+
# don't do debug builds on anything but i686 and x86_64
%ifnarch i686 x86_64
%define with_debug 0
@@ -522,8 +527,7 @@ Source24: config-rhel-generic
Source30: config-x86-generic
Source31: config-i586
-Source32: config-i686
-Source33: config-i686-PAE
+Source32: config-i686-PAE
Source40: config-x86_64-generic
@@ -1477,7 +1481,9 @@ mkdir -p $RPM_BUILD_ROOT/boot
cd linux-%{kversion}.%{_target_cpu}
%if %{with_debug}
+%ifnarch i686
BuildKernel %make_target %kernel_image debug
+%endif
%if %{with_pae}
BuildKernel %make_target %kernel_image PAEdebug
%endif
___
Fedora-kernel-list mailing list
Fedora-kernel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-kernel-list
Re: Rawhide kernel options not enabled?
On Wed, 4 Feb 2009, Roland McGrath wrote: Or you could take my advice of many moons ago now and find less cockamamy ways to implement this. ;-) By what? Rewriting gcc? Only a wee little bit. ;-) Seriously, -pg is eight kinds of wrong, and not even what you really want anyway. (If your probe points are at actual entry points instead of inside prologues, then you can get the function arguments directly, assuming you know which calling convention that particular function has, which you don't really but you'd probably be happy pretending you did.) kprobes are quite expensive on the tracer to trace every function. You do not really need any kind of magical list of spots generated at compile time. You can just do insertion anywhere it works. (If you're willing to fall back to kprobes, it works most anywhere.) You can keep it real primitive like now and just only work where there is exactly NOP5 sitting there. Then all you're really asking for at build time is to insert a gratuitous NOP5 at entry points. A compiler tweak for that is a pretty simple kludge, not even tied in to actual code generation magic. You could probably even do it with crazy-ass asm/.o fiddling as is your wont. Hacking gcc is not an option. What? Are we to wait till this hack in gcc comes out to be able to do this. Not to mention, dynamic ftrace runs on x86, powerpc, arm, and I think even superH. With more archs probably to come. Each has their own crap to deal with. The gcc for each arch will need to handle the jumps needed for modules, which on other archs is no easy task. -- Steve ___ Fedora-kernel-list mailing list Fedora-kernel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-kernel-list
Re: Rawhide kernel options not enabled?
Steven Rostedt rostedt-nx8x9ylhiw1afugrpc6...@public.gmane.org writes: [...] But with this on, you can enable kernel function tracing at runtime. And this is a very powerful tool. This might be something to discuss, where we may sacrifice a bit of power for the ability of dynamic tracing. Right, but ... Benchmarks welcome ;-) Who should shoulder that burden of proof? - FChE ___ Fedora-kernel-list mailing list Fedora-kernel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-kernel-list
Re: arch fun.
On 05.02.2009 21:29, Dave Jones wrote: On Thu, Feb 05, 2009 at 03:22:55PM -0500, Prarit Bhargava wrote: 2. Will we eventually rename kernel-PAE.686 to kernel.686? I don't think we can, It'd be nice to get a definite answer from the anaconda/yum crowd. otherwise someone with non-PAE 686's who does an update will suddenly find themselves unable to boot. Well, that -PAE at the things for users of RPM Fusion a lot harder, because they are used to yum install kmod-foo to get the kernel-module foo installed; in the future they have to either use kmod-foo or kmod-foo-PAE depending on what kernel they use. Sure, that's not directly a Fedora problem. But it makes things more complicated for Fedora users. Which imho not only is the wrong direction -- it's wrose for the fame of Fedora, as people don't really differentiate between Fedora and add-on repos. That's why I'd be glad if we could get rid of the -PAE... CU knurd ___ Fedora-kernel-list mailing list Fedora-kernel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-kernel-list
