Loading .gitignore +3 −0 Original line number Diff line number Diff line Loading @@ -92,3 +92,6 @@ extra_certificates signing_key.priv signing_key.x509 x509.genkey # Kconfig presets all.config CREDITS +16 −2 Original line number Diff line number Diff line Loading @@ -630,6 +630,13 @@ N: Michael Elizabeth Chastain E: mec@shout.net D: Configure, Menuconfig, xconfig N: Mauro Carvalho Chehab E: m.chehab@samsung.org E: mchehab@infradead.org D: Media subsystem (V4L/DVB) drivers and core D: EDAC drivers and EDAC 3.0 core rework S: Brazil N: Raymond Chen E: raymondc@microsoft.com D: Author of Configure script Loading Loading @@ -2560,10 +2567,14 @@ S: 22 Seaview St S: Fullarton 5063 S: South Australia N. Wolfgang Muees N: Wolfgang Muees E: wolfgang@iksw-muees.de D: Auerswald USB driver N: Paul Mundt E: paul.mundt@gmail.com D: SuperH maintainer N: Ian A. Murdock E: imurdock@gnu.ai.mit.edu D: Creator of Debian distribution Loading Loading @@ -2707,6 +2718,9 @@ N: Greg Page E: gpage@sovereign.org D: IPX development and support N: Venkatesh Pallipadi (Venki) D: x86/HPET N: David Parsons E: orc@pell.chi.il.us D: improved memory detection code. Loading Documentation/00-INDEX +20 −6 Original line number Diff line number Diff line Loading @@ -29,6 +29,8 @@ DMA-ISA-LPC.txt - How to do DMA with ISA (and LPC) devices. DMA-attributes.txt - listing of the various possible attributes a DMA region can have dmatest.txt - how to compile, configure and use the dmatest system. DocBook/ - directory with DocBook templates etc. for kernel documentation. EDID/ Loading Loading @@ -77,6 +79,8 @@ arm/ - directory with info about Linux on the ARM architecture. arm64/ - directory with info about Linux on the 64 bit ARM architecture. assoc_array.txt - generic associative array intro. atomic_ops.txt - semantics and behavior of atomic and bitmask operations. auxdisplay/ Loading @@ -87,6 +91,8 @@ bad_memory.txt - how to use kernel parameters to exclude bad RAM regions. basic_profiling.txt - basic instructions for those who wants to profile Linux kernel. bcache.txt - Block-layer cache on fast SSDs to improve slow (raid) I/O performance. binfmt_misc.txt - info on the kernel support for extra binary formats. blackfin/ Loading Loading @@ -171,6 +177,8 @@ early-userspace/ - info about initramfs, klibc, and userspace early during boot. edac.txt - information on EDAC - Error Detection And Correction efi-stub.txt - How to use the EFI boot stub to bypass GRUB or elilo on EFI systems. eisa.txt - info on EISA bus support. email-clients.txt Loading @@ -195,8 +203,8 @@ futex-requeue-pi.txt - info on requeueing of tasks from a non-PI futex to a PI futex gcov.txt - use of GCC's coverage testing tool "gcov" with the Linux kernel gpio.txt - overview of GPIO (General Purpose Input/Output) access conventions. gpio/ - gpio related documentation hid/ - directory with information on human interface devices highuid.txt Loading Loading @@ -255,6 +263,8 @@ kernel-docs.txt - listing of various WWW + books that document kernel internals. kernel-parameters.txt - summary listing of command line / boot prompt args for the kernel. kernel-per-CPU-kthreads.txt - List of all per-CPU kthreads and how they introduce jitter. kmemcheck.txt - info on dynamic checker that detects uses of uninitialized memory. kmemleak.txt Loading Loading @@ -299,8 +309,6 @@ memory-devices/ - directory with info on parts like the Texas Instruments EMIF driver memory-hotplug.txt - Hotpluggable memory support, how to use and current status. memory.txt - info on typical Linux memory problems. metag/ - directory with info about Linux on Meta architecture. mips/ Loading @@ -311,6 +319,8 @@ mmc/ - directory with info about the MMC subsystem mn10300/ - directory with info about the mn10300 architecture port module-signing.txt - Kernel module signing for increased security when loading modules. mtd/ - directory with info about memory technology devices (flash) mono.txt Loading Loading @@ -343,6 +353,8 @@ pcmcia/ - info on the Linux PCMCIA driver. percpu-rw-semaphore.txt - RCU based read-write semaphore optimized for locking for reading phy.txt - Description of the generic PHY framework. pi-futex.txt - documentation on lightweight priority inheritance futexes. pinctrl.txt Loading Loading @@ -401,8 +413,6 @@ serial-console.txt - how to set up Linux with a serial line console as the default. sgi-ioc4.txt - description of the SGI IOC4 PCI (multi function) device. sgi-visws.txt - short blurb on the SGI Visual Workstations. sh/ - directory with info on porting Linux to a new architecture. smsc_ece1099.txt Loading Loading @@ -431,6 +441,8 @@ sysrq.txt - info on the magic SysRq key. target/ - directory with info on generating TCM v4 fabric .ko modules this_cpu_ops.txt - List rationale behind and the way to use this_cpu operations. thermal/ - directory with information on managing thermal issues (CPU/temp) trace/ Loading Loading @@ -469,6 +481,8 @@ wimax/ - directory with info about Intel Wireless Wimax Connections workqueue.txt - information on the Concurrency Managed Workqueue implementation ww-mutex-design.txt - Intro to Mutex wait/would deadlock handling.s x86/x86_64/ - directory with info on Linux support for AMD x86-64 (Hammer) machines. xtensa/ Loading Documentation/ABI/stable/sysfs-firmware-opal-dump 0 → 100644 +41 −0 Original line number Diff line number Diff line What: /sys/firmware/opal/dump Date: Feb 2014 Contact: Stewart Smith <stewart@linux.vnet.ibm.com> Description: This directory exposes interfaces for interacting with the FSP and platform dumps through OPAL firmware interface. This is only for the powerpc/powernv platform. initiate_dump: When '1' is written to it, we will initiate a dump. Read this file for supported commands. 0xXX-0xYYYY: A directory for dump of type 0xXX and id 0xYYYY (in hex). The name of this directory should not be relied upon to be in this format, only that it's unique among all dumps. For determining the type and ID of the dump, use the id and type files. Do not rely on any particular size of dump type or dump id. Each dump has the following files: id: An ASCII representation of the dump ID in hex (e.g. '0x01') type: An ASCII representation of the type of dump in the format "0x%x %s" with the ID in hex and a description of the dump type (or 'unknown'). Type '0xffffffff unknown' is used when we could not get the type from firmware. e.g. '0x02 System/Platform Dump' dump: A binary file containing the dump. The size of the dump is the size of this file. acknowledge: When 'ack' is written to this, we will acknowledge that we've retrieved the dump to the service processor. It will then remove it, making the dump inaccessible. Reading this file will get a list of supported actions. Documentation/ABI/stable/sysfs-firmware-opal-elog 0 → 100644 +60 −0 Original line number Diff line number Diff line What: /sys/firmware/opal/elog Date: Feb 2014 Contact: Stewart Smith <stewart@linux.vnet.ibm.com> Description: This directory exposes error log entries retrieved through the OPAL firmware interface. Each error log is identified by a unique ID and will exist until explicitly acknowledged to firmware. Each log entry has a directory in /sys/firmware/opal/elog. Log entries may be purged by the service processor before retrieved by firmware or retrieved/acknowledged by Linux if there is no room for more log entries. In the event that Linux has retrieved the log entries but not explicitly acknowledged them to firmware and the service processor needs more room for log entries, the only remaining copy of a log message may be in Linux. Typically, a user space daemon will monitor for new entries, read them out and acknowledge them. The service processor may be able to store more log entries than firmware can, so after you acknowledge an event from Linux you may instantly get another one from the queue that was generated some time in the past. The raw log format is a binary format. We currently do not parse this at all in kernel, leaving it up to user space to solve the problem. In future, we may do more parsing in kernel and add more files to make it easier for simple user space processes to extract more information. For each log entry (directory), there are the following files: id: An ASCII representation of the ID of the error log, in hex - e.g. "0x01". type: An ASCII representation of the type id and description of the type of error log. Currently just "0x00 PEL" - platform error log. In the future there may be additional types. raw: A read-only binary file that can be read to get the raw log entry. These are <16kb, often just hundreds of bytes and "average" 2kb. acknowledge: Writing 'ack' to this file will acknowledge the error log to firmware (and in turn the service processor, if applicable). Shortly after acknowledging it, the log entry will be removed from sysfs. Reading this file will list the supported operations (curently just acknowledge). No newline at end of file Loading
.gitignore +3 −0 Original line number Diff line number Diff line Loading @@ -92,3 +92,6 @@ extra_certificates signing_key.priv signing_key.x509 x509.genkey # Kconfig presets all.config
CREDITS +16 −2 Original line number Diff line number Diff line Loading @@ -630,6 +630,13 @@ N: Michael Elizabeth Chastain E: mec@shout.net D: Configure, Menuconfig, xconfig N: Mauro Carvalho Chehab E: m.chehab@samsung.org E: mchehab@infradead.org D: Media subsystem (V4L/DVB) drivers and core D: EDAC drivers and EDAC 3.0 core rework S: Brazil N: Raymond Chen E: raymondc@microsoft.com D: Author of Configure script Loading Loading @@ -2560,10 +2567,14 @@ S: 22 Seaview St S: Fullarton 5063 S: South Australia N. Wolfgang Muees N: Wolfgang Muees E: wolfgang@iksw-muees.de D: Auerswald USB driver N: Paul Mundt E: paul.mundt@gmail.com D: SuperH maintainer N: Ian A. Murdock E: imurdock@gnu.ai.mit.edu D: Creator of Debian distribution Loading Loading @@ -2707,6 +2718,9 @@ N: Greg Page E: gpage@sovereign.org D: IPX development and support N: Venkatesh Pallipadi (Venki) D: x86/HPET N: David Parsons E: orc@pell.chi.il.us D: improved memory detection code. Loading
Documentation/00-INDEX +20 −6 Original line number Diff line number Diff line Loading @@ -29,6 +29,8 @@ DMA-ISA-LPC.txt - How to do DMA with ISA (and LPC) devices. DMA-attributes.txt - listing of the various possible attributes a DMA region can have dmatest.txt - how to compile, configure and use the dmatest system. DocBook/ - directory with DocBook templates etc. for kernel documentation. EDID/ Loading Loading @@ -77,6 +79,8 @@ arm/ - directory with info about Linux on the ARM architecture. arm64/ - directory with info about Linux on the 64 bit ARM architecture. assoc_array.txt - generic associative array intro. atomic_ops.txt - semantics and behavior of atomic and bitmask operations. auxdisplay/ Loading @@ -87,6 +91,8 @@ bad_memory.txt - how to use kernel parameters to exclude bad RAM regions. basic_profiling.txt - basic instructions for those who wants to profile Linux kernel. bcache.txt - Block-layer cache on fast SSDs to improve slow (raid) I/O performance. binfmt_misc.txt - info on the kernel support for extra binary formats. blackfin/ Loading Loading @@ -171,6 +177,8 @@ early-userspace/ - info about initramfs, klibc, and userspace early during boot. edac.txt - information on EDAC - Error Detection And Correction efi-stub.txt - How to use the EFI boot stub to bypass GRUB or elilo on EFI systems. eisa.txt - info on EISA bus support. email-clients.txt Loading @@ -195,8 +203,8 @@ futex-requeue-pi.txt - info on requeueing of tasks from a non-PI futex to a PI futex gcov.txt - use of GCC's coverage testing tool "gcov" with the Linux kernel gpio.txt - overview of GPIO (General Purpose Input/Output) access conventions. gpio/ - gpio related documentation hid/ - directory with information on human interface devices highuid.txt Loading Loading @@ -255,6 +263,8 @@ kernel-docs.txt - listing of various WWW + books that document kernel internals. kernel-parameters.txt - summary listing of command line / boot prompt args for the kernel. kernel-per-CPU-kthreads.txt - List of all per-CPU kthreads and how they introduce jitter. kmemcheck.txt - info on dynamic checker that detects uses of uninitialized memory. kmemleak.txt Loading Loading @@ -299,8 +309,6 @@ memory-devices/ - directory with info on parts like the Texas Instruments EMIF driver memory-hotplug.txt - Hotpluggable memory support, how to use and current status. memory.txt - info on typical Linux memory problems. metag/ - directory with info about Linux on Meta architecture. mips/ Loading @@ -311,6 +319,8 @@ mmc/ - directory with info about the MMC subsystem mn10300/ - directory with info about the mn10300 architecture port module-signing.txt - Kernel module signing for increased security when loading modules. mtd/ - directory with info about memory technology devices (flash) mono.txt Loading Loading @@ -343,6 +353,8 @@ pcmcia/ - info on the Linux PCMCIA driver. percpu-rw-semaphore.txt - RCU based read-write semaphore optimized for locking for reading phy.txt - Description of the generic PHY framework. pi-futex.txt - documentation on lightweight priority inheritance futexes. pinctrl.txt Loading Loading @@ -401,8 +413,6 @@ serial-console.txt - how to set up Linux with a serial line console as the default. sgi-ioc4.txt - description of the SGI IOC4 PCI (multi function) device. sgi-visws.txt - short blurb on the SGI Visual Workstations. sh/ - directory with info on porting Linux to a new architecture. smsc_ece1099.txt Loading Loading @@ -431,6 +441,8 @@ sysrq.txt - info on the magic SysRq key. target/ - directory with info on generating TCM v4 fabric .ko modules this_cpu_ops.txt - List rationale behind and the way to use this_cpu operations. thermal/ - directory with information on managing thermal issues (CPU/temp) trace/ Loading Loading @@ -469,6 +481,8 @@ wimax/ - directory with info about Intel Wireless Wimax Connections workqueue.txt - information on the Concurrency Managed Workqueue implementation ww-mutex-design.txt - Intro to Mutex wait/would deadlock handling.s x86/x86_64/ - directory with info on Linux support for AMD x86-64 (Hammer) machines. xtensa/ Loading
Documentation/ABI/stable/sysfs-firmware-opal-dump 0 → 100644 +41 −0 Original line number Diff line number Diff line What: /sys/firmware/opal/dump Date: Feb 2014 Contact: Stewart Smith <stewart@linux.vnet.ibm.com> Description: This directory exposes interfaces for interacting with the FSP and platform dumps through OPAL firmware interface. This is only for the powerpc/powernv platform. initiate_dump: When '1' is written to it, we will initiate a dump. Read this file for supported commands. 0xXX-0xYYYY: A directory for dump of type 0xXX and id 0xYYYY (in hex). The name of this directory should not be relied upon to be in this format, only that it's unique among all dumps. For determining the type and ID of the dump, use the id and type files. Do not rely on any particular size of dump type or dump id. Each dump has the following files: id: An ASCII representation of the dump ID in hex (e.g. '0x01') type: An ASCII representation of the type of dump in the format "0x%x %s" with the ID in hex and a description of the dump type (or 'unknown'). Type '0xffffffff unknown' is used when we could not get the type from firmware. e.g. '0x02 System/Platform Dump' dump: A binary file containing the dump. The size of the dump is the size of this file. acknowledge: When 'ack' is written to this, we will acknowledge that we've retrieved the dump to the service processor. It will then remove it, making the dump inaccessible. Reading this file will get a list of supported actions.
Documentation/ABI/stable/sysfs-firmware-opal-elog 0 → 100644 +60 −0 Original line number Diff line number Diff line What: /sys/firmware/opal/elog Date: Feb 2014 Contact: Stewart Smith <stewart@linux.vnet.ibm.com> Description: This directory exposes error log entries retrieved through the OPAL firmware interface. Each error log is identified by a unique ID and will exist until explicitly acknowledged to firmware. Each log entry has a directory in /sys/firmware/opal/elog. Log entries may be purged by the service processor before retrieved by firmware or retrieved/acknowledged by Linux if there is no room for more log entries. In the event that Linux has retrieved the log entries but not explicitly acknowledged them to firmware and the service processor needs more room for log entries, the only remaining copy of a log message may be in Linux. Typically, a user space daemon will monitor for new entries, read them out and acknowledge them. The service processor may be able to store more log entries than firmware can, so after you acknowledge an event from Linux you may instantly get another one from the queue that was generated some time in the past. The raw log format is a binary format. We currently do not parse this at all in kernel, leaving it up to user space to solve the problem. In future, we may do more parsing in kernel and add more files to make it easier for simple user space processes to extract more information. For each log entry (directory), there are the following files: id: An ASCII representation of the ID of the error log, in hex - e.g. "0x01". type: An ASCII representation of the type id and description of the type of error log. Currently just "0x00 PEL" - platform error log. In the future there may be additional types. raw: A read-only binary file that can be read to get the raw log entry. These are <16kb, often just hundreds of bytes and "average" 2kb. acknowledge: Writing 'ack' to this file will acknowledge the error log to firmware (and in turn the service processor, if applicable). Shortly after acknowledging it, the log entry will be removed from sysfs. Reading this file will list the supported operations (curently just acknowledge). No newline at end of file
