Hello community,
here is the log from the commit of package kernel-source for openSUSE:Factory checked in at 2012-05-26 13:09:06
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/kernel-source (Old)
and /work/SRC/openSUSE:Factory/.kernel-source.new (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Package is "kernel-source", Maintainer is "kernel-maintainers@forge.provo.novell.com"
Changes:
--------
--- /work/SRC/openSUSE:Factory/kernel-source/kernel-debug.changes 2012-05-23 09:21:58.000000000 +0200
+++ /work/SRC/openSUSE:Factory/.kernel-source.new/kernel-debug.changes 2012-05-26 13:09:11.000000000 +0200
@@ -1,0 +2,15 @@
+Wed May 23 15:59:25 CEST 2012 - jbeulich@novell.com
+
+- Update Xen patches to 3.4-final and c/s 1177.
+- commit a3c5f2c
+
+-------------------------------------------------------------------
+Tue May 22 14:21:24 CEST 2012 - trenn@suse.de
+
+- X86 acpi_cpufreq: Do not use request_module for autoloading
+ (bnc#756085).
+- Refresh patches.xen/xen3-auto-common.diff.
+- patches.xen/xen3-patch-3.3:
+- commit caf270e
+
+-------------------------------------------------------------------
kernel-default.changes: same change
kernel-desktop.changes: same change
kernel-docs.changes: same change
kernel-ec2.changes: same change
kernel-imx51.changes: same change
kernel-omap2plus.changes: same change
kernel-pae.changes: same change
kernel-ppc64.changes: same change
kernel-s390.changes: same change
kernel-source.changes: same change
kernel-syms.changes: same change
kernel-tegra.changes: same change
kernel-trace.changes: same change
kernel-u8500.changes: same change
kernel-vanilla.changes: same change
kernel-xen.changes: same change
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Other differences:
------------------
kernel-default.spec: same change
kernel-desktop.spec: same change
kernel-docs.spec: same change
kernel-ec2.spec: same change
kernel-imx51.spec: same change
kernel-omap2plus.spec: same change
kernel-pae.spec: same change
kernel-ppc64.spec: same change
kernel-s390.spec: same change
kernel-source.spec: same change
kernel-syms.spec: same change
kernel-tegra.spec: same change
kernel-trace.spec: same change
kernel-u8500.spec: same change
kernel-vanilla.spec: same change
kernel-xen.spec: same change
++++++ patches.drivers.tar.bz2 ++++++
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' '--exclude=.svnignore' old/patches.drivers/x86_acpi_cpufreq_autoload.patch new/patches.drivers/x86_acpi_cpufreq_autoload.patch
--- old/patches.drivers/x86_acpi_cpufreq_autoload.patch 1970-01-01 01:00:00.000000000 +0100
+++ new/patches.drivers/x86_acpi_cpufreq_autoload.patch 2012-05-22 14:21:24.000000000 +0200
@@ -0,0 +1,81 @@
+From: Thomas Renninger
+Subject: X86 acpi_cpufreq: Do not use request_module for autoloading
+Patch-Mainline: not yet, submitted
+References: bnc#756085
+
+The idea to check for needed cpufreq functions in ACPI processor object is
+a good (perfect) one, but using request_module in processor.ko
+has bad side-effects:
+It opens a hidden dependency: acpi-cpufreq.ko must be accessable when
+processor.ko is loaded (which is not the case if the latter gets loaded
+in initrd where the other one might not be present).
+Also I guess calling modprobe userspace from inside the kernel
+(comments indicate that is what happens), is considered an ugly workaround
+if nothing else works.
+
+Therefore try to load acpi-cpufreq on all CPUs with EST (Enhanced Speed Step)
+cpu feature flag.
+This may result in trying to load acpi-cpufreq on some machines which do
+not have cpufreq ACPI functions (which should be a BIOS bug then), but this
+does not hurt. acpi-cpufreq should always be the preferred cpufreq driver
+for EST capable CPUs.
+I am not 100% sure about VIA machines also exposing ACPI cpufreq functions.
+I could imagine they also have this CPU id feature set and everything is fine.
+In fact I have such a CPU at home, but trying it out is time intensive.
+As autoloading is a new feature, there cannot be regressions and if a non
+Intel CPU shows up that needs this driver as well, it can easily be added by
+another matching X86 model/family/feature line.
+
+References: https://bugzilla.novell.com/show_bug.cgi?id=756085
+
+Signed-off-by: Thomas Renninger
+Tested-by: tittiatcoke@gmail.com
+
+---
+ drivers/acpi/processor_driver.c | 1 -
+ drivers/cpufreq/acpi-cpufreq.c | 7 +++++++
+ include/acpi/processor.h | 1 -
+ 3 files changed, 7 insertions(+), 2 deletions(-)
+
+Index: linux-3.4-rc6-master/drivers/acpi/processor_driver.c
+===================================================================
+--- linux-3.4-rc6-master.orig/drivers/acpi/processor_driver.c
++++ linux-3.4-rc6-master/drivers/acpi/processor_driver.c
+@@ -474,7 +474,6 @@ static __ref int acpi_processor_start(st
+
+ #ifdef CONFIG_CPU_FREQ
+ acpi_processor_ppc_has_changed(pr, 0);
+- acpi_processor_load_module(pr);
+ #endif
+ acpi_processor_get_throttling_info(pr);
+ acpi_processor_get_limit_info(pr);
+Index: linux-3.4-rc6-master/include/acpi/processor.h
+===================================================================
+--- linux-3.4-rc6-master.orig/include/acpi/processor.h
++++ linux-3.4-rc6-master/include/acpi/processor.h
+@@ -225,7 +225,6 @@ struct acpi_processor_errata {
+ } piix4;
+ };
+
+-extern void acpi_processor_load_module(struct acpi_processor *pr);
+ extern int acpi_processor_preregister_performance(struct
+ acpi_processor_performance
+ __percpu *performance);
+Index: linux-3.4-rc6-master/drivers/cpufreq/acpi-cpufreq.c
+===================================================================
+--- linux-3.4-rc6-master.orig/drivers/cpufreq/acpi-cpufreq.c
++++ linux-3.4-rc6-master/drivers/cpufreq/acpi-cpufreq.c
+@@ -66,6 +66,13 @@ struct acpi_cpufreq_data {
+ unsigned int cpu_feature;
+ };
+
++static const struct x86_cpu_id acpi_cpufreq_ids[] = {
++ /* Enhanced Speed Step */
++ X86_FEATURE_MATCH(X86_FEATURE_EST),
++ {}
++};
++MODULE_DEVICE_TABLE(x86cpu, acpi_cpufreq_ids);
++
+ static DEFINE_PER_CPU(struct acpi_cpufreq_data *, acfreq_data);
+
+ /* acpi_perf_data is a pointer to percpu data. */
++++++ patches.xen.tar.bz2 ++++++
++++ 34161 lines of diff (skipped)
++++++ series.conf ++++++
--- /var/tmp/diff_new_pack.lSjpRm/_old 2012-05-26 13:09:18.000000000 +0200
+++ /var/tmp/diff_new_pack.lSjpRm/_new 2012-05-26 13:09:18.000000000 +0200
@@ -228,6 +228,7 @@
## cpuidle perf events cleanups and related
patches.arch/perf_timechart_fix_zero_timestamps.patch
+ patches.drivers/x86_acpi_cpufreq_autoload.patch
########################################################
# AGP, graphics related stuff
@@ -611,10 +612,7 @@
patches.xen/xen3-patch-3.1
patches.xen/xen3-patch-3.2
patches.xen/xen3-patch-3.3
- patches.xen/xen3-patch-3.4-rc3
- patches.xen/xen3-patch-3.4-rc4-rc5
- patches.xen/xen3-patch-3.4-rc5-rc6
- patches.xen/xen3-ia32-emulation-fix-build-problem-for-modular-ia32-a-out-support
+ patches.xen/xen3-patch-3.4
patches.xen/xen3-apei_allow_drivers_access_nvs_ram.patch
patches.xen/xen3-acpi_implement_overriding_of_arbitrary_acpi_tables_via_initrd.patch
patches.xen/xen3-stack-unwind
++++++ source-timestamp ++++++
--- /var/tmp/diff_new_pack.lSjpRm/_old 2012-05-26 13:09:18.000000000 +0200
+++ /var/tmp/diff_new_pack.lSjpRm/_new 2012-05-26 13:09:18.000000000 +0200
@@ -1,3 +1,3 @@
-2012-05-21 14:49:11 +0200
-GIT Revision: 91b2c6e7dedeaf80ebee53861f8eaadf972c40fe
+2012-05-23 15:59:25 +0200
+GIT Revision: a3c5f2c9fcea9aad9e12201c2700304d33469ace
GIT Branch: master
--
To unsubscribe, e-mail: opensuse-commit+unsubscribe@opensuse.org
For additional commands, e-mail: opensuse-commit+help@opensuse.org