Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit 07bbc16a authored by Ingo Molnar's avatar Ingo Molnar
Browse files

Merge branch 'timers/urgent' into x86/xen 



Conflicts:
	arch/x86/kernel/process_32.c
	arch/x86/kernel/process_64.c

Manual merge:

	arch/x86/kernel/smpboot.c

Signed-off-by: default avatarIngo Molnar <mingo@elte.hu>
parents 6a9e9184 f8e256c6

.mailmap

+2 −0
Original line number Original line Diff line number Diff line
@@ -96,4 +96,6 @@ Tejun Heo <htejun@gmail.com> 
Thomas Graf <tgraf@suug.ch>

Thomas Graf <tgraf@suug.ch>

Tony Luck <tony.luck@intel.com>

Tony Luck <tony.luck@intel.com>

Tsuneo Yoshioka <Tsuneo.Yoshioka@f-secure.com>

Tsuneo Yoshioka <Tsuneo.Yoshioka@f-secure.com>

Uwe Kleine-König <Uwe.Kleine-Koenig@digi.com>

Uwe Kleine-König <ukleinek@informatik.uni-freiburg.de>

Valdis Kletnieks <Valdis.Kletnieks@vt.edu>
 
Valdis Kletnieks <Valdis.Kletnieks@vt.edu>

Documentation/ABI/testing/sysfs-gpio

0 → 100644
+26 −0
Original line number Original line Diff line number Diff line 
What:		/sys/class/gpio/

Date:		July 2008

KernelVersion:	2.6.27

Contact:	David Brownell <dbrownell@users.sourceforge.net>

Description:



  As a Kconfig option, individual GPIO signals may be accessed from

  userspace.  GPIOs are only made available to userspace by an explicit

  "export" operation.  If a given GPIO is not claimed for use by

  kernel code, it may be exported by userspace (and unexported later).

  Kernel code may export it for complete or partial access.



  GPIOs are identified as they are inside the kernel, using integers in

  the range 0..INT_MAX.  See Documentation/gpio.txt for more information.



    /sys/class/gpio

	/export ... asks the kernel to export a GPIO to userspace

	/unexport ... to return a GPIO to the kernel

	/gpioN ... for each exported GPIO #N

	    /value ... always readable, writes fail for input GPIOs

	    /direction ... r/w as: in, out (default low); write: high, low

	/gpiochipN ... for each gpiochip; #N is its first GPIO

	    /base ... (r/o) same as N

	    /label ... (r/o) descriptive, not necessarily unique

	    /ngpio ... (r/o) number of GPIOs; numbered N to N + (ngpio - 1)

Documentation/cpusets.txt

+10 −8
Original line number Original line Diff line number Diff line
@@ -635,14 +635,16 @@ prior 'mems' setting, will not be moved. 




There is an exception to the above.  If hotplug functionality is used

There is an exception to the above.  If hotplug functionality is used

to remove all the CPUs that are currently assigned to a cpuset,

to remove all the CPUs that are currently assigned to a cpuset,

then the kernel will automatically update the cpus_allowed of all

then all the tasks in that cpuset will be moved to the nearest ancestor

tasks attached to CPUs in that cpuset to allow all CPUs.  When memory

with non-empty cpus.  But the moving of some (or all) tasks might fail if

hotplug functionality for removing Memory Nodes is available, a

cpuset is bound with another cgroup subsystem which has some restrictions

similar exception is expected to apply there as well.  In general,

on task attaching.  In this failing case, those tasks will stay

the kernel prefers to violate cpuset placement, over starving a task

in the original cpuset, and the kernel will automatically update

that has had all its allowed CPUs or Memory Nodes taken offline.  User

their cpus_allowed to allow all online CPUs.  When memory hotplug

code should reconfigure cpusets to only refer to online CPUs and Memory

functionality for removing Memory Nodes is available, a similar exception

Nodes when using hotplug to add or remove such resources.

is expected to apply there as well.  In general, the kernel prefers to

violate cpuset placement, over starving a task that has had all

its allowed CPUs or Memory Nodes taken offline.





There is a second exception to the above.  GFP_ATOMIC requests are

There is a second exception to the above.  GFP_ATOMIC requests are

kernel internal allocations that must be satisfied, immediately.

kernel internal allocations that must be satisfied, immediately.

Documentation/feature-removal-schedule.txt

+8 −0
Original line number Original line Diff line number Diff line
@@ -322,3 +322,11 @@ Why: Accounting can now be enabled/disabled without kernel recompilation. 
      controlled by a kernel/module/sysfs/sysctl parameter.

      controlled by a kernel/module/sysfs/sysctl parameter.

Who:  Krzysztof Piotr Oledzki <ole@ans.pl>

Who:  Krzysztof Piotr Oledzki <ole@ans.pl>





---------------------------



What: ide-scsi (BLK_DEV_IDESCSI)

When: 2.6.29

Why:  The 2.6 kernel supports direct writing to ide CD drives, which

      eliminates the need for ide-scsi. The new method is more

      efficient in every way.

Who:  FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>

Documentation/filesystems/proc.txt

+2 −0
Original line number Original line Diff line number Diff line
@@ -2413,6 +2413,8 @@ The following 4 memory types are supported: 
  - (bit 1) anonymous shared memory

  - (bit 1) anonymous shared memory

  - (bit 2) file-backed private memory

  - (bit 2) file-backed private memory

  - (bit 3) file-backed shared memory

  - (bit 3) file-backed shared memory

  - (bit 4) ELF header pages in file-backed private memory areas (it is

            effective only if the bit 2 is cleared)





  Note that MMIO pages such as frame buffer are never dumped and vDSO pages

  Note that MMIO pages such as frame buffer are never dumped and vDSO pages

  are always dumped regardless of the bitmask status.

  are always dumped regardless of the bitmask status.