Loading Documentation/ABI/obsolete/proc-sys-vm-nr_pdflush_threads 0 → 100644 +5 −0 Original line number Diff line number Diff line What: /proc/sys/vm/nr_pdflush_threads Date: June 2012 Contact: Wanpeng Li <liwp@linux.vnet.ibm.com> Description: Since pdflush is replaced by per-BDI flusher, the interface of old pdflush exported in /proc/sys/vm/ should be removed. Documentation/ABI/stable/sysfs-bus-firewire +11 −0 Original line number Diff line number Diff line Loading @@ -39,6 +39,17 @@ Users: udev rules to set ownership and access permissions or ACLs of /dev/fw[0-9]+ character device files What: /sys/bus/firewire/devices/fw[0-9]+/is_local Date: July 2012 KernelVersion: 3.6 Contact: linux1394-devel@lists.sourceforge.net Description: IEEE 1394 node device attribute. Read-only and immutable. Values: 1: The sysfs entry represents a local node (a controller card). 0: The sysfs entry represents a remote node. What: /sys/bus/firewire/devices/fw[0-9]+[.][0-9]+/ Date: May 2007 KernelVersion: 2.6.22 Loading Documentation/ABI/testing/sysfs-bus-rbd +8 −2 Original line number Diff line number Diff line Loading @@ -35,8 +35,14 @@ name pool The pool where this rbd image resides. The pool-name pair is unique per rados system. The name of the storage pool where this rbd image resides. An rbd image name is unique within its pool. pool_id The unique identifier for the rbd image's pool. This is a permanent attribute of the pool. A pool's id will never change. size Loading Documentation/ABI/testing/sysfs-devices-edac 0 → 100644 +140 −0 Original line number Diff line number Diff line What: /sys/devices/system/edac/mc/mc*/reset_counters Date: January 2006 Contact: linux-edac@vger.kernel.org Description: This write-only control file will zero all the statistical counters for UE and CE errors on the given memory controller. Zeroing the counters will also reset the timer indicating how long since the last counter were reset. This is useful for computing errors/time. Since the counters are always reset at driver initialization time, no module/kernel parameter is available. What: /sys/devices/system/edac/mc/mc*/seconds_since_reset Date: January 2006 Contact: linux-edac@vger.kernel.org Description: This attribute file displays how many seconds have elapsed since the last counter reset. This can be used with the error counters to measure error rates. What: /sys/devices/system/edac/mc/mc*/mc_name Date: January 2006 Contact: linux-edac@vger.kernel.org Description: This attribute file displays the type of memory controller that is being utilized. What: /sys/devices/system/edac/mc/mc*/size_mb Date: January 2006 Contact: linux-edac@vger.kernel.org Description: This attribute file displays, in count of megabytes, of memory that this memory controller manages. What: /sys/devices/system/edac/mc/mc*/ue_count Date: January 2006 Contact: linux-edac@vger.kernel.org Description: This attribute file displays the total count of uncorrectable errors that have occurred on this memory controller. If panic_on_ue is set, this counter will not have a chance to increment, since EDAC will panic the system What: /sys/devices/system/edac/mc/mc*/ue_noinfo_count Date: January 2006 Contact: linux-edac@vger.kernel.org Description: This attribute file displays the number of UEs that have occurred on this memory controller with no information as to which DIMM slot is having errors. What: /sys/devices/system/edac/mc/mc*/ce_count Date: January 2006 Contact: linux-edac@vger.kernel.org Description: This attribute file displays the total count of correctable errors that have occurred on this memory controller. This count is very important to examine. CEs provide early indications that a DIMM is beginning to fail. This count field should be monitored for non-zero values and report such information to the system administrator. What: /sys/devices/system/edac/mc/mc*/ce_noinfo_count Date: January 2006 Contact: linux-edac@vger.kernel.org Description: This attribute file displays the number of CEs that have occurred on this memory controller wherewith no information as to which DIMM slot is having errors. Memory is handicapped, but operational, yet no information is available to indicate which slot the failing memory is in. This count field should be also be monitored for non-zero values. What: /sys/devices/system/edac/mc/mc*/sdram_scrub_rate Date: February 2007 Contact: linux-edac@vger.kernel.org Description: Read/Write attribute file that controls memory scrubbing. The scrubbing rate used by the memory controller is set by writing a minimum bandwidth in bytes/sec to the attribute file. The rate will be translated to an internal value that gives at least the specified rate. Reading the file will return the actual scrubbing rate employed. If configuration fails or memory scrubbing is not implemented, the value of the attribute file will be -1. What: /sys/devices/system/edac/mc/mc*/max_location Date: April 2012 Contact: Mauro Carvalho Chehab <mchehab@redhat.com> linux-edac@vger.kernel.org Description: This attribute file displays the information about the last available memory slot in this memory controller. It is used by userspace tools in order to display the memory filling layout. What: /sys/devices/system/edac/mc/mc*/(dimm|rank)*/size Date: April 2012 Contact: Mauro Carvalho Chehab <mchehab@redhat.com> linux-edac@vger.kernel.org Description: This attribute file will display the size of dimm or rank. For dimm*/size, this is the size, in MB of the DIMM memory stick. For rank*/size, this is the size, in MB for one rank of the DIMM memory stick. On single rank memories (1R), this is also the total size of the dimm. On dual rank (2R) memories, this is half the size of the total DIMM memories. What: /sys/devices/system/edac/mc/mc*/(dimm|rank)*/dimm_dev_type Date: April 2012 Contact: Mauro Carvalho Chehab <mchehab@redhat.com> linux-edac@vger.kernel.org Description: This attribute file will display what type of DRAM device is being utilized on this DIMM (x1, x2, x4, x8, ...). What: /sys/devices/system/edac/mc/mc*/(dimm|rank)*/dimm_edac_mode Date: April 2012 Contact: Mauro Carvalho Chehab <mchehab@redhat.com> linux-edac@vger.kernel.org Description: This attribute file will display what type of Error detection and correction is being utilized. For example: S4ECD4ED would mean a Chipkill with x4 DRAM. What: /sys/devices/system/edac/mc/mc*/(dimm|rank)*/dimm_label Date: April 2012 Contact: Mauro Carvalho Chehab <mchehab@redhat.com> linux-edac@vger.kernel.org Description: This control file allows this DIMM to have a label assigned to it. With this label in the module, when errors occur the output can provide the DIMM label in the system log. This becomes vital for panic events to isolate the cause of the UE event. DIMM Labels must be assigned after booting, with information that correctly identifies the physical slot with its silk screen label. This information is currently very motherboard specific and determination of this information must occur in userland at this time. What: /sys/devices/system/edac/mc/mc*/(dimm|rank)*/dimm_location Date: April 2012 Contact: Mauro Carvalho Chehab <mchehab@redhat.com> linux-edac@vger.kernel.org Description: This attribute file will display the location (csrow/channel, branch/channel/slot or channel/slot) of the dimm or rank. What: /sys/devices/system/edac/mc/mc*/(dimm|rank)*/dimm_mem_type Date: April 2012 Contact: Mauro Carvalho Chehab <mchehab@redhat.com> linux-edac@vger.kernel.org Description: This attribute file will display what type of memory is currently on this csrow. Normally, either buffered or unbuffered memory (for example, Unbuffered-DDR3). Documentation/ABI/testing/sysfs-devices-platform-sh_mobile_lcdc_fb 0 → 100644 +44 −0 Original line number Diff line number Diff line What: /sys/devices/platform/sh_mobile_lcdc_fb.[0-3]/graphics/fb[0-9]/ovl_alpha Date: May 2012 Contact: Laurent Pinchart <laurent.pinchart@ideasonboard.com> Description: This file is only available on fb[0-9] devices corresponding to overlay planes. Stores the alpha blending value for the overlay. Values range from 0 (transparent) to 255 (opaque). The value is ignored if the mode is not set to Alpha Blending. What: /sys/devices/platform/sh_mobile_lcdc_fb.[0-3]/graphics/fb[0-9]/ovl_mode Date: May 2012 Contact: Laurent Pinchart <laurent.pinchart@ideasonboard.com> Description: This file is only available on fb[0-9] devices corresponding to overlay planes. Selects the composition mode for the overlay. Possible values are 0 - Alpha Blending 1 - ROP3 What: /sys/devices/platform/sh_mobile_lcdc_fb.[0-3]/graphics/fb[0-9]/ovl_position Date: May 2012 Contact: Laurent Pinchart <laurent.pinchart@ideasonboard.com> Description: This file is only available on fb[0-9] devices corresponding to overlay planes. Stores the x,y overlay position on the display in pixels. The position format is `[0-9]+,[0-9]+'. What: /sys/devices/platform/sh_mobile_lcdc_fb.[0-3]/graphics/fb[0-9]/ovl_rop3 Date: May 2012 Contact: Laurent Pinchart <laurent.pinchart@ideasonboard.com> Description: This file is only available on fb[0-9] devices corresponding to overlay planes. Stores the raster operation (ROP3) for the overlay. Values range from 0 to 255. The value is ignored if the mode is not set to ROP3. Loading
Documentation/ABI/obsolete/proc-sys-vm-nr_pdflush_threads 0 → 100644 +5 −0 Original line number Diff line number Diff line What: /proc/sys/vm/nr_pdflush_threads Date: June 2012 Contact: Wanpeng Li <liwp@linux.vnet.ibm.com> Description: Since pdflush is replaced by per-BDI flusher, the interface of old pdflush exported in /proc/sys/vm/ should be removed.
Documentation/ABI/stable/sysfs-bus-firewire +11 −0 Original line number Diff line number Diff line Loading @@ -39,6 +39,17 @@ Users: udev rules to set ownership and access permissions or ACLs of /dev/fw[0-9]+ character device files What: /sys/bus/firewire/devices/fw[0-9]+/is_local Date: July 2012 KernelVersion: 3.6 Contact: linux1394-devel@lists.sourceforge.net Description: IEEE 1394 node device attribute. Read-only and immutable. Values: 1: The sysfs entry represents a local node (a controller card). 0: The sysfs entry represents a remote node. What: /sys/bus/firewire/devices/fw[0-9]+[.][0-9]+/ Date: May 2007 KernelVersion: 2.6.22 Loading
Documentation/ABI/testing/sysfs-bus-rbd +8 −2 Original line number Diff line number Diff line Loading @@ -35,8 +35,14 @@ name pool The pool where this rbd image resides. The pool-name pair is unique per rados system. The name of the storage pool where this rbd image resides. An rbd image name is unique within its pool. pool_id The unique identifier for the rbd image's pool. This is a permanent attribute of the pool. A pool's id will never change. size Loading
Documentation/ABI/testing/sysfs-devices-edac 0 → 100644 +140 −0 Original line number Diff line number Diff line What: /sys/devices/system/edac/mc/mc*/reset_counters Date: January 2006 Contact: linux-edac@vger.kernel.org Description: This write-only control file will zero all the statistical counters for UE and CE errors on the given memory controller. Zeroing the counters will also reset the timer indicating how long since the last counter were reset. This is useful for computing errors/time. Since the counters are always reset at driver initialization time, no module/kernel parameter is available. What: /sys/devices/system/edac/mc/mc*/seconds_since_reset Date: January 2006 Contact: linux-edac@vger.kernel.org Description: This attribute file displays how many seconds have elapsed since the last counter reset. This can be used with the error counters to measure error rates. What: /sys/devices/system/edac/mc/mc*/mc_name Date: January 2006 Contact: linux-edac@vger.kernel.org Description: This attribute file displays the type of memory controller that is being utilized. What: /sys/devices/system/edac/mc/mc*/size_mb Date: January 2006 Contact: linux-edac@vger.kernel.org Description: This attribute file displays, in count of megabytes, of memory that this memory controller manages. What: /sys/devices/system/edac/mc/mc*/ue_count Date: January 2006 Contact: linux-edac@vger.kernel.org Description: This attribute file displays the total count of uncorrectable errors that have occurred on this memory controller. If panic_on_ue is set, this counter will not have a chance to increment, since EDAC will panic the system What: /sys/devices/system/edac/mc/mc*/ue_noinfo_count Date: January 2006 Contact: linux-edac@vger.kernel.org Description: This attribute file displays the number of UEs that have occurred on this memory controller with no information as to which DIMM slot is having errors. What: /sys/devices/system/edac/mc/mc*/ce_count Date: January 2006 Contact: linux-edac@vger.kernel.org Description: This attribute file displays the total count of correctable errors that have occurred on this memory controller. This count is very important to examine. CEs provide early indications that a DIMM is beginning to fail. This count field should be monitored for non-zero values and report such information to the system administrator. What: /sys/devices/system/edac/mc/mc*/ce_noinfo_count Date: January 2006 Contact: linux-edac@vger.kernel.org Description: This attribute file displays the number of CEs that have occurred on this memory controller wherewith no information as to which DIMM slot is having errors. Memory is handicapped, but operational, yet no information is available to indicate which slot the failing memory is in. This count field should be also be monitored for non-zero values. What: /sys/devices/system/edac/mc/mc*/sdram_scrub_rate Date: February 2007 Contact: linux-edac@vger.kernel.org Description: Read/Write attribute file that controls memory scrubbing. The scrubbing rate used by the memory controller is set by writing a minimum bandwidth in bytes/sec to the attribute file. The rate will be translated to an internal value that gives at least the specified rate. Reading the file will return the actual scrubbing rate employed. If configuration fails or memory scrubbing is not implemented, the value of the attribute file will be -1. What: /sys/devices/system/edac/mc/mc*/max_location Date: April 2012 Contact: Mauro Carvalho Chehab <mchehab@redhat.com> linux-edac@vger.kernel.org Description: This attribute file displays the information about the last available memory slot in this memory controller. It is used by userspace tools in order to display the memory filling layout. What: /sys/devices/system/edac/mc/mc*/(dimm|rank)*/size Date: April 2012 Contact: Mauro Carvalho Chehab <mchehab@redhat.com> linux-edac@vger.kernel.org Description: This attribute file will display the size of dimm or rank. For dimm*/size, this is the size, in MB of the DIMM memory stick. For rank*/size, this is the size, in MB for one rank of the DIMM memory stick. On single rank memories (1R), this is also the total size of the dimm. On dual rank (2R) memories, this is half the size of the total DIMM memories. What: /sys/devices/system/edac/mc/mc*/(dimm|rank)*/dimm_dev_type Date: April 2012 Contact: Mauro Carvalho Chehab <mchehab@redhat.com> linux-edac@vger.kernel.org Description: This attribute file will display what type of DRAM device is being utilized on this DIMM (x1, x2, x4, x8, ...). What: /sys/devices/system/edac/mc/mc*/(dimm|rank)*/dimm_edac_mode Date: April 2012 Contact: Mauro Carvalho Chehab <mchehab@redhat.com> linux-edac@vger.kernel.org Description: This attribute file will display what type of Error detection and correction is being utilized. For example: S4ECD4ED would mean a Chipkill with x4 DRAM. What: /sys/devices/system/edac/mc/mc*/(dimm|rank)*/dimm_label Date: April 2012 Contact: Mauro Carvalho Chehab <mchehab@redhat.com> linux-edac@vger.kernel.org Description: This control file allows this DIMM to have a label assigned to it. With this label in the module, when errors occur the output can provide the DIMM label in the system log. This becomes vital for panic events to isolate the cause of the UE event. DIMM Labels must be assigned after booting, with information that correctly identifies the physical slot with its silk screen label. This information is currently very motherboard specific and determination of this information must occur in userland at this time. What: /sys/devices/system/edac/mc/mc*/(dimm|rank)*/dimm_location Date: April 2012 Contact: Mauro Carvalho Chehab <mchehab@redhat.com> linux-edac@vger.kernel.org Description: This attribute file will display the location (csrow/channel, branch/channel/slot or channel/slot) of the dimm or rank. What: /sys/devices/system/edac/mc/mc*/(dimm|rank)*/dimm_mem_type Date: April 2012 Contact: Mauro Carvalho Chehab <mchehab@redhat.com> linux-edac@vger.kernel.org Description: This attribute file will display what type of memory is currently on this csrow. Normally, either buffered or unbuffered memory (for example, Unbuffered-DDR3).
Documentation/ABI/testing/sysfs-devices-platform-sh_mobile_lcdc_fb 0 → 100644 +44 −0 Original line number Diff line number Diff line What: /sys/devices/platform/sh_mobile_lcdc_fb.[0-3]/graphics/fb[0-9]/ovl_alpha Date: May 2012 Contact: Laurent Pinchart <laurent.pinchart@ideasonboard.com> Description: This file is only available on fb[0-9] devices corresponding to overlay planes. Stores the alpha blending value for the overlay. Values range from 0 (transparent) to 255 (opaque). The value is ignored if the mode is not set to Alpha Blending. What: /sys/devices/platform/sh_mobile_lcdc_fb.[0-3]/graphics/fb[0-9]/ovl_mode Date: May 2012 Contact: Laurent Pinchart <laurent.pinchart@ideasonboard.com> Description: This file is only available on fb[0-9] devices corresponding to overlay planes. Selects the composition mode for the overlay. Possible values are 0 - Alpha Blending 1 - ROP3 What: /sys/devices/platform/sh_mobile_lcdc_fb.[0-3]/graphics/fb[0-9]/ovl_position Date: May 2012 Contact: Laurent Pinchart <laurent.pinchart@ideasonboard.com> Description: This file is only available on fb[0-9] devices corresponding to overlay planes. Stores the x,y overlay position on the display in pixels. The position format is `[0-9]+,[0-9]+'. What: /sys/devices/platform/sh_mobile_lcdc_fb.[0-3]/graphics/fb[0-9]/ovl_rop3 Date: May 2012 Contact: Laurent Pinchart <laurent.pinchart@ideasonboard.com> Description: This file is only available on fb[0-9] devices corresponding to overlay planes. Stores the raster operation (ROP3) for the overlay. Values range from 0 to 255. The value is ignored if the mode is not set to ROP3.
