Tags

This is the 3.0.98 stable release

Linux 3.12-rc3

ACPI and power management fixes for 3.12-rc3

 1) After recent locking changes in the cpufreq core it is possible
    to trigger BUG_ON(!policy) in lock_policy_rwsem_read() if
    cpufreq_get() is called before registering a cpufreq driver.
    Fix from Viresh Kumar.

 2) If intel_pstate has been loaded already, it doesn't make sense
    to do anything in acpi_cpufreq_init() and moreover doing something
    in there in that case may be harmful, so make that function return
    immediately if another cpufreq driver is already present.  From
    Yinghai Lu.

 3) The ACPI IPMI driver sometimes attempts to acquire a mutex from
    interrupt context, which can be avoided by replacing that mutex
    with a spinlock.  From Lv Zheng.

 4) A NULL pointer may be dereferenced by the exynos5440 cpufreq
    driver if a memory allocation made by it fails.  Fix from
    Sachin Kamat.

 5) Hanjun Guo's commit fixes a typo in the kerneldoc comment
    documenting acpi_bus_unregister_driver().

/

Small fbdev fixes for various fb drivers

This is the 3.11.2 stable release

This is the 3.10.13 stable release

This is the 3.4.63 stable release

This is the 3.0.97 stable release

Linux 3.12-rc2

ACPI and power management fixes for 3.12-rc2

 1) Four fixes for cpufreq regressions introduced by the changes that
    removed Device Tree parsing for CPU device nodes from cpufreq
    drivers from Sudeep KarkadaNagesha.

 2) Two fixes for recent cpufreq regressions introduced by changes
    related to the preservation of sysfs attributes over system
    suspend/resume cycles from Viresh Kumar.

 3) Fix for ACPI-based wakeup signaling in the PCI subsystem that
    fails to stop PME polling for devices put into the D3cold power
    state from Rafael J Wysocki.

 4) Fix for bad interactions between cpufreq and udev on systems
    supporting intel_pstate where acpi-cpufreq is available as well
    from Yinghai Lu.

/

Linux 3.12-rc1

This is the 3.11.1 stable release

This is the 3.10.12 stable release

This is the 3.4.62 stable release

This is the 3.0.96 stable release

The highlights of the release are nested EPT and pv-ticketlocks
support (hypervisor part; guest part, which is most of the code, goes
through tip tree).  Apart of that there are many fixes for all arches.

IOMMU Updates for Linux v3.12

This round the updates contain:

	* A new driver for the Freescale PAMU IOMMU from Varun Sethi.
	  This driver has cooked for a while and required changes to the
	  IOMMU-API and infrastructure that were already merged before.
	* Updates for the ARM-SMMU driver from Will Deacon
	* Various fixes, the most important one is probably a fix from
	  Alex Williamson for a memory leak in the VT-d page-table
	  freeing code

In summary not all that much. The biggest part in the diffstat is the
new PAMU driver.

ACPI and power management fixes for 3.12-rc1

 1) ACPI-based PCI hotplug (ACPIPHP) fixes related to spurious events

  After the recent ACPIPHP changes we've seen some interesting breakage
  on a system that triggers device check notifications during boot for
  non-existing devices.  Although those notifications are really
  spurious, we should be able to deal with them nevertheless and that
  shouldn't introduce too much overhead.  Four commits to make that
  work properly.

 2) Memory hotplug and hibernation mutual exclusion rework

  This was maent to be a cleanup, but it happens to fix a classical
  ABBA deadlock between system suspend/hibernation and ACPI memory
  hotplug which is possible if they are started roughly at the same
  time.  Three commits rework memory hotplug so that it doesn't
  acquire pm_mutex and make hibernation use device_hotplug_lock
  which prevents it from racing with memory hotplug.

 3) ACPI Intel LPSS (Low-Power Subsystem) driver crash fix

  The ACPI LPSS driver crashes during boot on Apple Macbook Air with
  Haswell that has slightly unusual BIOS configuration in which one
  of the LPSS device's _CRS method doesn't return all of the information
  expected by the driver.  Fix from Mika Westerberg, for stable.

 4) ACPICA fix related to Store->ArgX operation

  AML interpreter fix for obscure breakage that causes AML to be
  executed incorrectly on some machines (observed in practice).  From
  Bob Moore.

 5) ACPI core fix for PCI ACPI device objects lookup

  There still are cases in which there is more than one ACPI device
  object matching a given PCI device and we don't choose the one that
  the BIOS expects us to choose, so this makes the lookup take more
  criteria into account in those cases.

 6) Fix to prevent cpuidle from crashing in some rare cases

  If the result of cpuidle_get_driver() is NULL, which can happen on
  some systems, cpuidle_driver_ref() will crash trying to use that
  pointer and the Daniel Fu's fix prevents that from happening.

 7) cpufreq fixes related to CPU hotplug

  Stephen Boyd reported a number of concurrency problems with cpufreq
  related to CPU hotplug which are addressed by a series of fixes
  from Srivatsa S Bhat and Viresh Kumar.

 8) cpufreq fix for time conversion in time_in_state attribute

  Time conversion carried out by cpufreq when user space attempts to
  read /sys/devices/system/cpu/cpu*/cpufreq/stats/time_in_state won't
  work correcty if cputime_t doesn't map directly to jiffies.  Fix
  from Andreas Schwab.

 9) Revert of a troublesome cpufreq commit

  Commit 7c30ed5 (cpufreq: make sure frequency transitions are
  serialized) was intended to address some known concurrency problems
  in cpufreq related to the ordering of transitions, but unfortunately
  it introduced several problems of its own, so I decided to revert it
  now and address the original problems later in a more robust way.

10) Intel Haswell CPU models for intel_pstate from Nell Hardcastle.

11) cpufreq fixes related to system suspend/resume

  The recent cpufreq changes that made it preserve CPU sysfs attributes
  over suspend/resume cycles introduced a possible NULL pointer
  dereference that caused it to crash during the second attempt to
  suspend.  Three commits from Srivatsa S Bhat fix that problem and a
  couple of related issues.

12) cpufreq locking fix

  cpufreq_policy_restore() should acquire the lock for reading, but
  it acquires it for writing.  Fix from Lan Tianyu.

/

This is the 3.2.51 stable release

VFIO updates include safer default file flags for VFIO device fds,
an external user interface exported to allow other modules to hold
references to VFIO groups, a fix to test for extended config space
on PCIe and PCI-x, and new hot reset interfaces for PCI devices
which allows the user to do PCI bus/slot resets when all of the
devices affected by the reset are owned by the user.

For this last feature, the PCI bus reset interface, I depend on
changes already merged from Bjorn's PCI pull request.  I therefore
merged my tree up to commit cb3e433, which I think was the correct
action, but as Stephen Rothwell noted, I failed to provide a commit
message indicating why the merge was required.  Sorry for that.
Thanks,
Alex