Merge remote branch 'airlied/drm-fixes' into drm-intel-fixes (1bb95834) · Commits · e / devices / android_kernel_xiaomi_markw

Documentation/ABI/obsolete/proc-pid-oom_adj

0 → 100644

+22 −0

Original line number	Diff line number	Diff line
		What: /proc/<pid>/oom_adj
		When: August 2012
		Why: /proc/<pid>/oom_adj allows userspace to influence the oom killer's
		badness heuristic used to determine which task to kill when the kernel
		is out of memory.

		The badness heuristic has since been rewritten since the introduction of
		this tunable such that its meaning is deprecated. The value was
		implemented as a bitshift on a score generated by the badness()
		function that did not have any precise units of measure. With the
		rewrite, the score is given as a proportion of available memory to the
		task allocating pages, so using a bitshift which grows the score
		exponentially is, thus, impossible to tune with fine granularity.

		A much more powerful interface, /proc/<pid>/oom_score_adj, was
		introduced with the oom killer rewrite that allows users to increase or
		decrease the badness() score linearly. This interface will replace
		/proc/<pid>/oom_adj.

		A warning will be emitted to the kernel log if an application uses this
		deprecated interface. After it is printed once, future warnings will be
		suppressed until the kernel is rebooted.

Documentation/ABI/testing/sysfs-block-zram

0 → 100644

+99 −0

Original line number	Diff line number	Diff line
		What: /sys/block/zram<id>/disksize
		Date: August 2010
		Contact: Nitin Gupta <ngupta@vflare.org>
		Description:
		The disksize file is read-write and specifies the disk size
		which represents the limit on the uncompressed worth of data
		that can be stored in this disk.

		What: /sys/block/zram<id>/initstate
		Date: August 2010
		Contact: Nitin Gupta <ngupta@vflare.org>
		Description:
		The disksize file is read-only and shows the initialization
		state of the device.

		What: /sys/block/zram<id>/reset
		Date: August 2010
		Contact: Nitin Gupta <ngupta@vflare.org>
		Description:
		The disksize file is write-only and allows resetting the
		device. The reset operation frees all the memory assocaited
		with this device.

		What: /sys/block/zram<id>/num_reads
		Date: August 2010
		Contact: Nitin Gupta <ngupta@vflare.org>
		Description:
		The num_reads file is read-only and specifies the number of
		reads (failed or successful) done on this device.

		What: /sys/block/zram<id>/num_writes
		Date: August 2010
		Contact: Nitin Gupta <ngupta@vflare.org>
		Description:
		The num_writes file is read-only and specifies the number of
		writes (failed or successful) done on this device.

		What: /sys/block/zram<id>/invalid_io
		Date: August 2010
		Contact: Nitin Gupta <ngupta@vflare.org>
		Description:
		The invalid_io file is read-only and specifies the number of
		non-page-size-aligned I/O requests issued to this device.

		What: /sys/block/zram<id>/notify_free
		Date: August 2010
		Contact: Nitin Gupta <ngupta@vflare.org>
		Description:
		The notify_free file is read-only and specifies the number of
		swap slot free notifications received by this device. These
		notifications are send to a swap block device when a swap slot
		is freed. This statistic is applicable only when this disk is
		being used as a swap disk.

		What: /sys/block/zram<id>/discard
		Date: August 2010
		Contact: Nitin Gupta <ngupta@vflare.org>
		Description:
		The discard file is read-only and specifies the number of
		discard requests received by this device. These requests
		provide information to block device regarding blocks which are
		no longer used by filesystem.

		What: /sys/block/zram<id>/zero_pages
		Date: August 2010
		Contact: Nitin Gupta <ngupta@vflare.org>
		Description:
		The zero_pages file is read-only and specifies number of zero
		filled pages written to this disk. No memory is allocated for
		such pages.

		What: /sys/block/zram<id>/orig_data_size
		Date: August 2010
		Contact: Nitin Gupta <ngupta@vflare.org>
		Description:
		The orig_data_size file is read-only and specifies uncompressed
		size of data stored in this disk. This excludes zero-filled
		pages (zero_pages) since no memory is allocated for them.
		Unit: bytes

		What: /sys/block/zram<id>/compr_data_size
		Date: August 2010
		Contact: Nitin Gupta <ngupta@vflare.org>
		Description:
		The compr_data_size file is read-only and specifies compressed
		size of data stored in this disk. So, compression ratio can be
		calculated using orig_data_size and this statistic.
		Unit: bytes

		What: /sys/block/zram<id>/mem_used_total
		Date: August 2010
		Contact: Nitin Gupta <ngupta@vflare.org>
		Description:
		The mem_used_total file is read-only and specifies the amount
		of memory, including allocator fragmentation and metadata
		overhead, allocated for this disk. So, allocator space
		efficiency can be calculated using compr_data_size and this
		statistic.
		Unit: bytes
		No newline at end of file

Documentation/DocBook/kgdb.tmpl

+12 −1

Original line number	Diff line number	Diff line
		@@ -710,7 +710,18 @@ Task Addr Pid Parent [*] cpu State Thread Command
		<listitem><para>A simple shell</para></listitem>
		<listitem><para>The kdb core command set</para></listitem>
		<listitem><para>A registration API to register additional kdb shell commands.</para>
		<para>A good example of a self-contained kdb module is the "ftdump" command for dumping the ftrace buffer. See: kernel/trace/trace_kdb.c</para></listitem>
		<itemizedlist>
		<listitem><para>A good example of a self-contained kdb module
		is the "ftdump" command for dumping the ftrace buffer. See:
		kernel/trace/trace_kdb.c</para></listitem>
		<listitem><para>For an example of how to dynamically register
		a new kdb command you can build the kdb_hello.ko kernel module
		from samples/kdb/kdb_hello.c. To build this example you can
		set CONFIG_SAMPLES=y and CONFIG_SAMPLE_KDB=m in your kernel
		config. Later run "modprobe kdb_hello" and the next time you
		enter the kdb shell, you can run the "hello"
		command.</para></listitem>
		</itemizedlist></listitem>
		<listitem><para>The implementation for kdb_printf() which
		emits messages directly to I/O drivers, bypassing the kernel
		log.</para></listitem>

Documentation/DocBook/media-entities.tmpl

+6 −0

Original line number	Diff line number	Diff line
		@@ -250,6 +250,9 @@
		<!ENTITY sub-yuv422p SYSTEM "v4l/pixfmt-yuv422p.xml">
		<!ENTITY sub-yuyv SYSTEM "v4l/pixfmt-yuyv.xml">
		<!ENTITY sub-yvyu SYSTEM "v4l/pixfmt-yvyu.xml">
		<!ENTITY sub-srggb10 SYSTEM "v4l/pixfmt-srggb10.xml">
		<!ENTITY sub-srggb8 SYSTEM "v4l/pixfmt-srggb8.xml">
		<!ENTITY sub-y10 SYSTEM "v4l/pixfmt-y10.xml">
		<!ENTITY sub-pixfmt SYSTEM "v4l/pixfmt.xml">
		<!ENTITY sub-cropcap SYSTEM "v4l/vidioc-cropcap.xml">
		<!ENTITY sub-dbg-g-register SYSTEM "v4l/vidioc-dbg-g-register.xml">
		@@ -347,6 +350,9 @@
		<!ENTITY yuv422p SYSTEM "v4l/pixfmt-yuv422p.xml">
		<!ENTITY yuyv SYSTEM "v4l/pixfmt-yuyv.xml">
		<!ENTITY yvyu SYSTEM "v4l/pixfmt-yvyu.xml">
		<!ENTITY srggb10 SYSTEM "v4l/pixfmt-srggb10.xml">
		<!ENTITY srggb8 SYSTEM "v4l/pixfmt-srggb8.xml">
		<!ENTITY y10 SYSTEM "v4l/pixfmt-y10.xml">
		<!ENTITY cropcap SYSTEM "v4l/vidioc-cropcap.xml">
		<!ENTITY dbg-g-register SYSTEM "v4l/vidioc-dbg-g-register.xml">
		<!ENTITY encoder-cmd SYSTEM "v4l/vidioc-encoder-cmd.xml">

Documentation/DocBook/v4l/compat.xml

+16 −8

Original line number	Diff line number	Diff line
		@@ -21,11 +21,15 @@ API.</para>
		<title>Opening and Closing Devices</title>

		<para>For compatibility reasons the character device file names
		recommended for V4L2 video capture, overlay, radio, teletext and raw
		recommended for V4L2 video capture, overlay, radio and raw
		vbi capture devices did not change from those used by V4L. They are
		listed in <xref linkend="devices" /> and below in <xref
		linkend="v4l-dev" />.</para>

		<para>The teletext devices (minor range 192-223) have been removed in
		V4L2 and no longer exist. There is no hardware available anymore for handling
		pure teletext. Instead raw or sliced VBI is used.</para>

		<para>The V4L <filename>videodev</filename> module automatically
		assigns minor numbers to drivers in load order, depending on the
		registered device type. We recommend that V4L2 drivers by default
		@@ -65,13 +69,6 @@ not compatible with V4L or V4L2.</para> </footnote>,
		<filename>/dev/radio63</filename></para></entry>
		<entry>64-127</entry>
		</row>
		<row>
		<entry>Teletext decoder</entry>
		<entry><para><filename>/dev/vtx</filename>,
		<filename>/dev/vtx0</filename> to
		<filename>/dev/vtx31</filename></para></entry>
		<entry>192-223</entry>
		</row>
		<row>
		<entry>Raw VBI capture</entry>
		<entry><para><filename>/dev/vbi</filename>,
		@@ -2345,6 +2342,17 @@ more information.</para>
		</listitem>
		</orderedlist>
		</section>
		<section>
		<title>V4L2 in Linux 2.6.37</title>
		<orderedlist>
		<listitem>
		<para>Remove the vtx (videotext/teletext) API. This API was no longer
		used and no hardware exists to verify the API. Nor were any userspace applications found
		that used it. It was originally scheduled for removal in 2.6.35.
		</para>
		</listitem>
		</orderedlist>
		</section>

		<section id="other">
		<title>Relation of V4L2 to other Linux multimedia APIs</title>