config FSCACHE tristate "General filesystem local caching manager" help This option enables a generic filesystem caching manager that can be used by various network and other filesystems to cache data locally. Different sorts of caches can be plugged in, depending on the resources available. See Documentation/filesystems/caching/fscache.txt for more information. config FSCACHE_STATS bool "Gather statistical information on local caching" depends on FSCACHE && PROC_FS help This option causes statistical information to be gathered on local caching and exported through file: /proc/fs/fscache/stats The gathering of statistics adds a certain amount of overhead to execution as there are a quite a few stats gathered, and on a multi-CPU system these may be on cachelines that keep bouncing between CPUs. On the other hand, the stats are very useful for debugging purposes. Saying 'Y' here is recommended. See Documentation/filesystems/caching/fscache.txt for more information. config FSCACHE_HISTOGRAM bool "Gather latency information on local caching" depends on FSCACHE && PROC_FS help This option causes latency information to be gathered on local caching and exported through file: /proc/fs/fscache/histogram The generation of this histogram adds a certain amount of overhead to execution as there are a number of points at which data is gathered, and on a multi-CPU system these may be on cachelines that keep bouncing between CPUs. On the other hand, the histogram may be useful for debugging purposes. Saying 'N' here is recommended. See Documentation/filesystems/caching/fscache.txt for more information. config FSCACHE_DEBUG bool "Debug FS-Cache" depends on FSCACHE help This permits debugging to be dynamically enabled in the local caching management module. If this is set, the debugging output may be enabled by setting bits in /sys/modules/fscache/parameter/debug. See Documentation/filesystems/caching/fscache.txt for more information. config FSCACHE_OBJECT_LIST bool "Maintain global object list for debugging purposes" depends on FSCACHE && PROC_FS help Maintain a global list of active fscache objects that can be retrieved through /proc/fs/fscache/objects for debugging purposes ='hidden' name='id' value='54791b276b4000b307339f269d3bf7db877d536f'/>
path: root/include/sound/hdmi-codec.h
diff options
context:
space:
mode:
authorDavid S. Miller <davem@davemloft.net>2017-01-30 14:28:22 -0800
committerDavid S. Miller <davem@davemloft.net>2017-01-30 14:28:22 -0800
commit54791b276b4000b307339f269d3bf7db877d536f (patch)
tree1c2616bd373ce5ea28aac2a53e32f5b5834901ce /include/sound/hdmi-codec.h
parent5d0e7705774dd412a465896d08d59a81a345c1e4 (diff)
parent047487241ff59374fded8c477f21453681f5995c (diff)
Merge branch 'sparc64-non-resumable-user-error-recovery'
Liam R. Howlett says: ==================== sparc64: Recover from userspace non-resumable PIO & MEM errors A non-resumable error from userspace is able to cause a kernel panic or trap loop due to the setup and handling of the queued traps once in the kernel. This patch series addresses both of these issues. The queues are fixed by simply zeroing the memory before use. PIO errors from userspace will result in a SIGBUS being sent to the user process. The MEM errors form userspace will result in a SIGKILL and also cause the offending pages to be claimed so they are no longer used in future tasks. SIGKILL is used to ensure that the process does not try to coredump and result in an attempt to read the memory again from within kernel space. Although there is a HV call to scrub the memory (mem_scrub), there is no easy way to guarantee that the real memory address(es) are not used by other tasks. Clearing the error with mem_scrub would zero the memory and cause the other processes to proceed with bad data. The handling of other non-resumable errors remain unchanged and will cause a panic. ==================== Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'include/sound/hdmi-codec.h')