Merge branch 'tracing/urgent' into tracing/core (9de09ace) · Commits · e / devices / android_kernel_fairphone_FP3

Documentation/ABI/testing/sysfs-bus-pci-devices-cciss

+28 −0

Original line number	Diff line number	Diff line
		@@ -31,3 +31,31 @@ Date: March 2009
		Kernel Version: 2.6.30
		Contact: iss_storagedev@hp.com
		Description: A symbolic link to /sys/block/cciss!cXdY

		Where: /sys/bus/pci/devices/<dev>/ccissX/rescan
		Date: August 2009
		Kernel Version: 2.6.31
		Contact: iss_storagedev@hp.com
		Description: Kicks of a rescan of the controller to discover logical
		drive topology changes.

		Where: /sys/bus/pci/devices/<dev>/ccissX/cXdY/lunid
		Date: August 2009
		Kernel Version: 2.6.31
		Contact: iss_storagedev@hp.com
		Description: Displays the 8-byte LUN ID used to address logical
		drive Y of controller X.

		Where: /sys/bus/pci/devices/<dev>/ccissX/cXdY/raid_level
		Date: August 2009
		Kernel Version: 2.6.31
		Contact: iss_storagedev@hp.com
		Description: Displays the RAID level of logical drive Y of
		controller X.

		Where: /sys/bus/pci/devices/<dev>/ccissX/cXdY/usage_count
		Date: August 2009
		Kernel Version: 2.6.31
		Contact: iss_storagedev@hp.com
		Description: Displays the usage count (number of opens) of logical drive Y
		of controller X.

Documentation/ABI/testing/sysfs-class-usb_host→Documentation/ABI/testing/sysfs-class-uwb_rc-wusbhc

+2 −2

Original line number	Diff line number	Diff line
		What: /sys/class/usb_host/usb_hostN/wusb_chid
		What: /sys/class/uwb_rc/uwbN/wusbhc/wusb_chid
		Date: July 2008
		KernelVersion: 2.6.27
		Contact: David Vrabel <david.vrabel@csr.com>
		@@ -9,7 +9,7 @@ Description:

		Set an all zero CHID to stop the host controller.

		What: /sys/class/usb_host/usb_hostN/wusb_trust_timeout
		What: /sys/class/uwb_rc/uwbN/wusbhc/wusb_trust_timeout
		Date: July 2008
		KernelVersion: 2.6.27
		Contact: David Vrabel <david.vrabel@csr.com>

Documentation/cgroups/cgroups.txt

+9 −2

Original line number	Diff line number	Diff line
		@@ -227,7 +227,14 @@ as the path relative to the root of the cgroup file system.
		Each cgroup is represented by a directory in the cgroup file system
		containing the following files describing that cgroup:

		- tasks: list of tasks (by pid) attached to that cgroup
		- tasks: list of tasks (by pid) attached to that cgroup. This list
		is not guaranteed to be sorted. Writing a thread id into this file
		moves the thread into this cgroup.
		- cgroup.procs: list of tgids in the cgroup. This list is not
		guaranteed to be sorted or free of duplicate tgids, and userspace
		should sort/uniquify the list if this property is required.
		Writing a tgid into this file moves all threads with that tgid into
		this cgroup.
		- notify_on_release flag: run the release agent on exit?
		- release_agent: the path to use for release notifications (this file
		exists in the top cgroup only)
		@@ -374,7 +381,7 @@ Now you want to do something with this cgroup.

		In this directory you can find several files:
		# ls
		notify_on_release tasks
		cgroup.procs notify_on_release tasks
		(plus whatever files added by the attached subsystems)

		Now attach your shell to this cgroup:

Documentation/debugging-via-ohci1394.txt

+4 −4

Original line number	Diff line number	Diff line
		@@ -64,14 +64,14 @@ be used to view the printk buffer of a remote machine, even with live update.

		Bernhard Kaindl enhanced firescope to support accessing 64-bit machines
		from 32-bit firescope and vice versa:
		- ftp://ftp.suse.de/private/bk/firewire/tools/firescope-0.2.2.tar.bz2
		- http://halobates.de/firewire/firescope-0.2.2.tar.bz2

		and he implemented fast system dump (alpha version - read README.txt):
		- ftp://ftp.suse.de/private/bk/firewire/tools/firedump-0.1.tar.bz2
		- http://halobates.de/firewire/firedump-0.1.tar.bz2

		There is also a gdb proxy for firewire which allows to use gdb to access
		data which can be referenced from symbols found by gdb in vmlinux:
		- ftp://ftp.suse.de/private/bk/firewire/tools/fireproxy-0.33.tar.bz2
		- http://halobates.de/firewire/fireproxy-0.33.tar.bz2

		The latest version of this gdb proxy (fireproxy-0.34) can communicate (not
		yet stable) with kgdb over an memory-based communication module (kgdbom).
		@@ -178,7 +178,7 @@ Step-by-step instructions for using firescope with early OHCI initialization:

		Notes
		-----
		Documentation and specifications: ftp://ftp.suse.de/private/bk/firewire/docs
		Documentation and specifications: http://halobates.de/firewire/

		FireWire is a trademark of Apple Inc. - for more information please refer to:
		http://en.wikipedia.org/wiki/FireWire

Documentation/feature-removal-schedule.txt

+38 −0

Original line number	Diff line number	Diff line
		@@ -418,6 +418,14 @@ When: 2.6.33
		Why: Should be implemented in userspace, policy daemon.
		Who: Johannes Berg <johannes@sipsolutions.net>

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

		What: CONFIG_INOTIFY
		When: 2.6.33
		Why: last user (audit) will be converted to the newer more generic
		and more easily maintained fsnotify subsystem
		Who: Eric Paris <eparis@redhat.com>

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

		What: lock_policy_rwsem_* and unlock_policy_rwsem_* will not be
		@@ -451,3 +459,33 @@ Why: OSS sound_core grabs all legacy minors (0-255) of SOUND_MAJOR
		will also allow making ALSA OSS emulation independent of
		sound_core. The dependency will be broken then too.
		Who: Tejun Heo <tj@kernel.org>

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

		What: Support for VMware's guest paravirtuliazation technique [VMI] will be
		dropped.
		When: 2.6.37 or earlier.
		Why: With the recent innovations in CPU hardware acceleration technologies
		from Intel and AMD, VMware ran a few experiments to compare these
		techniques to guest paravirtualization technique on VMware's platform.
		These hardware assisted virtualization techniques have outperformed the
		performance benefits provided by VMI in most of the workloads. VMware
		expects that these hardware features will be ubiquitous in a couple of
		years, as a result, VMware has started a phased retirement of this
		feature from the hypervisor. We will be removing this feature from the
		Kernel too. Right now we are targeting 2.6.37 but can retire earlier if
		technical reasons (read opportunity to remove major chunk of pvops)
		arise.

		Please note that VMI has always been an optimization and non-VMI kernels
		still work fine on VMware's platform.
		Latest versions of VMware's product which support VMI are,
		Workstation 7.0 and VSphere 4.0 on ESX side, future maintainence
		releases for these products will continue supporting VMI.

		For more details about VMI retirement take a look at this,
		http://blogs.vmware.com/guestosguide/2009/09/vmi-retirement.html

		Who: Alok N Kataria <akataria@vmware.com>

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