On Thu, 2012-02-16 at 15:16 -0600, Bruno Wolff III wrote: > On Thu, Feb 16, 2012 at 14:40:53 -0500, > David Malcolm <dmalc...@redhat.com> wrote: > > On Thu, 2012-02-16 at 12:06 -0500, Dave Jones wrote: > > > On Thu, Feb 16, 2012 at 10:44:45AM -0600, Mike Chambers wrote: > > > > Just seeing if it's just me, or we back to being slow again during > > > > testing with the debug options and the kernel? Am on a F16 kernel and > > > > is little better than F17 3.3 kernels. > > > > > > the first -rc build of each kernel release has debug turned off. > > > subsequent builds reenable it. > > > > Is it possible to directly observe whether or not debugging is turned on > > at runtime e.g. via some magic value in /proc or /sys ? > > If you look at the koji build information, the package list is different for > release builds and debug builds.
My question was about "at runtime": my thinking was that it's useful to spell out to the user that they shouldn't expect the final released performance from the current system, perhaps adding a message somewhere in the UI, so that certain websites who shall remain nameless don't try to benchmark the debug builds. But I just had another variant of this idea: could the string "debug" be embedded in the release string of the kernel? (and wire this up in the specfile so that it's automatically added) so e.g. kernel-3.3.0-0.rc3.git6.2.fc18 would become: kernel-3.3.0-0.rc3.git6.2.debug.fc18 or kernel-3.3.0-0.rc3.git6.2.fc18.debug That way it'd show up everywhere e.g. in uname -a, in gnome-system-monitor, on logon, etc, and make it obvious that the debug code is enabled. Not sure if this is a good idea or not Dave -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
