Automatic merge with /usr/src/ntfs-2.6.git. (2a322e4c) · Commits · e / devices / android_kernel_teracube_2e

Documentation/00-INDEX

+2 −0

Original line number	Diff line number	Diff line
		@@ -138,6 +138,8 @@ java.txt
		- info on the in-kernel binary support for Java(tm).
		kbuild/
		- directory with info about the kernel build process.
		kdumpt.txt
		- mini HowTo on getting the crash dump code to work.
		kernel-doc-nano-HOWTO.txt
		- mini HowTo on generation and location of kernel documentation files.
		kernel-docs.txt

Documentation/SubmittingPatches

+1 −16

Original line number	Diff line number	Diff line
		@@ -132,21 +132,6 @@ which require discussion or do not have a clear advantage should
		usually be sent first to linux-kernel. Only after the patch is
		discussed should the patch then be submitted to Linus.

		For small patches you may want to CC the Trivial Patch Monkey
		trivial@rustcorp.com.au set up by Rusty Russell; which collects "trivial"
		patches. Trivial patches must qualify for one of the following rules:
		Spelling fixes in documentation
		Spelling fixes which could break grep(1).
		Warning fixes (cluttering with useless warnings is bad)
		Compilation fixes (only if they are actually correct)
		Runtime fixes (only if they actually fix things)
		Removing use of deprecated functions/macros (eg. check_region).
		Contact detail and documentation fixes
		Non-portable code replaced by portable code (even in arch-specific,
		since people copy, as long as it's trivial)
		Any fix by the author/maintainer of the file. (ie. patch monkey
		in re-transmission mode)



		5) Select your CC (e-mail carbon copy) list.
		@@ -299,7 +284,7 @@ can certify the below:

		then you just add a line saying

		Signed-off-by: Random J Developer <random@developer.org>
		Signed-off-by: Random J Developer <random@developer.example.org>

		Some people also put extra tags at the end. They'll just be ignored for
		now, but you can do this to mark internal company procedures or just

Documentation/cdrom/sbpcd

+10 −6

Original line number	Diff line number	Diff line
		@@ -419,6 +419,7 @@ into the file "track01":
		*/
		#include <stdio.h>
		#include <sys/ioctl.h>
		#include <sys/types.h>
		#include <linux/cdrom.h>

		static struct cdrom_tochdr hdr;
		@@ -429,7 +430,7 @@ static int datafile, drive;
		static int i, j, limit, track, err;
		static char filename[32];

		main(int argc, char *argv[])
		int main(int argc, char *argv[])
		{
		/*
		* open /dev/cdrom
		@@ -516,6 +517,7 @@ entry[track+1].cdte_addr.lba=entry[track].cdte_addr.lba+300;
		}
		arg.addr.lba++;
		}
		return 0;
		}
		/===================== end program ========================================/

		@@ -564,15 +566,16 @@ Appendix -- the "cdtester" utility:
		#include <stdio.h>
		#include <malloc.h>
		#include <sys/ioctl.h>
		#include <sys/types.h>
		#include <linux/cdrom.h>

		#ifdef AZT_PRIVATE_IOCTLS
		#include <linux/../../drivers/cdrom/aztcd.h>
		#endif AZT_PRIVATE_IOCTLS
		#endif /* AZT_PRIVATE_IOCTLS */
		#ifdef SBP_PRIVATE_IOCTLS
		#include <linux/../../drivers/cdrom/sbpcd.h>
		#include <linux/fs.h>
		#endif SBP_PRIVATE_IOCTLS
		#endif /* SBP_PRIVATE_IOCTLS */

		struct cdrom_tochdr hdr;
		struct cdrom_tochdr tocHdr;
		@@ -590,7 +593,7 @@ union
		struct cdrom_msf msf;
		unsigned char buf[CD_FRAMESIZE_RAW];
		} azt;
		#endif AZT_PRIVATE_IOCTLS
		#endif /* AZT_PRIVATE_IOCTLS */
		int i, i1, i2, i3, j, k;
		unsigned char sequence=0;
		unsigned char command[80];
		@@ -738,7 +741,7 @@ void display(int size,unsigned char *buffer)
		}
		}

		main(int argc, char *argv[])
		int main(int argc, char *argv[])
		{
		printf("\nTesting tool for a CDROM driver's audio functions V0.1\n");
		printf("(C) 1995 Eberhard Moenkeberg <emoenke@gwdg.de>\n");
		@@ -1046,12 +1049,13 @@ main(int argc, char *argv[])
		rc=ioctl(drive,CDROMAUDIOBUFSIZ,j);
		printf("%d frames granted.\n",rc);
		break;
		#endif SBP_PRIVATE_IOCTLS
		#endif /* SBP_PRIVATE_IOCTLS */
		default:
		printf("unknown command: \"%s\".\n",command);
		break;
		}
		}
		return 0;
		}
		/==========================================================================/

Documentation/cpu-freq/governors.txt

+12 −2

Original line number	Diff line number	Diff line
		@@ -9,6 +9,7 @@


		Dominik Brodowski <linux@brodo.de>
		some additions and corrections by Nico Golde <nico@ngolde.de>



		@@ -25,6 +26,7 @@ Contents:
		2.1 Performance
		2.2 Powersave
		2.3 Userspace
		2.4 Ondemand

		3. The Governor Interface in the CPUfreq Core

		@@ -86,7 +88,7 @@ highest frequency within the borders of scaling_min_freq and
		scaling_max_freq.


		2.1 Powersave
		2.2 Powersave
		-------------

		The CPUfreq governor "powersave" sets the CPU statically to the
		@@ -94,7 +96,7 @@ lowest frequency within the borders of scaling_min_freq and
		scaling_max_freq.


		2.2 Userspace
		2.3 Userspace
		-------------

		The CPUfreq governor "userspace" allows the user, or any userspace
		@@ -103,6 +105,14 @@ by making a sysfs file "scaling_setspeed" available in the CPU-device
		directory.


		2.4 Ondemand
		------------

		The CPUfreq govenor "ondemand" sets the CPU depending on the
		current usage. To do this the CPU must have the capability to
		switch the frequency very fast.



		3. The Governor Interface in the CPUfreq Core
		=============================================

Documentation/cpusets.txt

+16 −0

Original line number	Diff line number	Diff line
		@@ -51,6 +51,14 @@ mems_allowed vector.

		If a cpuset is cpu or mem exclusive, no other cpuset, other than a direct
		ancestor or descendent, may share any of the same CPUs or Memory Nodes.
		A cpuset that is cpu exclusive has a sched domain associated with it.
		The sched domain consists of all cpus in the current cpuset that are not
		part of any exclusive child cpusets.
		This ensures that the scheduler load balacing code only balances
		against the cpus that are in the sched domain as defined above and not
		all of the cpus in the system. This removes any overhead due to
		load balancing code trying to pull tasks outside of the cpu exclusive
		cpuset only to be prevented by the tasks' cpus_allowed mask.

		User level code may create and destroy cpusets by name in the cpuset
		virtual file system, manage the attributes and permissions of these
		@@ -84,6 +92,9 @@ This can be especially valuable on:
		and a database), or
		* NUMA systems running large HPC applications with demanding
		performance characteristics.
		* Also cpu_exclusive cpusets are useful for servers running orthogonal
		workloads such as RT applications requiring low latency and HPC
		applications that are throughput sensitive

		These subsets, or "soft partitions" must be able to be dynamically
		adjusted, as the job mix changes, without impacting other concurrently
		@@ -125,6 +136,8 @@ Cpusets extends these two mechanisms as follows:
		- A cpuset may be marked exclusive, which ensures that no other
		cpuset (except direct ancestors and descendents) may contain
		any overlapping CPUs or Memory Nodes.
		Also a cpu_exclusive cpuset would be associated with a sched
		domain.
		- You can list all the tasks (by pid) attached to any cpuset.

		The implementation of cpusets requires a few, simple hooks
		@@ -136,6 +149,9 @@ into the rest of the kernel, none in performance critical paths:
		allowed in that tasks cpuset.
		- in sched.c migrate_all_tasks(), to keep migrating tasks within
		the CPUs allowed by their cpuset, if possible.
		- in sched.c, a new API partition_sched_domains for handling
		sched domain changes associated with cpu_exclusive cpusets
		and related changes in both sched.c and arch/ia64/kernel/domain.c
		- in the mbind and set_mempolicy system calls, to mask the requested
		Memory Nodes by what's allowed in that tasks cpuset.
		- in page_alloc, to restrict memory to allowed nodes.