Skip to content

cloud-kernel
cloud-kernel

openanolis / cloud-kernel
接近 2 年 前同步成功

通知 170
Star 36
Fork 7
cloud-kernel
cloud-kernel
提交 dbbc21bb 编写于 作者: M Mark Brown
浏览文件
操作

Merge tag 'v4.10-rc1' into asoc-intel 

Linux 4.10-rc1
上级 f6fa11a3 7ce7d89f
展开全部 隐藏空白更改
内联 并排
Showing with 89618 addition and 59664 deletion

要显示的变更太多。

To preserve performance only 1000 of 1000+ files are displayed.
文本差异 电子邮件补丁
CREDITS
浏览文件 @ dbbc21bb
......@@ -2775,6 +2775,10 @@ S: C/ Mieses 20, 9-B
S: Valladolid 47009
S: Spain
N: Peter Oruba
D: AMD Microcode loader driver
S: Germany
N: Jens Osterkamp
E: jens@de.ibm.com
D: Maintainer of Spidernet network driver for Cell
......@@ -3945,8 +3949,6 @@ E: gwingerde@gmail.com
D: Ralink rt2x00 WLAN driver
D: Minix V2 file-system
D: Misc fixes
S: Geessinkweg 177
S: 7544 TX Enschede
S: The Netherlands
N: Lars Wirzenius
......
Documentation/00-INDEX
浏览文件 @ dbbc21bb
......@@ -14,13 +14,8 @@ Following translations are available on the WWW:
- this file.
ABI/
- info on kernel <-> userspace ABI and relative interface stability.
BUG-HUNTING
- brute force method of doing binary search of patches to find bug.
Changes
- list of changes that break older software packages.
CodingStyle
- how the maintainers expect the C code in the kernel to look.
- nothing here, just a pointer to process/coding-style.rst.
DMA-API.txt
- DMA API, pci_ API & extensions for non-consistent memory machines.
DMA-API-HOWTO.txt
......@@ -33,8 +28,6 @@ DocBook/
- directory with DocBook templates etc. for kernel documentation.
EDID/
- directory with info on customizing EDID for broken gfx/displays.
HOWTO
- the process and procedures of how to do Linux kernel development.
IPMI.txt
- info on Linux Intelligent Platform Management Interface (IPMI) Driver.
IRQ-affinity.txt
......@@ -46,62 +39,43 @@ IRQ.txt
Intel-IOMMU.txt
- basic info on the Intel IOMMU virtualization support.
Makefile
- This file does nothing. Removing it breaks make htmldocs and
make distclean.
ManagementStyle
- how to (attempt to) manage kernel hackers.
- It's not of interest for those who aren't touching the build system.
Makefile.sphinx
- It's not of interest for those who aren't touching the build system.
PCI/
- info related to PCI drivers.
RCU/
- directory with info on RCU (read-copy update).
SAK.txt
- info on Secure Attention Keys.
SM501.txt
- Silicon Motion SM501 multimedia companion chip
SecurityBugs
- procedure for reporting security bugs found in the kernel.
SubmitChecklist
- Linux kernel patch submission checklist.
SubmittingDrivers
- procedure to get a new driver source included into the kernel tree.
SubmittingPatches
- procedure to get a source patch included into the kernel tree.
VGA-softcursor.txt
- how to change your VGA cursor from a blinking underscore.
- nothing here, just a pointer to process/coding-style.rst.
accounting/
- documentation on accounting and taskstats.
acpi/
- info on ACPI-specific hooks in the kernel.
admin-guide/
- info related to Linux users and system admins.
aoe/
- description of AoE (ATA over Ethernet) along with config examples.
applying-patches.txt
- description of various trees and how to apply their patches.
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/
- misc. LCD driver documentation (cfag12864b, ks0108).
backlight/
- directory with info on controlling backlights in flat panel displays
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/
- directory with documentation for the Blackfin arch.
block/
- info on the Block I/O (BIO) layer.
blockdev/
- info on block devices & drivers
braille-console.txt
- info on how to use serial devices for Braille support.
bt8xxgpio.txt
- info on how to modify a bt8xx video card for GPIO usage.
btmrvl.txt
......@@ -114,18 +88,24 @@ cachetlb.txt
- describes the cache/TLB flushing interfaces Linux uses.
cdrom/
- directory with information on the CD-ROM drivers that Linux has.
cgroups/
- cgroups features, including cpusets and memory controller.
cgroup-v1/
- cgroups v1 features, including cpusets and memory controller.
cgroup-v2.txt
- cgroups v2 features, including cpusets and memory controller.
circular-buffers.txt
- how to make use of the existing circular buffer infrastructure
clk.txt
- info on the common clock framework
coccinelle.txt
- info on how to get and use the Coccinelle code checking tool.
cma/
- Continuous Memory Area (CMA) debugfs interface.
conf.py
- It's not of interest for those who aren't touching the build system.
connector/
- docs on the netlink based userspace<->kernel space communication mod.
console/
- documentation on Linux console drivers.
core-api/
- documentation on kernel core components.
cpu-freq/
- info on CPU frequency and voltage scaling.
cpu-hotplug.txt
......@@ -150,42 +130,42 @@ debugging-via-ohci1394.txt
- how to use firewire like a hardware debugger memory reader.
dell_rbu.txt
- document demonstrating the use of the Dell Remote BIOS Update driver.
development-process/
- how to work with the mainline kernel development process.
dev-tools/
- directory with info on development tools for the kernel.
device-mapper/
- directory with info on Device Mapper.
devices.txt
- plain ASCII listing of all the nodes in /dev/ with major minor #'s.
dmaengine/
- the DMA engine and controller API guides.
devicetree/
- directory with info on device tree files used by OF/PowerPC/ARM
digsig.txt
-info on the Digital Signature Verification API
dma-buf-sharing.txt
- the DMA Buffer Sharing API Guide
docutils.conf
- nothing here. Just a configuration file for docutils.
dontdiff
- file containing a list of files that should never be diff'ed.
driver-api/
- the Linux driver implementer's API guide.
driver-model/
- directory with info about Linux driver model.
dvb/
- info on Linux Digital Video Broadcast (DVB) subsystem.
dynamic-debug-howto.txt
- how to use the dynamic debug (dyndbg) feature.
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
- info on how to use e-mail to send un-mangled (git) patches.
extcon/
- directory with porting guide for Android kernel switch driver.
isa.txt
- info on EISA bus support.
fault-injection/
- dir with docs about the fault injection capabilities infrastructure.
fb/
- directory with info on the frame buffer graphics abstraction layer.
features/
- status of feature implementation on different architectures.
filesystems/
- info on the vfs and the various filesystems that Linux supports.
firmware_class/
......@@ -194,20 +174,22 @@ flexible-arrays.txt
- how to make use of flexible sized arrays in linux
fmc/
- information about the FMC bus abstraction
fpga/
- FPGA Manager Core.
frv/
- Fujitsu FR-V Linux documentation.
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
gcc-plugins.txt
- GCC plugin infrastructure.
gpio/
- gpio related documentation
gpu/
- directory with information on GPU driver developer's guide.
hid/
- directory with information on human interface devices
highuid.txt
- notes on the change from 16 bit to 32 bit user/group IDs.
hsi.txt
- HSI subsystem overview.
hwspinlock.txt
- hardware spinlock provides hardware assistance for synchronization
timers/
......@@ -218,18 +200,18 @@ hwmon/
- directory with docs on various hardware monitoring drivers.
i2c/
- directory with info about the I2C bus/protocol (2 wire, kHz speed).
i2o/
- directory with info about the Linux I2O subsystem.
x86/i386/
- directory with info about Linux on Intel 32 bit architecture.
ia64/
- directory with info about Linux on Intel 64 bit architecture.
ide/
- Information regarding the Enhanced IDE drive.
iio/
- info on industrial IIO configfs support.
index.rst
- main index for the documentation at ReST format.
infiniband/
- directory with documents concerning Linux InfiniBand support.
init.txt
- what to do when the kernel can't find the 1st process to run.
initrd.txt
- how to use the RAM disk as an initial/temporary root filesystem.
input/
- info on Linux input device support.
intel_txt.txt
......@@ -248,28 +230,16 @@ isapnp.txt
- info on Linux ISA Plug & Play support.
isdn/
- directory with info on the Linux ISDN support, and supported cards.
java.txt
- info on the in-kernel binary support for Java(tm).
ja_JP/
- directory with Japanese translations of various documents
kbuild/
- directory with info about the kernel build process.
kernel-doc-nano-HOWTO.txt
- outdated info about kernel-doc documentation.
kdump/
- directory with mini HowTo on getting the crash dump code to work.
kernel-docs.txt
- listing of various WWW + books that document kernel internals.
kernel-documentation.rst
doc-guide/
- how to write and format reStructuredText kernel documentation
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
- info on how to make use of the kernel memory leak detection system
ko_KR/
- directory with Korean translations of various documents
kobject.txt
- info of the kobject infrastructure of the Linux kernel.
kprobes.txt
......@@ -284,8 +254,8 @@ ldm.txt
- a brief description of LDM (Windows Dynamic Disks).
leds/
- directory with info about LED handling under Linux.
local_ops.txt
- semantics and behavior of local atomic operations.
livepatch/
- info on kernel live patching.
locking/
- directory with info about kernel locking primitives
lockup-watchdogs.txt
......@@ -298,22 +268,24 @@ lzo.txt
- kernel LZO decompressor input formats
m68k/
- directory with info about Linux on Motorola 68k architecture.
magic-number.txt
- list of magic numbers used to mark/protect kernel data structures.
mailbox.txt
- How to write drivers for the common mailbox framework (IPC).
md.txt
- info on boot arguments for the multiple devices driver.
media-framework.txt
- info on media framework, its data structures, functions and usage.
md-cluster.txt
- info on shared-device RAID MD cluster.
media/
- info on media drivers: uAPI, kAPI and driver documentation.
memory-barriers.txt
- info on Linux kernel memory barriers.
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.
men-chameleon-bus.txt
- info on MEN chameleon bus.
metag/
- directory with info about Linux on Meta architecture.
mic/
- Intel Many Integrated Core (MIC) architecture device driver.
mips/
- directory with info about Linux on MIPS architecture.
misc-devices/
......@@ -322,12 +294,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
- how to execute Mono-based .NET binaries with the help of BINFMT_MISC.
namespaces/
- directory with various information about namespaces
netlabel/
......@@ -336,30 +304,42 @@ networking/
- directory with info on various aspects of networking with Linux.
nfc/
- directory relating info about Near Field Communications support.
nios2/
- Linux on the Nios II architecture.
nommu-mmap.txt
- documentation about no-mmu memory mapping support.
numastat.txt
- info on how to read Numa policy hit/miss statistics in sysfs.
oops-tracing.txt
- how to decode those nasty internal kernel error dump messages.
ntb.txt
- info on Non-Transparent Bridge (NTB) drivers.
nvdimm/
- info on non-volatile devices.
nvmem/
- info on non volatile memory framework.
output/
- default directory where html/LaTeX/pdf files will be written.
padata.txt
- An introduction to the "padata" parallel execution API
parisc/
- directory with info on using Linux on PA-RISC architecture.
parport.txt
- how to use the parallel-port driver.
parport-lowlevel.txt
- description and usage of the low level parallel port functions.
pcmcia/
- info on the Linux PCMCIA driver.
percpu-rw-semaphore.txt
- RCU based read-write semaphore optimized for locking for reading
perf/
- info about the APM X-Gene SoC Performance Monitoring Unit (PMU).
phy/
- ino on Samsung USB 2.0 PHY adaptation layer.
phy.txt
- Description of the generic PHY framework.
pi-futex.txt
- documentation on lightweight priority inheritance futexes.
pinctrl.txt
- info on pinctrl subsystem and the PINMUX/PINCONF and drivers
platform/
- List of supported hardware by compal and Dell laptop.
pnp.txt
- Linux Plug and Play documentation.
power/
......@@ -372,14 +352,16 @@ preempt-locking.txt
- info on locking under a preemptive kernel.
printk-formats.txt
- how to get printk format specifiers right
process/
- how to work with the mainline kernel development process.
pps/
- directory with information on the pulse-per-second support
pti/
- directory with info on Intel MID PTI.
ptp/
- directory with info on support for IEEE 1588 PTP clocks in Linux.
pwm.txt
- info on the pulse width modulation driver subsystem
ramoops.txt
- documentation of the ramoops oops/panic logging module.
rapidio/
- directory with info on RapidIO packet-based fabric interconnect
rbtree.txt
......@@ -406,8 +388,6 @@ security/
- directory that contains security-related info
serial/
- directory with info on the low level serial API.
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.
sh/
......@@ -416,24 +396,20 @@ smsc_ece1099.txt
-info on the smsc Keyboard Scan Expansion/GPIO Expansion device.
sound/
- directory with info on sound card support.
sparse.txt
- info on how to obtain and use the sparse tool for typechecking.
spi/
- overview of Linux kernel Serial Peripheral Interface (SPI) support.
stable_api_nonsense.txt
- info on why the kernel does not have a stable in-kernel api or abi.
stable_kernel_rules.txt
- rules and procedures for the -stable kernel releases.
sphinx/
- no documentation here, just files required by Sphinx toolchain.
sphinx-static/
- no documentation here, just files required by Sphinx toolchain.
static-keys.txt
- info on how static keys allow debug code in hotpaths via patching
svga.txt
- short guide on selecting video modes at boot via VGA BIOS.
sysfs-rules.txt
- How not to use sysfs.
sync_file.txt
- Sync file API guide.
sysctl/
- directory with info on the /proc/sys/* files.
sysrq.txt
- info on the magic SysRq key.
target/
- directory with info on generating TCM v4 fabric .ko modules
this_cpu_ops.txt
......@@ -442,39 +418,29 @@ thermal/
- directory with information on managing thermal issues (CPU/temp)
trace/
- directory with info on tracing technologies within linux
translations/
- translations of this document from English to another language
unaligned-memory-access.txt
- info on how to avoid arch breaking unaligned memory access in code.
unicode.txt
- info on the Unicode character/font mapping used in Linux.
unshare.txt
- description of the Linux unshare system call.
usb/
- directory with info regarding the Universal Serial Bus.
vDSO/
- directory with info regarding virtual dynamic shared objects
vfio.txt
- info on Virtual Function I/O used in guest/hypervisor instances.
vgaarbiter.txt
- info on enable/disable the legacy decoding on different VGA devices
video-output.txt
- sysfs class driver interface to enable/disable a video output device.
video4linux/
- directory with info regarding video/TV/radio cards and linux.
virtual/
- directory with information on the various linux virtualizations.
vm/
- directory with info on the Linux vm code.
vme_api.txt
- file relating info on the VME bus API in linux
volatile-considered-harmful.txt
- Why the "volatile" type class should not be used
w1/
- directory with documents regarding the 1-wire (w1) subsystem.
watchdog/
- how to auto-reboot Linux if it has "fallen and can't get up". ;-)
wimax/
- directory with info about Intel Wireless Wimax Connections
workqueue.txt
core-api/workqueue.rst
- information on the Concurrency Managed Workqueue implementation
x86/x86_64/
- directory with info on Linux support for AMD x86-64 (Hammer) machines.
......@@ -484,7 +450,5 @@ xtensa/
- directory with documents relating to arch/xtensa port/implementation
xz.txt
- how to make use of the XZ data compression within linux kernel
zh_CN/
- directory with Chinese translations of various documents
zorro.txt
- info on writing drivers for Zorro bus devices found on Amigas.
Documentation/80211/conf.py 已删除 100644 → 0
浏览文件 @ f6fa11a3
# -*- coding: utf-8; mode: python -*-
project = "Linux 802.11 Driver Developer's Guide"
tags.add("subproject")
Documentation/80211/index.rst 已删除 100644 → 0
浏览文件 @ f6fa11a3
=====================================
Linux 802.11 Driver Developer's Guide
=====================================
.. toctree::
introduction
cfg80211
mac80211
mac80211-advanced
.. only:: subproject
Indices
=======
* :ref:`genindex`
Documentation/ABI/README
浏览文件 @ dbbc21bb
......@@ -84,4 +84,4 @@ stable:
- Kernel-internal symbols. Do not rely on the presence, absence, location, or
type of any kernel symbol, either in System.map files or the kernel binary
itself. See Documentation/stable_api_nonsense.txt.
itself. See Documentation/process/stable-api-nonsense.rst.
Documentation/ABI/stable/sysfs-devices
浏览文件 @ dbbc21bb
......@@ -8,3 +8,17 @@ Description:
Any device associated with a device-tree node will have
an of_path symlink pointing to the corresponding device
node in /sys/firmware/devicetree/
What: /sys/devices/*/devspec
Date: October 2016
Contact: Device Tree mailing list <devicetree@vger.kernel.org>
Description:
If CONFIG_OF is enabled, then this file is present. When
read, it returns full name of the device node.
What: /sys/devices/*/obppath
Date: October 2016
Contact: Device Tree mailing list <devicetree@vger.kernel.org>
Description:
If CONFIG_OF is enabled, then this file is present. When
read, it returns full name of the device node.
Documentation/ABI/testing/sysfs-block
浏览文件 @ dbbc21bb
......@@ -235,3 +235,45 @@ Description:
write_same_max_bytes is 0, write same is not supported
by the device.
What: /sys/block/<disk>/queue/write_zeroes_max_bytes
Date: November 2016
Contact: Chaitanya Kulkarni <chaitanya.kulkarni@wdc.com>
Description:
Devices that support write zeroes operation in which a
single request can be issued to zero out the range of
contiguous blocks on storage without having any payload
in the request. This can be used to optimize writing zeroes
to the devices. write_zeroes_max_bytes indicates how many
bytes can be written in a single write zeroes command. If
write_zeroes_max_bytes is 0, write zeroes is not supported
by the device.
What: /sys/block/<disk>/queue/zoned
Date: September 2016
Contact: Damien Le Moal <damien.lemoal@hgst.com>
Description:
zoned indicates if the device is a zoned block device
and the zone model of the device if it is indeed zoned.
The possible values indicated by zoned are "none" for
regular block devices and "host-aware" or "host-managed"
for zoned block devices. The characteristics of
host-aware and host-managed zoned block devices are
described in the ZBC (Zoned Block Commands) and ZAC
(Zoned Device ATA Command Set) standards. These standards
also define the "drive-managed" zone model. However,
since drive-managed zoned block devices do not support
zone commands, they will be treated as regular block
devices and zoned will report "none".
What: /sys/block/<disk>/queue/chunk_sectors
Date: September 2016
Contact: Hannes Reinecke <hare@suse.com>
Description:
chunk_sectors has different meaning depending on the type
of the disk. For a RAID device (dm-raid), chunk_sectors
indicates the size in 512B sectors of the RAID volume
stripe segment. For a zoned block device, either
host-aware or host-managed, chunk_sectors indicates the
size of 512B sectors of the zones of the device, with
the eventual exception of the last zone of the device
which may be smaller.
Documentation/ABI/testing/sysfs-bus-fsl-mc 0 → 100644
浏览文件 @ dbbc21bb
What: /sys/bus/fsl-mc/drivers/.../bind
Date: December 2016
Contact: stuart.yoder@nxp.com
Description:
Writing a device location to this file will cause
the driver to attempt to bind to the device found at
this location. The format for the location is Object.Id
and is the same as found in /sys/bus/fsl-mc/devices/.
For example:
# echo dpni.2 > /sys/bus/fsl-mc/drivers/fsl_dpaa2_eth/bind
What: /sys/bus/fsl-mc/drivers/.../unbind
Date: December 2016
Contact: stuart.yoder@nxp.com
Description:
Writing a device location to this file will cause the
driver to attempt to unbind from the device found at
this location. The format for the location is Object.Id
and is the same as found in /sys/bus/fsl-mc/devices/.
For example:
# echo dpni.2 > /sys/bus/fsl-mc/drivers/fsl_dpaa2_eth/unbind
Documentation/ABI/testing/sysfs-bus-iio
浏览文件 @ dbbc21bb
......@@ -329,6 +329,7 @@ What: /sys/bus/iio/devices/iio:deviceX/in_pressure_scale
What: /sys/bus/iio/devices/iio:deviceX/in_humidityrelative_scale
What: /sys/bus/iio/devices/iio:deviceX/in_velocity_sqrt(x^2+y^2+z^2)_scale
What: /sys/bus/iio/devices/iio:deviceX/in_illuminance_scale
What: /sys/bus/iio/devices/iio:deviceX/in_countY_scale
KernelVersion: 2.6.35
Contact: linux-iio@vger.kernel.org
Description:
......@@ -1579,3 +1580,20 @@ Contact: linux-iio@vger.kernel.org
Description:
Raw (unscaled no offset etc.) electric conductivity reading that
can be processed to siemens per meter.
What: /sys/bus/iio/devices/iio:deviceX/in_countY_raw
KernelVersion: 4.9
Contact: linux-iio@vger.kernel.org
Description:
Raw counter device counts from channel Y. For quadrature
counters, multiplication by an available [Y]_scale results in
the counts of a single quadrature signal phase from channel Y.
What: /sys/bus/iio/devices/iio:deviceX/in_indexY_raw
KernelVersion: 4.9
Contact: linux-iio@vger.kernel.org
Description:
Raw counter device index value from channel Y. This attribute
provides an absolute positional reference (e.g. a pulse once per
revolution) which may be used to home positional systems as
required.
Documentation/ABI/testing/sysfs-bus-iio-adc-envelope-detector 0 → 100644
浏览文件 @ dbbc21bb
What: /sys/bus/iio/devices/iio:deviceX/in_altvoltageY_invert
Date: October 2016
KernelVersion: 4.9
Contact: Peter Rosin <peda@axentia.se>
Description:
The DAC is used to find the peak level of an alternating
voltage input signal by a binary search using the output
of a comparator wired to an interrupt pin. Like so:
_
| \
input +------>-------|+ \
| \
.-------. | }---.
| | | / |
| dac|-->--|- / |
| | |_/ |
| | |
| | |
| irq|------<-------'
| |
'-------'
The boolean invert attribute (0/1) should be set when the
input signal is centered around the maximum value of the
dac instead of zero. The envelope detector will search
from below in this case and will also invert the result.
The edge/level of the interrupt is also switched to its
opposite value.
What: /sys/bus/iio/devices/iio:deviceX/in_altvoltageY_compare_interval
Date: October 2016
KernelVersion: 4.9
Contact: Peter Rosin <peda@axentia.se>
Description:
Number of milliseconds to wait for the comparator in each
step of the binary search for the input peak level. Needs
to relate to the frequency of the input signal.
Documentation/ABI/testing/sysfs-bus-iio-counter-104-quad-8 0 → 100644
浏览文件 @ dbbc21bb
What: /sys/bus/iio/devices/iio:deviceX/in_count_count_direction_available
What: /sys/bus/iio/devices/iio:deviceX/in_count_count_mode_available
What: /sys/bus/iio/devices/iio:deviceX/in_count_noise_error_available
What: /sys/bus/iio/devices/iio:deviceX/in_count_quadrature_mode_available
What: /sys/bus/iio/devices/iio:deviceX/in_index_index_polarity_available
What: /sys/bus/iio/devices/iio:deviceX/in_index_synchronous_mode_available
KernelVersion: 4.9
Contact: linux-iio@vger.kernel.org
Description:
Discrete set of available values for the respective counter
configuration are listed in this file.
What: /sys/bus/iio/devices/iio:deviceX/in_countY_count_direction
KernelVersion: 4.9
Contact: linux-iio@vger.kernel.org
Description:
Read-only attribute that indicates whether the counter for
channel Y is counting up or down.
What: /sys/bus/iio/devices/iio:deviceX/in_countY_count_mode
KernelVersion: 4.9
Contact: linux-iio@vger.kernel.org
Description:
Count mode for channel Y. Four count modes are available:
normal, range limit, non-recycle, and modulo-n. The preset value
for channel Y is used by the count mode where required.
Normal:
Counting is continuous in either direction.
Range Limit:
An upper or lower limit is set, mimicking limit switches
in the mechanical counterpart. The upper limit is set to
the preset value, while the lower limit is set to 0. The
counter freezes at count = preset when counting up, and
at count = 0 when counting down. At either of these
limits, the counting is resumed only when the count
direction is reversed.
Non-recycle:
Counter is disabled whenever a 24-bit count overflow or
underflow takes place. The counter is re-enabled when a
new count value is loaded to the counter via a preset
operation or write to raw.
Modulo-N:
A count boundary is set between 0 and the preset value.
The counter is reset to 0 at count = preset when
counting up, while the counter is set to the preset
value at count = 0 when counting down; the counter does
not freeze at the bundary points, but counts
continuously throughout.
What: /sys/bus/iio/devices/iio:deviceX/in_countY_noise_error
KernelVersion: 4.9
Contact: linux-iio@vger.kernel.org
Description:
Read-only attribute that indicates whether excessive noise is
present at the channel Y count inputs in quadrature clock mode;
irrelevant in non-quadrature clock mode.
What: /sys/bus/iio/devices/iio:deviceX/in_countY_preset
KernelVersion: 4.9
Contact: linux-iio@vger.kernel.org
Description:
If the counter device supports preset registers, the preset
count for channel Y is provided by this attribute.
What: /sys/bus/iio/devices/iio:deviceX/in_countY_quadrature_mode
KernelVersion: 4.9
Contact: linux-iio@vger.kernel.org
Description:
Configure channel Y counter for non-quadrature or quadrature
clock mode. Selecting non-quadrature clock mode will disable
synchronous load mode. In quadrature clock mode, the channel Y
scale attribute selects the encoder phase division (scale of 1
selects full-cycle, scale of 0.5 selects half-cycle, scale of
0.25 selects quarter-cycle) processed by the channel Y counter.
Non-quadrature:
The filter and decoder circuit are bypassed. Encoder A
input serves as the count input and B as the UP/DOWN
direction control input, with B = 1 selecting UP Count
mode and B = 0 selecting Down Count mode.
Quadrature:
Encoder A and B inputs are digitally filtered and
decoded for UP/DN clock.
What: /sys/bus/iio/devices/iio:deviceX/in_countY_set_to_preset_on_index
KernelVersion: 4.9
Contact: linux-iio@vger.kernel.org
Description:
Whether to set channel Y counter with channel Y preset value
when channel Y index input is active, or continuously count.
Valid attribute values are boolean.
What: /sys/bus/iio/devices/iio:deviceX/in_indexY_index_polarity
KernelVersion: 4.9
Contact: linux-iio@vger.kernel.org
Description:
Active level of channel Y index input; irrelevant in
non-synchronous load mode.
What: /sys/bus/iio/devices/iio:deviceX/in_indexY_synchronous_mode
KernelVersion: 4.9
Contact: linux-iio@vger.kernel.org
Description:
Configure channel Y counter for non-synchronous or synchronous
load mode. Synchronous load mode cannot be selected in
non-quadrature clock mode.
Non-synchronous:
A logic low level is the active level at this index
input. The index function (as enabled via
set_to_preset_on_index) is performed directly on the
active level of the index input.
Synchronous:
Intended for interfacing with encoder Index output in
quadrature clock mode. The active level is configured
via index_polarity. The index function (as enabled via
set_to_preset_on_index) is performed synchronously with
the quadrature clock on the active level of the index
input.
Documentation/ABI/testing/sysfs-bus-iio-cros-ec 0 → 100644
浏览文件 @ dbbc21bb
What: /sys/bus/iio/devices/iio:deviceX/calibrate
Date: July 2015
KernelVersion: 4.7
Contact: linux-iio@vger.kernel.org
Description:
Writing '1' will perform a FOC (Fast Online Calibration). The
corresponding calibration offsets can be read from *_calibbias
entries.
What: /sys/bus/iio/devices/iio:deviceX/location
Date: July 2015
KernelVersion: 4.7
Contact: linux-iio@vger.kernel.org
Description:
This attribute returns a string with the physical location where
the motion sensor is placed. For example, in a laptop a motion
sensor can be located on the base or on the lid. Current valid
values are 'base' and 'lid'.
Documentation/ABI/testing/sysfs-bus-iio-dac-dpot-dac 0 → 100644
浏览文件 @ dbbc21bb
What: /sys/bus/iio/devices/iio:deviceX/out_voltageY_raw_available
Date: October 2016
KernelVersion: 4.9
Contact: Peter Rosin <peda@axentia.se>
Description:
The range of available values represented as the minimum value,
the step and the maximum value, all enclosed in square brackets.
Example: [0 1 256]
Documentation/ABI/testing/sysfs-bus-iio-light-isl29018 0 → 100644
浏览文件 @ dbbc21bb
What: /sys/bus/iio/devices/iio:deviceX/proximity_on_chip_ambient_infrared_suppression
Date: January 2011
KernelVersion: 2.6.37
Contact: linux-iio@vger.kernel.org
Description:
From ISL29018 Data Sheet (FN6619.4, Oct 8, 2012) regarding the
infrared suppression:
Scheme 0, makes full n (4, 8, 12, 16) bits (unsigned) proximity
detection. The range of Scheme 0 proximity count is from 0 to
2^n. Logic 1 of this bit, Scheme 1, makes n-1 (3, 7, 11, 15)
bits (2's complementary) proximity_less_ambient detection. The
range of Scheme 1 proximity count is from -2^(n-1) to 2^(n-1).
The sign bit is extended for resolutions less than 16. While
Scheme 0 has wider dynamic range, Scheme 1 proximity detection
is less affected by the ambient IR noise variation.
0 Sensing IR from LED and ambient
1 Sensing IR from LED with ambient IR rejection
Documentation/ABI/testing/sysfs-bus-iio-light-tsl2583 0 → 100644
浏览文件 @ dbbc21bb
What: /sys/bus/iio/devices/device[n]/in_illuminance_calibrate
KernelVersion: 2.6.37
Contact: linux-iio@vger.kernel.org
Description:
This property causes an internal calibration of the als gain trim
value which is later used in calculating illuminance in lux.
What: /sys/bus/iio/devices/device[n]/in_illuminance_lux_table
KernelVersion: 2.6.37
Contact: linux-iio@vger.kernel.org
Description:
This property gets/sets the table of coefficients
used in calculating illuminance in lux.
What: /sys/bus/iio/devices/device[n]/in_illuminance_input_target
KernelVersion: 2.6.37
Contact: linux-iio@vger.kernel.org
Description:
This property is the known externally illuminance (in lux).
It is used in the process of calibrating the device accuracy.
Documentation/ABI/testing/sysfs-bus-iio-potentiometer-mcp4531 0 → 100644
浏览文件 @ dbbc21bb
What: /sys/bus/iio/devices/iio:deviceX/out_resistance_raw_available
Date: October 2016
KernelVersion: 4.9
Contact: Peter Rosin <peda@axentia.se>
Description:
The range of available values represented as the minimum value,
the step and the maximum value, all enclosed in square brackets.
Example: [0 1 256]
Documentation/ABI/testing/sysfs-bus-pci
浏览文件 @ dbbc21bb
......@@ -294,3 +294,10 @@ Description:
a firmware bug to the system vendor. Writing to this file
taints the kernel with TAINT_FIRMWARE_WORKAROUND, which
reduces the supportability of your system.
What: /sys/bus/pci/devices/.../revision
Date: November 2016
Contact: Emil Velikov <emil.l.velikov@gmail.com>
Description:
This file contains the revision field of the the PCI device.
The value comes from device config space. The file is read only.
Documentation/ABI/testing/sysfs-bus-vfio-mdev 0 → 100644
浏览文件 @ dbbc21bb
What: /sys/.../<device>/mdev_supported_types/
Date: October 2016
Contact: Kirti Wankhede <kwankhede@nvidia.com>
Description:
This directory contains list of directories of currently
supported mediated device types and their details for
<device>. Supported type attributes are defined by the
vendor driver who registers with Mediated device framework.
Each supported type is a directory whose name is created
by adding the device driver string as a prefix to the
string provided by the vendor driver.
What: /sys/.../<device>/mdev_supported_types/<type-id>/
Date: October 2016
Contact: Kirti Wankhede <kwankhede@nvidia.com>
Description:
This directory gives details of supported type, like name,
description, available_instances, device_api etc.
'device_api' and 'available_instances' are mandatory
attributes to be provided by vendor driver. 'name',
'description' and other vendor driver specific attributes
are optional.
What: /sys/.../mdev_supported_types/<type-id>/create
Date: October 2016
Contact: Kirti Wankhede <kwankhede@nvidia.com>
Description:
Writing UUID to this file will create mediated device of
type <type-id> for parent device <device>. This is a
write-only file.
For example:
# echo "83b8f4f2-509f-382f-3c1e-e6bfe0fa1001" > \
/sys/devices/foo/mdev_supported_types/foo-1/create
What: /sys/.../mdev_supported_types/<type-id>/devices/
Date: October 2016
Contact: Kirti Wankhede <kwankhede@nvidia.com>
Description:
This directory contains symbolic links pointing to mdev
devices sysfs entries which are created of this <type-id>.
What: /sys/.../mdev_supported_types/<type-id>/available_instances
Date: October 2016
Contact: Kirti Wankhede <kwankhede@nvidia.com>
Description:
Reading this attribute will show the number of mediated
devices of type <type-id> that can be created. This is a
readonly file.
Users:
Userspace applications interested in creating mediated
device of that type. Userspace application should check
the number of available instances could be created before
creating mediated device of this type.
What: /sys/.../mdev_supported_types/<type-id>/device_api
Date: October 2016
Contact: Kirti Wankhede <kwankhede@nvidia.com>
Description:
Reading this attribute will show VFIO device API supported
by this type. For example, "vfio-pci" for a PCI device,
"vfio-platform" for platform device.
What: /sys/.../mdev_supported_types/<type-id>/name
Date: October 2016
Contact: Kirti Wankhede <kwankhede@nvidia.com>
Description:
Reading this attribute will show human readable name of the
mediated device that will get created of type <type-id>.
This is optional attribute. For example: "Grid M60-0Q"
Users:
Userspace applications interested in knowing the name of
a particular <type-id> that can help in understanding the
type of mediated device.
What: /sys/.../mdev_supported_types/<type-id>/description
Date: October 2016
Contact: Kirti Wankhede <kwankhede@nvidia.com>
Description:
Reading this attribute will show description of the type of
mediated device that will get created of type <type-id>.
This is optional attribute. For example:
"2 heads, 512M FB, 2560x1600 maximum resolution"
Users:
Userspace applications interested in knowing the details of
a particular <type-id> that can help in understanding the
features provided by that type of mediated device.
What: /sys/.../<device>/<UUID>/
Date: October 2016
Contact: Kirti Wankhede <kwankhede@nvidia.com>
Description:
This directory represents device directory of mediated
device. It contains all the attributes related to mediated
device.
What: /sys/.../<device>/<UUID>/mdev_type
Date: October 2016
Contact: Kirti Wankhede <kwankhede@nvidia.com>
Description:
This is symbolic link pointing to supported type, <type-id>
directory of which this mediated device is created.
What: /sys/.../<device>/<UUID>/remove
Date: October 2016
Contact: Kirti Wankhede <kwankhede@nvidia.com>
Description:
Writing '1' to this file destroys the mediated device. The
vendor driver can fail the remove() callback if that device
is active and the vendor driver doesn't support hot unplug.
Example:
# echo 1 > /sys/bus/mdev/devices/<UUID>/remove
Documentation/ABI/testing/sysfs-class-fpga-bridge 0 → 100644
浏览文件 @ dbbc21bb
What: /sys/class/fpga_bridge/<bridge>/name
Date: January 2016
KernelVersion: 4.5
Contact: Alan Tull <atull@opensource.altera.com>
Description: Name of low level FPGA bridge driver.
What: /sys/class/fpga_bridge/<bridge>/state
Date: January 2016
KernelVersion: 4.5
Contact: Alan Tull <atull@opensource.altera.com>
Description: Show bridge state as "enabled" or "disabled"
Documentation/ABI/testing/sysfs-class-led
浏览文件 @ dbbc21bb
......@@ -4,16 +4,24 @@ KernelVersion: 2.6.17
Contact: Richard Purdie <rpurdie@rpsys.net>
Description:
Set the brightness of the LED. Most LEDs don't
have hardware brightness support so will just be turned on for
have hardware brightness support, so will just be turned on for
non-zero brightness settings. The value is between 0 and
/sys/class/leds/<led>/max_brightness.
Writing 0 to this file clears active trigger.
Writing non-zero to this file while trigger is active changes the
top brightness trigger is going to use.
What: /sys/class/leds/<led>/max_brightness
Date: March 2006
KernelVersion: 2.6.17
Contact: Richard Purdie <rpurdie@rpsys.net>
Description:
Maximum brightness level for this led, default is 255 (LED_FULL).
Maximum brightness level for this LED, default is 255 (LED_FULL).
If the LED does not support different brightness levels, this
should be 1.
What: /sys/class/leds/<led>/trigger
Date: March 2006
......@@ -21,7 +29,7 @@ KernelVersion: 2.6.17
Contact: Richard Purdie <rpurdie@rpsys.net>
Description:
Set the trigger for this LED. A trigger is a kernel based source
of led events.
of LED events.
You can change triggers in a similar manner to the way an IO
scheduler is chosen. Trigger specific parameters can appear in
/sys/class/leds/<led> once a given trigger is selected. For
......
Documentation/ABI/testing/sysfs-class-mei
浏览文件 @ dbbc21bb
......@@ -29,3 +29,19 @@ Description: Display fw status registers content
Also number of registers varies between 1 and 6
depending on generation.
What: /sys/class/mei/meiN/hbm_ver
Date: Aug 2016
KernelVersion: 4.9
Contact: Tomas Winkler <tomas.winkler@intel.com>
Description: Display the negotiated HBM protocol version.
The HBM protocol version negotiated
between the driver and the device.
What: /sys/class/mei/meiN/hbm_ver_drv
Date: Aug 2016
KernelVersion: 4.9
Contact: Tomas Winkler <tomas.winkler@intel.com>
Description: Display the driver HBM protocol version.
The HBM protocol version supported by the driver.
Documentation/ABI/testing/sysfs-class-remoteproc 0 → 100644
浏览文件 @ dbbc21bb
What: /sys/class/remoteproc/.../firmware
Date: October 2016
Contact: Matt Redfearn <matt.redfearn@imgtec.com>
Description: Remote processor firmware
Reports the name of the firmware currently loaded to the
remote processor.
To change the running firmware, ensure the remote processor is
stopped (using /sys/class/remoteproc/.../state) and write a new filename.
What: /sys/class/remoteproc/.../state
Date: October 2016
Contact: Matt Redfearn <matt.redfearn@imgtec.com>
Description: Remote processor state
Reports the state of the remote processor, which will be one of:
"offline"
"suspended"
"running"
"crashed"
"invalid"
"offline" means the remote processor is powered off.
"suspended" means that the remote processor is suspended and
must be woken to receive messages.
"running" is the normal state of an available remote processor
"crashed" indicates that a problem/crash has been detected on
the remote processor.
"invalid" is returned if the remote processor is in an
unknown state.
Writing this file controls the state of the remote processor.
The following states can be written:
"start"
"stop"
Writing "start" will attempt to start the processor running the
firmware indicated by, or written to,
/sys/class/remoteproc/.../firmware. The remote processor should
transition to "running" state.
Writing "stop" will attempt to halt the remote processor and
return it to the "offline" state.
Documentation/ABI/testing/sysfs-class-rtc-rtc0-device-rtc_calibration
浏览文件 @ dbbc21bb
What: Attribute for calibrating ST-Ericsson AB8500 Real Time Clock
What: /sys/class/rtc/rtc0/device/rtc_calibration
Date: Oct 2011
KernelVersion: 3.0
Contact: Mark Godfrey <mark.godfrey@stericsson.com>
Description: The rtc_calibration attribute allows the userspace to
Description: Attribute for calibrating ST-Ericsson AB8500 Real Time Clock
The rtc_calibration attribute allows the userspace to
calibrate the AB8500.s 32KHz Real Time Clock.
Every 60 seconds the AB8500 will correct the RTC's value
by adding to it the value of this attribute.
......
Documentation/ABI/testing/sysfs-devices-deferred_probe 0 → 100644
浏览文件 @ dbbc21bb
What: /sys/devices/.../deferred_probe
Date: August 2016
Contact: Ben Hutchings <ben.hutchings@codethink.co.uk>
Description:
The /sys/devices/.../deferred_probe attribute is
present for all devices. If a driver detects during
probing a device that a related device is not yet
ready, it may defer probing of the first device. The
kernel will retry probing the first device after any
other device is successfully probed. This attribute
reads as 1 if probing of this device is currently
deferred, or 0 otherwise.
Documentation/ABI/testing/sysfs-devices-system-cpu
浏览文件 @ dbbc21bb
......@@ -272,6 +272,22 @@ Description: Parameters for the CPU cache attributes
the modified cache line is written to main
memory only when it is replaced
What: /sys/devices/system/cpu/cpu*/cache/index*/id
Date: September 2016
Contact: Linux kernel mailing list <linux-kernel@vger.kernel.org>
Description: Cache id
The id provides a unique number for a specific instance of
a cache of a particular type. E.g. there may be a level
3 unified cache on each socket in a server and we may
assign them ids 0, 1, 2, ...
Note that id value can be non-contiguous. E.g. level 1
caches typically exist per core, but there may not be a
power of two cores on a socket, so these caches may be
numbered 0, 1, 2, 3, 4, 5, 8, 9, 10, ...
What: /sys/devices/system/cpu/cpuX/cpufreq/throttle_stats
/sys/devices/system/cpu/cpuX/cpufreq/throttle_stats/turbo_stat
/sys/devices/system/cpu/cpuX/cpufreq/throttle_stats/sub_turbo_stat
......
Documentation/ABI/testing/sysfs-kernel-slab
浏览文件 @ dbbc21bb
......@@ -347,7 +347,7 @@ Description:
because of fragmentation, SLUB will retry with the minimum order
possible depending on its characteristics.
When debug_guardpage_minorder=N (N > 0) parameter is specified
(see Documentation/kernel-parameters.txt), the minimum possible
(see Documentation/admin-guide/kernel-parameters.rst), the minimum possible
order is used and this sysfs entry can not be used to change
the order at run time.
......
Documentation/ABI/testing/sysfs-platform-phy-rcar-gen3-usb2 0 → 100644
浏览文件 @ dbbc21bb
What: /sys/devices/platform/<phy-name>/role
Date: October 2016
KernelVersion: 4.10
Contact: Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>
Description:
This file can be read and write.
The file can show/change the phy mode for role swap of usb.
Write the following strings to change the mode:
"host" - switching mode from peripheral to host.
"peripheral" - switching mode from host to peripheral.
Read the file, then it shows the following strings:
"host" - The mode is host now.
"peripheral" - The mode is peripheral now.
Documentation/ABI/testing/sysfs-power
浏览文件 @ dbbc21bb
......@@ -7,30 +7,35 @@ Description:
subsystem.
What: /sys/power/state
Date: May 2014
Date: November 2016
Contact: Rafael J. Wysocki <rjw@rjwysocki.net>
Description:
The /sys/power/state file controls system sleep states.
Reading from this file returns the available sleep state
labels, which may be "mem", "standby", "freeze" and "disk"
(hibernation). The meanings of the first three labels depend on
the relative_sleep_states command line argument as follows:
1) relative_sleep_states = 1
"mem", "standby", "freeze" represent non-hibernation sleep
states from the deepest ("mem", always present) to the
shallowest ("freeze"). "standby" and "freeze" may or may
not be present depending on the capabilities of the
platform. "freeze" can only be present if "standby" is
present.
2) relative_sleep_states = 0 (default)
"mem" - "suspend-to-RAM", present if supported.
"standby" - "power-on suspend", present if supported.
"freeze" - "suspend-to-idle", always present.
Writing to this file one of these strings causes the system to
transition into the corresponding state, if available. See
Documentation/power/states.txt for a description of what
"suspend-to-RAM", "power-on suspend" and "suspend-to-idle" mean.
labels, which may be "mem" (suspend), "standby" (power-on
suspend), "freeze" (suspend-to-idle) and "disk" (hibernation).
Writing one of the above strings to this file causes the system
to transition into the corresponding state, if available.
See Documentation/power/states.txt for more information.
What: /sys/power/mem_sleep
Date: November 2016
Contact: Rafael J. Wysocki <rjw@rjwysocki.net>
Description:
The /sys/power/mem_sleep file controls the operating mode of
system suspend. Reading from it returns the available modes
as "s2idle" (always present), "shallow" and "deep" (present if
supported). The mode that will be used on subsequent attempts
to suspend the system (by writing "mem" to the /sys/power/state
file described above) is enclosed in square brackets.
Writing one of the above strings to this file causes the mode
represented by it to be used on subsequent attempts to suspend
the system.
See Documentation/power/states.txt for more information.
What: /sys/power/disk
Date: September 2006
......
Documentation/BUG-HUNTING 已删除 100644 → 0
浏览文件 @ f6fa11a3
Table of contents
=================
Last updated: 20 December 2005
Contents
========
- Introduction
- Devices not appearing
- Finding patch that caused a bug
-- Finding using git-bisect
-- Finding it the old way
- Fixing the bug
Introduction
============
Always try the latest kernel from kernel.org and build from source. If you are
not confident in doing that please report the bug to your distribution vendor
instead of to a kernel developer.
Finding bugs is not always easy. Have a go though. If you can't find it don't
give up. Report as much as you have found to the relevant maintainer. See
MAINTAINERS for who that is for the subsystem you have worked on.
Before you submit a bug report read REPORTING-BUGS.
Devices not appearing
=====================
Often this is caused by udev. Check that first before blaming it on the
kernel.
Finding patch that caused a bug
===============================
Finding using git-bisect
------------------------
Using the provided tools with git makes finding bugs easy provided the bug is
reproducible.
Steps to do it:
- start using git for the kernel source
- read the man page for git-bisect
- have fun
Finding it the old way
----------------------
[Sat Mar 2 10:32:33 PST 1996 KERNEL_BUG-HOWTO lm@sgi.com (Larry McVoy)]
This is how to track down a bug if you know nothing about kernel hacking.
It's a brute force approach but it works pretty well.
You need:
. A reproducible bug - it has to happen predictably (sorry)
. All the kernel tar files from a revision that worked to the
revision that doesn't
You will then do:
. Rebuild a revision that you believe works, install, and verify that.
. Do a binary search over the kernels to figure out which one
introduced the bug. I.e., suppose 1.3.28 didn't have the bug, but
you know that 1.3.69 does. Pick a kernel in the middle and build
that, like 1.3.50. Build & test; if it works, pick the mid point
between .50 and .69, else the mid point between .28 and .50.
. You'll narrow it down to the kernel that introduced the bug. You
can probably do better than this but it gets tricky.
. Narrow it down to a subdirectory
- Copy kernel that works into "test". Let's say that 3.62 works,
but 3.63 doesn't. So you diff -r those two kernels and come
up with a list of directories that changed. For each of those
directories:
Copy the non-working directory next to the working directory
as "dir.63".
One directory at time, try moving the working directory to
"dir.62" and mv dir.63 dir"time, try
mv dir dir.62
mv dir.63 dir
find dir -name '*.[oa]' -print | xargs rm -f
And then rebuild and retest. Assuming that all related
changes were contained in the sub directory, this should
isolate the change to a directory.
Problems: changes in header files may have occurred; I've
found in my case that they were self explanatory - you may
or may not want to give up when that happens.
. Narrow it down to a file
- You can apply the same technique to each file in the directory,
hoping that the changes in that file are self contained.
. Narrow it down to a routine
- You can take the old file and the new file and manually create
a merged file that has
#ifdef VER62
routine()
{
...
}
#else
routine()
{
...
}
#endif
And then walk through that file, one routine at a time and
prefix it with
#define VER62
/* both routines here */
#undef VER62
Then recompile, retest, move the ifdefs until you find the one
that makes the difference.
Finally, you take all the info that you have, kernel revisions, bug
description, the extent to which you have narrowed it down, and pass
that off to whomever you believe is the maintainer of that section.
A post to linux.dev.kernel isn't such a bad idea if you've done some
work to narrow it down.
If you get it down to a routine, you'll probably get a fix in 24 hours.
My apologies to Linus and the other kernel hackers for describing this
brute force approach, it's hardly what a kernel hacker would do. However,
it does work and it lets non-hackers help fix bugs. And it is cool
because Linux snapshots will let you do this - something that you can't
do with vendor supplied releases.
Fixing the bug
==============
Nobody is going to tell you how to fix bugs. Seriously. You need to work it
out. But below are some hints on how to use the tools.
To debug a kernel, use objdump and look for the hex offset from the crash
output to find the valid line of code/assembler. Without debug symbols, you
will see the assembler code for the routine shown, but if your kernel has
debug symbols the C code will also be available. (Debug symbols can be enabled
in the kernel hacking menu of the menu configuration.) For example:
objdump -r -S -l --disassemble net/dccp/ipv4.o
NB.: you need to be at the top level of the kernel tree for this to pick up
your C files.
If you don't have access to the code you can also debug on some crash dumps
e.g. crash dump output as shown by Dave Miller.
> EIP is at ip_queue_xmit+0x14/0x4c0
> ...
> Code: 44 24 04 e8 6f 05 00 00 e9 e8 fe ff ff 8d 76 00 8d bc 27 00 00
> 00 00 55 57 56 53 81 ec bc 00 00 00 8b ac 24 d0 00 00 00 8b 5d 08
> <8b> 83 3c 01 00 00 89 44 24 14 8b 45 28 85 c0 89 44 24 18 0f 85
>
> Put the bytes into a "foo.s" file like this:
>
> .text
> .globl foo
> foo:
> .byte .... /* bytes from Code: part of OOPS dump */
>
> Compile it with "gcc -c -o foo.o foo.s" then look at the output of
> "objdump --disassemble foo.o".
>
> Output:
>
> ip_queue_xmit:
> push %ebp
> push %edi
> push %esi
> push %ebx
> sub $0xbc, %esp
> mov 0xd0(%esp), %ebp ! %ebp = arg0 (skb)
> mov 0x8(%ebp), %ebx ! %ebx = skb->sk
> mov 0x13c(%ebx), %eax ! %eax = inet_sk(sk)->opt
In addition, you can use GDB to figure out the exact file and line
number of the OOPS from the vmlinux file. If you have
CONFIG_DEBUG_INFO enabled, you can simply copy the EIP value from the
OOPS:
EIP: 0060:[<c021e50e>] Not tainted VLI
And use GDB to translate that to human-readable form:
gdb vmlinux
(gdb) l *0xc021e50e
If you don't have CONFIG_DEBUG_INFO enabled, you use the function
offset from the OOPS:
EIP is at vt_ioctl+0xda8/0x1482
And recompile the kernel with CONFIG_DEBUG_INFO enabled:
make vmlinux
gdb vmlinux
(gdb) p vt_ioctl
(gdb) l *(0x<address of vt_ioctl> + 0xda8)
or, as one command
(gdb) l *(vt_ioctl + 0xda8)
If you have a call trace, such as :-
>Call Trace:
> [<ffffffff8802c8e9>] :jbd:log_wait_commit+0xa3/0xf5
> [<ffffffff810482d9>] autoremove_wake_function+0x0/0x2e
> [<ffffffff8802770b>] :jbd:journal_stop+0x1be/0x1ee
> ...
this shows the problem in the :jbd: module. You can load that module in gdb
and list the relevant code.
gdb fs/jbd/jbd.ko
(gdb) p log_wait_commit
(gdb) l *(0x<address> + 0xa3)
or
(gdb) l *(log_wait_commit + 0xa3)
Another very useful option of the Kernel Hacking section in menuconfig is
Debug memory allocations. This will help you see whether data has been
initialised and not set before use etc. To see the values that get assigned
with this look at mm/slab.c and search for POISON_INUSE. When using this an
Oops will often show the poisoned data instead of zero which is the default.
Once you have worked out a fix please submit it upstream. After all open
source is about sharing what you do and don't you want to be recognised for
your genius?
Please do read Documentation/SubmittingPatches though to help your code get
accepted.
Documentation/Changes 已删除 100644 → 0
浏览文件 @ f6fa11a3
.. _changes:
Minimal requerements to compile the Kernel
++++++++++++++++++++++++++++++++++++++++++
Intro
=====
This document is designed to provide a list of the minimum levels of
software necessary to run the 4.x kernels.
This document is originally based on my "Changes" file for 2.0.x kernels
and therefore owes credit to the same people as that file (Jared Mauch,
Axel Boldt, Alessandro Sigala, and countless other users all over the
'net).
Current Minimal Requirements
****************************
Upgrade to at **least** these software revisions before thinking you've
encountered a bug! If you're unsure what version you're currently
running, the suggested command should tell you.
Again, keep in mind that this list assumes you are already functionally
running a Linux kernel. Also, not all tools are necessary on all
systems; obviously, if you don't have any ISDN hardware, for example,
you probably needn't concern yourself with isdn4k-utils.
====================== =============== ========================================
Program Minimal version Command to check the version
====================== =============== ========================================
GNU C 3.2 gcc --version
GNU make 3.80 make --version
binutils 2.12 ld -v
util-linux 2.10o fdformat --version
module-init-tools 0.9.10 depmod -V
e2fsprogs 1.41.4 e2fsck -V
jfsutils 1.1.3 fsck.jfs -V
reiserfsprogs 3.6.3 reiserfsck -V
xfsprogs 2.6.0 xfs_db -V
squashfs-tools 4.0 mksquashfs -version
btrfs-progs 0.18 btrfsck
pcmciautils 004 pccardctl -V
quota-tools 3.09 quota -V
PPP 2.4.0 pppd --version
isdn4k-utils 3.1pre1 isdnctrl 2>&1|grep version
nfs-utils 1.0.5 showmount --version
procps 3.2.0 ps --version
oprofile 0.9 oprofiled --version
udev 081 udevd --version
grub 0.93 grub --version || grub-install --version
mcelog 0.6 mcelog --version
iptables 1.4.2 iptables -V
openssl & libcrypto 1.0.0 openssl version
bc 1.06.95 bc --version
Sphinx\ [#f1]_ 1.2 sphinx-build --version
====================== =============== ========================================
.. [#f1] Sphinx is needed only to build the Kernel documentation
Kernel compilation
******************
GCC
---
The gcc version requirements may vary depending on the type of CPU in your
computer.
Make
----
You will need GNU make 3.80 or later to build the kernel.
Binutils
--------
Linux on IA-32 has recently switched from using ``as86`` to using ``gas`` for
assembling the 16-bit boot code, removing the need for ``as86`` to compile
your kernel. This change does, however, mean that you need a recent
release of binutils.
Perl
----
You will need perl 5 and the following modules: ``Getopt::Long``,
``Getopt::Std``, ``File::Basename``, and ``File::Find`` to build the kernel.
BC
--
You will need bc to build kernels 3.10 and higher
OpenSSL
-------
Module signing and external certificate handling use the OpenSSL program and
crypto library to do key creation and signature generation.
You will need openssl to build kernels 3.7 and higher if module signing is
enabled. You will also need openssl development packages to build kernels 4.3
and higher.
System utilities
****************
Architectural changes
---------------------
DevFS has been obsoleted in favour of udev
(http://www.kernel.org/pub/linux/utils/kernel/hotplug/)
32-bit UID support is now in place. Have fun!
Linux documentation for functions is transitioning to inline
documentation via specially-formatted comments near their
definitions in the source. These comments can be combined with the
SGML templates in the Documentation/DocBook directory to make DocBook
files, which can then be converted by DocBook stylesheets to PostScript,
HTML, PDF files, and several other formats. In order to convert from
DocBook format to a format of your choice, you'll need to install Jade as
well as the desired DocBook stylesheets.
Util-linux
----------
New versions of util-linux provide ``fdisk`` support for larger disks,
support new options to mount, recognize more supported partition
types, have a fdformat which works with 2.4 kernels, and similar goodies.
You'll probably want to upgrade.
Ksymoops
--------
If the unthinkable happens and your kernel oopses, you may need the
ksymoops tool to decode it, but in most cases you don't.
It is generally preferred to build the kernel with ``CONFIG_KALLSYMS`` so
that it produces readable dumps that can be used as-is (this also
produces better output than ksymoops). If for some reason your kernel
is not build with ``CONFIG_KALLSYMS`` and you have no way to rebuild and
reproduce the Oops with that option, then you can still decode that Oops
with ksymoops.
Module-Init-Tools
-----------------
A new module loader is now in the kernel that requires ``module-init-tools``
to use. It is backward compatible with the 2.4.x series kernels.
Mkinitrd
--------
These changes to the ``/lib/modules`` file tree layout also require that
mkinitrd be upgraded.
E2fsprogs
---------
The latest version of ``e2fsprogs`` fixes several bugs in fsck and
debugfs. Obviously, it's a good idea to upgrade.
JFSutils
--------
The ``jfsutils`` package contains the utilities for the file system.
The following utilities are available:
- ``fsck.jfs`` - initiate replay of the transaction log, and check
and repair a JFS formatted partition.
- ``mkfs.jfs`` - create a JFS formatted partition.
- other file system utilities are also available in this package.
Reiserfsprogs
-------------
The reiserfsprogs package should be used for reiserfs-3.6.x
(Linux kernels 2.4.x). It is a combined package and contains working
versions of ``mkreiserfs``, ``resize_reiserfs``, ``debugreiserfs`` and
``reiserfsck``. These utils work on both i386 and alpha platforms.
Xfsprogs
--------
The latest version of ``xfsprogs`` contains ``mkfs.xfs``, ``xfs_db``, and the
``xfs_repair`` utilities, among others, for the XFS filesystem. It is
architecture independent and any version from 2.0.0 onward should
work correctly with this version of the XFS kernel code (2.6.0 or
later is recommended, due to some significant improvements).
PCMCIAutils
-----------
PCMCIAutils replaces ``pcmcia-cs``. It properly sets up
PCMCIA sockets at system startup and loads the appropriate modules
for 16-bit PCMCIA devices if the kernel is modularized and the hotplug
subsystem is used.
Quota-tools
-----------
Support for 32 bit uid's and gid's is required if you want to use
the newer version 2 quota format. Quota-tools version 3.07 and
newer has this support. Use the recommended version or newer
from the table above.
Intel IA32 microcode
--------------------
A driver has been added to allow updating of Intel IA32 microcode,
accessible as a normal (misc) character device. If you are not using
udev you may need to::
mkdir /dev/cpu
mknod /dev/cpu/microcode c 10 184
chmod 0644 /dev/cpu/microcode
as root before you can use this. You'll probably also want to
get the user-space microcode_ctl utility to use with this.
udev
----
``udev`` is a userspace application for populating ``/dev`` dynamically with
only entries for devices actually present. ``udev`` replaces the basic
functionality of devfs, while allowing persistent device naming for
devices.
FUSE
----
Needs libfuse 2.4.0 or later. Absolute minimum is 2.3.0 but mount
options ``direct_io`` and ``kernel_cache`` won't work.
Networking
**********
General changes
---------------
If you have advanced network configuration needs, you should probably
consider using the network tools from ip-route2.
Packet Filter / NAT
-------------------
The packet filtering and NAT code uses the same tools like the previous 2.4.x
kernel series (iptables). It still includes backwards-compatibility modules
for 2.2.x-style ipchains and 2.0.x-style ipfwadm.
PPP
---
The PPP driver has been restructured to support multilink and to
enable it to operate over diverse media layers. If you use PPP,
upgrade pppd to at least 2.4.0.
If you are not using udev, you must have the device file /dev/ppp
which can be made by::
mknod /dev/ppp c 108 0
as root.
Isdn4k-utils
------------
Due to changes in the length of the phone number field, isdn4k-utils
needs to be recompiled or (preferably) upgraded.
NFS-utils
---------
In ancient (2.4 and earlier) kernels, the nfs server needed to know
about any client that expected to be able to access files via NFS. This
information would be given to the kernel by ``mountd`` when the client
mounted the filesystem, or by ``exportfs`` at system startup. exportfs
would take information about active clients from ``/var/lib/nfs/rmtab``.
This approach is quite fragile as it depends on rmtab being correct
which is not always easy, particularly when trying to implement
fail-over. Even when the system is working well, ``rmtab`` suffers from
getting lots of old entries that never get removed.
With modern kernels we have the option of having the kernel tell mountd
when it gets a request from an unknown host, and mountd can give
appropriate export information to the kernel. This removes the
dependency on ``rmtab`` and means that the kernel only needs to know about
currently active clients.
To enable this new functionality, you need to::
mount -t nfsd nfsd /proc/fs/nfsd
before running exportfs or mountd. It is recommended that all NFS
services be protected from the internet-at-large by a firewall where
that is possible.
mcelog
------
On x86 kernels the mcelog utility is needed to process and log machine check
events when ``CONFIG_X86_MCE`` is enabled. Machine check events are errors
reported by the CPU. Processing them is strongly encouraged.
Kernel documentation
********************
Sphinx
------
The ReST markups currently used by the Documentation/ files are meant to be
built with ``Sphinx`` version 1.2 or upper. If you're desiring to build
PDF outputs, it is recommended to use version 1.4.6.
.. note::
Please notice that, for PDF and LaTeX output, you'll also need ``XeLaTeX``
version 3.14159265. Depending on the distribution, you may also need
to install a series of ``texlive`` packages that provide the minimal
set of functionalities required for ``XeLaTex`` to work.
Other tools
-----------
In order to produce documentation from DocBook, you'll also need ``xmlto``.
Please notice, however, that we're currently migrating all documents to use
``Sphinx``.
Getting updated software
========================
Kernel compilation
******************
gcc
---
- <ftp://ftp.gnu.org/gnu/gcc/>
Make
----
- <ftp://ftp.gnu.org/gnu/make/>
Binutils
--------
- <ftp://ftp.kernel.org/pub/linux/devel/binutils/>
OpenSSL
-------
- <https://www.openssl.org/>
System utilities
****************
Util-linux
----------
- <ftp://ftp.kernel.org/pub/linux/utils/util-linux/>
Ksymoops
--------
- <ftp://ftp.kernel.org/pub/linux/utils/kernel/ksymoops/v2.4/>
Module-Init-Tools
-----------------
- <ftp://ftp.kernel.org/pub/linux/kernel/people/rusty/modules/>
Mkinitrd
--------
- <https://code.launchpad.net/initrd-tools/main>
E2fsprogs
---------
- <http://prdownloads.sourceforge.net/e2fsprogs/e2fsprogs-1.29.tar.gz>
JFSutils
--------
- <http://jfs.sourceforge.net/>
Reiserfsprogs
-------------
- <http://www.kernel.org/pub/linux/utils/fs/reiserfs/>
Xfsprogs
--------
- <ftp://oss.sgi.com/projects/xfs/>
Pcmciautils
-----------
- <ftp://ftp.kernel.org/pub/linux/utils/kernel/pcmcia/>
Quota-tools
-----------
- <http://sourceforge.net/projects/linuxquota/>
DocBook Stylesheets
-------------------
- <http://sourceforge.net/projects/docbook/files/docbook-dsssl/>
XMLTO XSLT Frontend
-------------------
- <http://cyberelk.net/tim/xmlto/>
Intel P6 microcode
------------------
- <https://downloadcenter.intel.com/>
udev
----
- <http://www.freedesktop.org/software/systemd/man/udev.html>
FUSE
----
- <http://sourceforge.net/projects/fuse>
mcelog
------
- <http://www.mcelog.org/>
Networking
**********
PPP
---
- <ftp://ftp.samba.org/pub/ppp/>
Isdn4k-utils
------------
- <ftp://ftp.isdn4linux.de/pub/isdn4linux/utils/>
NFS-utils
---------
- <http://sourceforge.net/project/showfiles.php?group_id=14>
Iptables
--------
- <http://www.iptables.org/downloads.html>
Ip-route2
---------
- <https://www.kernel.org/pub/linux/utils/net/iproute2/>
OProfile
--------
- <http://oprofile.sf.net/download/>
NFS-Utils
---------
- <http://nfs.sourceforge.net/>
Kernel documentation
********************
Sphinx
------
- <http://www.sphinx-doc.org/>
Documentation/Changes 0 → 120000
浏览文件 @ dbbc21bb
process/changes.rst
\ No newline at end of file
Documentation/CodeOfConflict 已删除 100644 → 0
浏览文件 @ f6fa11a3
Code of Conflict
----------------
The Linux kernel development effort is a very personal process compared
to "traditional" ways of developing software. Your code and ideas
behind it will be carefully reviewed, often resulting in critique and
criticism. The review will almost always require improvements to the
code before it can be included in the kernel. Know that this happens
because everyone involved wants to see the best possible solution for
the overall success of Linux. This development process has been proven
to create the most robust operating system kernel ever, and we do not
want to do anything to cause the quality of submission and eventual
result to ever decrease.
If however, anyone feels personally abused, threatened, or otherwise
uncomfortable due to this process, that is not acceptable. If so,
please contact the Linux Foundation's Technical Advisory Board at
<tab@lists.linux-foundation.org>, or the individual members, and they
will work to resolve the issue to the best of their ability. For more
information on who is on the Technical Advisory Board and what their
role is, please see:
http://www.linuxfoundation.org/projects/linux/tab
As a reviewer of code, please strive to keep things civil and focused on
the technical issues involved. We are all humans, and frustrations can
be high on both sides of the process. Try to keep in mind the immortal
words of Bill and Ted, "Be excellent to each other."
Documentation/CodingStyle
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/DocBook/Makefile
浏览文件 @ dbbc21bb
......@@ -9,13 +9,11 @@
DOCBOOKS := z8530book.xml \
kernel-hacking.xml kernel-locking.xml deviceiobook.xml \
writing_usb_driver.xml networking.xml \
kernel-api.xml filesystems.xml lsm.xml usb.xml kgdb.xml \
kernel-api.xml filesystems.xml lsm.xml kgdb.xml \
gadget.xml libata.xml mtdnand.xml librs.xml rapidio.xml \
genericirq.xml s390-drivers.xml uio-howto.xml scsi.xml \
debugobjects.xml sh.xml regulator.xml \
alsa-driver-api.xml writing-an-alsa-driver.xml \
tracepoint.xml w1.xml \
writing_musb_glue_layer.xml crypto-API.xml iio.xml
80211.xml sh.xml regulator.xml w1.xml \
writing_musb_glue_layer.xml iio.xml
ifeq ($(DOCBOOKS),)
......@@ -264,6 +262,7 @@ clean-files := $(DOCBOOKS) \
$(patsubst %.xml, %.aux.xml, $(DOCBOOKS)) \
$(patsubst %.xml, %.xml.db, $(DOCBOOKS)) \
$(patsubst %.xml, %.xml, $(DOCBOOKS)) \
$(patsubst %.xml, .%.xml.cmd, $(DOCBOOKS)) \
$(index)
clean-dirs := $(patsubst %.xml,%,$(DOCBOOKS)) man
......
Documentation/DocBook/alsa-driver-api.tmpl 已删除 100644 → 0
浏览文件 @ f6fa11a3
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN"
"http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd" []>
<!-- ****************************************************** -->
<!-- Header -->
<!-- ****************************************************** -->
<book id="ALSA-Driver-API">
<bookinfo>
<title>The ALSA Driver API</title>
<legalnotice>
<para>
This document is free; you can redistribute it and/or modify it
under the terms of the GNU General Public License as published by
the Free Software Foundation; either version 2 of the License, or
(at your option) any later version.
</para>
<para>
This document is distributed in the hope that it will be useful,
but <emphasis>WITHOUT ANY WARRANTY</emphasis>; without even the
implied warranty of <emphasis>MERCHANTABILITY or FITNESS FOR A
PARTICULAR PURPOSE</emphasis>. See the GNU General Public License
for more details.
</para>
<para>
You should have received a copy of the GNU General Public
License along with this program; if not, write to the Free
Software Foundation, Inc., 59 Temple Place, Suite 330, Boston,
MA 02111-1307 USA
</para>
</legalnotice>
</bookinfo>
<toc></toc>
<chapter><title>Management of Cards and Devices</title>
<sect1><title>Card Management</title>
!Esound/core/init.c
</sect1>
<sect1><title>Device Components</title>
!Esound/core/device.c
</sect1>
<sect1><title>Module requests and Device File Entries</title>
!Esound/core/sound.c
</sect1>
<sect1><title>Memory Management Helpers</title>
!Esound/core/memory.c
!Esound/core/memalloc.c
</sect1>
</chapter>
<chapter><title>PCM API</title>
<sect1><title>PCM Core</title>
!Esound/core/pcm.c
!Esound/core/pcm_lib.c
!Esound/core/pcm_native.c
!Iinclude/sound/pcm.h
</sect1>
<sect1><title>PCM Format Helpers</title>
!Esound/core/pcm_misc.c
</sect1>
<sect1><title>PCM Memory Management</title>
!Esound/core/pcm_memory.c
</sect1>
<sect1><title>PCM DMA Engine API</title>
!Esound/core/pcm_dmaengine.c
!Iinclude/sound/dmaengine_pcm.h
</sect1>
</chapter>
<chapter><title>Control/Mixer API</title>
<sect1><title>General Control Interface</title>
!Esound/core/control.c
</sect1>
<sect1><title>AC97 Codec API</title>
!Esound/pci/ac97/ac97_codec.c
!Esound/pci/ac97/ac97_pcm.c
</sect1>
<sect1><title>Virtual Master Control API</title>
!Esound/core/vmaster.c
!Iinclude/sound/control.h
</sect1>
</chapter>
<chapter><title>MIDI API</title>
<sect1><title>Raw MIDI API</title>
!Esound/core/rawmidi.c
</sect1>
<sect1><title>MPU401-UART API</title>
!Esound/drivers/mpu401/mpu401_uart.c
</sect1>
</chapter>
<chapter><title>Proc Info API</title>
<sect1><title>Proc Info Interface</title>
!Esound/core/info.c
</sect1>
</chapter>
<chapter><title>Compress Offload</title>
<sect1><title>Compress Offload API</title>
!Esound/core/compress_offload.c
!Iinclude/uapi/sound/compress_offload.h
!Iinclude/uapi/sound/compress_params.h
!Iinclude/sound/compress_driver.h
</sect1>
</chapter>
<chapter><title>ASoC</title>
<sect1><title>ASoC Core API</title>
!Iinclude/sound/soc.h
!Esound/soc/soc-core.c
<!-- !Esound/soc/soc-cache.c no docbook comments here -->
!Esound/soc/soc-devres.c
!Esound/soc/soc-io.c
!Esound/soc/soc-pcm.c
!Esound/soc/soc-ops.c
!Esound/soc/soc-compress.c
</sect1>
<sect1><title>ASoC DAPM API</title>
!Esound/soc/soc-dapm.c
</sect1>
<sect1><title>ASoC DMA Engine API</title>
!Esound/soc/soc-generic-dmaengine-pcm.c
</sect1>
</chapter>
<chapter><title>Miscellaneous Functions</title>
<sect1><title>Hardware-Dependent Devices API</title>
!Esound/core/hwdep.c
</sect1>
<sect1><title>Jack Abstraction Layer API</title>
!Iinclude/sound/jack.h
!Esound/core/jack.c
!Esound/soc/soc-jack.c
</sect1>
<sect1><title>ISA DMA Helpers</title>
!Esound/core/isadma.c
</sect1>
<sect1><title>Other Helper Macros</title>
!Iinclude/sound/core.h
</sect1>
</chapter>
</book>
Documentation/DocBook/crypto-API.tmpl 已删除 100644 → 0
浏览文件 @ f6fa11a3
此差异已折叠。
Documentation/DocBook/debugobjects.tmpl 已删除 100644 → 0
浏览文件 @ f6fa11a3
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN"
"http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd" []>
<book id="debug-objects-guide">
<bookinfo>
<title>Debug objects life time</title>
<authorgroup>
<author>
<firstname>Thomas</firstname>
<surname>Gleixner</surname>
<affiliation>
<address>
<email>tglx@linutronix.de</email>
</address>
</affiliation>
</author>
</authorgroup>
<copyright>
<year>2008</year>
<holder>Thomas Gleixner</holder>
</copyright>
<legalnotice>
<para>
This documentation is free software; you can redistribute
it and/or modify it under the terms of the GNU General Public
License version 2 as published by the Free Software Foundation.
</para>
<para>
This program is distributed in the hope that it will be
useful, but WITHOUT ANY WARRANTY; without even the implied
warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
See the GNU General Public License for more details.
</para>
<para>
You should have received a copy of the GNU General Public
License along with this program; if not, write to the Free
Software Foundation, Inc., 59 Temple Place, Suite 330, Boston,
MA 02111-1307 USA
</para>
<para>
For more details see the file COPYING in the source
distribution of Linux.
</para>
</legalnotice>
</bookinfo>
<toc></toc>
<chapter id="intro">
<title>Introduction</title>
<para>
debugobjects is a generic infrastructure to track the life time
of kernel objects and validate the operations on those.
</para>
<para>
debugobjects is useful to check for the following error patterns:
<itemizedlist>
<listitem><para>Activation of uninitialized objects</para></listitem>
<listitem><para>Initialization of active objects</para></listitem>
<listitem><para>Usage of freed/destroyed objects</para></listitem>
</itemizedlist>
</para>
<para>
debugobjects is not changing the data structure of the real
object so it can be compiled in with a minimal runtime impact
and enabled on demand with a kernel command line option.
</para>
</chapter>
<chapter id="howto">
<title>Howto use debugobjects</title>
<para>
A kernel subsystem needs to provide a data structure which
describes the object type and add calls into the debug code at
appropriate places. The data structure to describe the object
type needs at minimum the name of the object type. Optional
functions can and should be provided to fixup detected problems
so the kernel can continue to work and the debug information can
be retrieved from a live system instead of hard core debugging
with serial consoles and stack trace transcripts from the
monitor.
</para>
<para>
The debug calls provided by debugobjects are:
<itemizedlist>
<listitem><para>debug_object_init</para></listitem>
<listitem><para>debug_object_init_on_stack</para></listitem>
<listitem><para>debug_object_activate</para></listitem>
<listitem><para>debug_object_deactivate</para></listitem>
<listitem><para>debug_object_destroy</para></listitem>
<listitem><para>debug_object_free</para></listitem>
<listitem><para>debug_object_assert_init</para></listitem>
</itemizedlist>
Each of these functions takes the address of the real object and
a pointer to the object type specific debug description
structure.
</para>
<para>
Each detected error is reported in the statistics and a limited
number of errors are printk'ed including a full stack trace.
</para>
<para>
The statistics are available via /sys/kernel/debug/debug_objects/stats.
They provide information about the number of warnings and the
number of successful fixups along with information about the
usage of the internal tracking objects and the state of the
internal tracking objects pool.
</para>
</chapter>
<chapter id="debugfunctions">
<title>Debug functions</title>
<sect1 id="prototypes">
<title>Debug object function reference</title>
!Elib/debugobjects.c
</sect1>
<sect1 id="debug_object_init">
<title>debug_object_init</title>
<para>
This function is called whenever the initialization function
of a real object is called.
</para>
<para>
When the real object is already tracked by debugobjects it is
checked, whether the object can be initialized. Initializing
is not allowed for active and destroyed objects. When
debugobjects detects an error, then it calls the fixup_init
function of the object type description structure if provided
by the caller. The fixup function can correct the problem
before the real initialization of the object happens. E.g. it
can deactivate an active object in order to prevent damage to
the subsystem.
</para>
<para>
When the real object is not yet tracked by debugobjects,
debugobjects allocates a tracker object for the real object
and sets the tracker object state to ODEBUG_STATE_INIT. It
verifies that the object is not on the callers stack. If it is
on the callers stack then a limited number of warnings
including a full stack trace is printk'ed. The calling code
must use debug_object_init_on_stack() and remove the object
before leaving the function which allocated it. See next
section.
</para>
</sect1>
<sect1 id="debug_object_init_on_stack">
<title>debug_object_init_on_stack</title>
<para>
This function is called whenever the initialization function
of a real object which resides on the stack is called.
</para>
<para>
When the real object is already tracked by debugobjects it is
checked, whether the object can be initialized. Initializing
is not allowed for active and destroyed objects. When
debugobjects detects an error, then it calls the fixup_init
function of the object type description structure if provided
by the caller. The fixup function can correct the problem
before the real initialization of the object happens. E.g. it
can deactivate an active object in order to prevent damage to
the subsystem.
</para>
<para>
When the real object is not yet tracked by debugobjects
debugobjects allocates a tracker object for the real object
and sets the tracker object state to ODEBUG_STATE_INIT. It
verifies that the object is on the callers stack.
</para>
<para>
An object which is on the stack must be removed from the
tracker by calling debug_object_free() before the function
which allocates the object returns. Otherwise we keep track of
stale objects.
</para>
</sect1>
<sect1 id="debug_object_activate">
<title>debug_object_activate</title>
<para>
This function is called whenever the activation function of a
real object is called.
</para>
<para>
When the real object is already tracked by debugobjects it is
checked, whether the object can be activated. Activating is
not allowed for active and destroyed objects. When
debugobjects detects an error, then it calls the
fixup_activate function of the object type description
structure if provided by the caller. The fixup function can
correct the problem before the real activation of the object
happens. E.g. it can deactivate an active object in order to
prevent damage to the subsystem.
</para>
<para>
When the real object is not yet tracked by debugobjects then
the fixup_activate function is called if available. This is
necessary to allow the legitimate activation of statically
allocated and initialized objects. The fixup function checks
whether the object is valid and calls the debug_objects_init()
function to initialize the tracking of this object.
</para>
<para>
When the activation is legitimate, then the state of the
associated tracker object is set to ODEBUG_STATE_ACTIVE.
</para>
</sect1>
<sect1 id="debug_object_deactivate">
<title>debug_object_deactivate</title>
<para>
This function is called whenever the deactivation function of
a real object is called.
</para>
<para>
When the real object is tracked by debugobjects it is checked,
whether the object can be deactivated. Deactivating is not
allowed for untracked or destroyed objects.
</para>
<para>
When the deactivation is legitimate, then the state of the
associated tracker object is set to ODEBUG_STATE_INACTIVE.
</para>
</sect1>
<sect1 id="debug_object_destroy">
<title>debug_object_destroy</title>
<para>
This function is called to mark an object destroyed. This is
useful to prevent the usage of invalid objects, which are
still available in memory: either statically allocated objects
or objects which are freed later.
</para>
<para>
When the real object is tracked by debugobjects it is checked,
whether the object can be destroyed. Destruction is not
allowed for active and destroyed objects. When debugobjects
detects an error, then it calls the fixup_destroy function of
the object type description structure if provided by the
caller. The fixup function can correct the problem before the
real destruction of the object happens. E.g. it can deactivate
an active object in order to prevent damage to the subsystem.
</para>
<para>
When the destruction is legitimate, then the state of the
associated tracker object is set to ODEBUG_STATE_DESTROYED.
</para>
</sect1>
<sect1 id="debug_object_free">
<title>debug_object_free</title>
<para>
This function is called before an object is freed.
</para>
<para>
When the real object is tracked by debugobjects it is checked,
whether the object can be freed. Free is not allowed for
active objects. When debugobjects detects an error, then it
calls the fixup_free function of the object type description
structure if provided by the caller. The fixup function can
correct the problem before the real free of the object
happens. E.g. it can deactivate an active object in order to
prevent damage to the subsystem.
</para>
<para>
Note that debug_object_free removes the object from the
tracker. Later usage of the object is detected by the other
debug checks.
</para>
</sect1>
<sect1 id="debug_object_assert_init">
<title>debug_object_assert_init</title>
<para>
This function is called to assert that an object has been
initialized.
</para>
<para>
When the real object is not tracked by debugobjects, it calls
fixup_assert_init of the object type description structure
provided by the caller, with the hardcoded object state
ODEBUG_NOT_AVAILABLE. The fixup function can correct the problem
by calling debug_object_init and other specific initializing
functions.
</para>
<para>
When the real object is already tracked by debugobjects it is
ignored.
</para>
</sect1>
</chapter>
<chapter id="fixupfunctions">
<title>Fixup functions</title>
<sect1 id="debug_obj_descr">
<title>Debug object type description structure</title>
!Iinclude/linux/debugobjects.h
</sect1>
<sect1 id="fixup_init">
<title>fixup_init</title>
<para>
This function is called from the debug code whenever a problem
in debug_object_init is detected. The function takes the
address of the object and the state which is currently
recorded in the tracker.
</para>
<para>
Called from debug_object_init when the object state is:
<itemizedlist>
<listitem><para>ODEBUG_STATE_ACTIVE</para></listitem>
</itemizedlist>
</para>
<para>
The function returns true when the fixup was successful,
otherwise false. The return value is used to update the
statistics.
</para>
<para>
Note, that the function needs to call the debug_object_init()
function again, after the damage has been repaired in order to
keep the state consistent.
</para>
</sect1>
<sect1 id="fixup_activate">
<title>fixup_activate</title>
<para>
This function is called from the debug code whenever a problem
in debug_object_activate is detected.
</para>
<para>
Called from debug_object_activate when the object state is:
<itemizedlist>
<listitem><para>ODEBUG_STATE_NOTAVAILABLE</para></listitem>
<listitem><para>ODEBUG_STATE_ACTIVE</para></listitem>
</itemizedlist>
</para>
<para>
The function returns true when the fixup was successful,
otherwise false. The return value is used to update the
statistics.
</para>
<para>
Note that the function needs to call the debug_object_activate()
function again after the damage has been repaired in order to
keep the state consistent.
</para>
<para>
The activation of statically initialized objects is a special
case. When debug_object_activate() has no tracked object for
this object address then fixup_activate() is called with
object state ODEBUG_STATE_NOTAVAILABLE. The fixup function
needs to check whether this is a legitimate case of a
statically initialized object or not. In case it is it calls
debug_object_init() and debug_object_activate() to make the
object known to the tracker and marked active. In this case
the function should return false because this is not a real
fixup.
</para>
</sect1>
<sect1 id="fixup_destroy">
<title>fixup_destroy</title>
<para>
This function is called from the debug code whenever a problem
in debug_object_destroy is detected.
</para>
<para>
Called from debug_object_destroy when the object state is:
<itemizedlist>
<listitem><para>ODEBUG_STATE_ACTIVE</para></listitem>
</itemizedlist>
</para>
<para>
The function returns true when the fixup was successful,
otherwise false. The return value is used to update the
statistics.
</para>
</sect1>
<sect1 id="fixup_free">
<title>fixup_free</title>
<para>
This function is called from the debug code whenever a problem
in debug_object_free is detected. Further it can be called
from the debug checks in kfree/vfree, when an active object is
detected from the debug_check_no_obj_freed() sanity checks.
</para>
<para>
Called from debug_object_free() or debug_check_no_obj_freed()
when the object state is:
<itemizedlist>
<listitem><para>ODEBUG_STATE_ACTIVE</para></listitem>
</itemizedlist>
</para>
<para>
The function returns true when the fixup was successful,
otherwise false. The return value is used to update the
statistics.
</para>
</sect1>
<sect1 id="fixup_assert_init">
<title>fixup_assert_init</title>
<para>
This function is called from the debug code whenever a problem
in debug_object_assert_init is detected.
</para>
<para>
Called from debug_object_assert_init() with a hardcoded state
ODEBUG_STATE_NOTAVAILABLE when the object is not found in the
debug bucket.
</para>
<para>
The function returns true when the fixup was successful,
otherwise false. The return value is used to update the
statistics.
</para>
<para>
Note, this function should make sure debug_object_init() is
called before returning.
</para>
<para>
The handling of statically initialized objects is a special
case. The fixup function should check if this is a legitimate
case of a statically initialized object or not. In this case only
debug_object_init() should be called to make the object known to
the tracker. Then the function should return false because this
is not
a real fixup.
</para>
</sect1>
</chapter>
<chapter id="bugs">
<title>Known Bugs And Assumptions</title>
<para>
None (knock on wood).
</para>
</chapter>
</book>
Documentation/DocBook/kernel-hacking.tmpl
浏览文件 @ dbbc21bb
......@@ -1208,8 +1208,8 @@ static struct block_device_operations opt_fops = {
<listitem>
<para>
Finally, don't forget to read <filename>Documentation/SubmittingPatches</filename>
and possibly <filename>Documentation/SubmittingDrivers</filename>.
Finally, don't forget to read <filename>Documentation/process/submitting-patches.rst</filename>
and possibly <filename>Documentation/process/submitting-drivers.rst</filename>.
</para>
</listitem>
</itemizedlist>
......
Documentation/DocBook/tracepoint.tmpl 已删除 100644 → 0
浏览文件 @ f6fa11a3
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN"
"http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd" []>
<book id="Tracepoints">
<bookinfo>
<title>The Linux Kernel Tracepoint API</title>
<authorgroup>
<author>
<firstname>Jason</firstname>
<surname>Baron</surname>
<affiliation>
<address>
<email>jbaron@redhat.com</email>
</address>
</affiliation>
</author>
<author>
<firstname>William</firstname>
<surname>Cohen</surname>
<affiliation>
<address>
<email>wcohen@redhat.com</email>
</address>
</affiliation>
</author>
</authorgroup>
<legalnotice>
<para>
This documentation is free software; you can redistribute
it and/or modify it under the terms of the GNU General Public
License as published by the Free Software Foundation; either
version 2 of the License, or (at your option) any later
version.
</para>
<para>
This program is distributed in the hope that it will be
useful, but WITHOUT ANY WARRANTY; without even the implied
warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
See the GNU General Public License for more details.
</para>
<para>
You should have received a copy of the GNU General Public
License along with this program; if not, write to the Free
Software Foundation, Inc., 59 Temple Place, Suite 330, Boston,
MA 02111-1307 USA
</para>
<para>
For more details see the file COPYING in the source
distribution of Linux.
</para>
</legalnotice>
</bookinfo>
<toc></toc>
<chapter id="intro">
<title>Introduction</title>
<para>
Tracepoints are static probe points that are located in strategic points
throughout the kernel. 'Probes' register/unregister with tracepoints
via a callback mechanism. The 'probes' are strictly typed functions that
are passed a unique set of parameters defined by each tracepoint.
</para>
<para>
From this simple callback mechanism, 'probes' can be used to profile, debug,
and understand kernel behavior. There are a number of tools that provide a
framework for using 'probes'. These tools include Systemtap, ftrace, and
LTTng.
</para>
<para>
Tracepoints are defined in a number of header files via various macros. Thus,
the purpose of this document is to provide a clear accounting of the available
tracepoints. The intention is to understand not only what tracepoints are
available but also to understand where future tracepoints might be added.
</para>
<para>
The API presented has functions of the form:
<function>trace_tracepointname(function parameters)</function>. These are the
tracepoints callbacks that are found throughout the code. Registering and
unregistering probes with these callback sites is covered in the
<filename>Documentation/trace/*</filename> directory.
</para>
</chapter>
<chapter id="irq">
<title>IRQ</title>
!Iinclude/trace/events/irq.h
</chapter>
<chapter id="signal">
<title>SIGNAL</title>
!Iinclude/trace/events/signal.h
</chapter>
<chapter id="block">
<title>Block IO</title>
!Iinclude/trace/events/block.h
</chapter>
<chapter id="workqueue">
<title>Workqueue</title>
!Iinclude/trace/events/workqueue.h
</chapter>
</book>
Documentation/DocBook/uio-howto.tmpl
浏览文件 @ dbbc21bb
......@@ -45,6 +45,13 @@ GPL version 2.
</abstract>
<revhistory>
<revision>
<revnumber>0.10</revnumber>
<date>2016-10-17</date>
<authorinitials>sch</authorinitials>
<revremark>Added generic hyperv driver
</revremark>
</revision>
<revision>
<revnumber>0.9</revnumber>
<date>2009-07-16</date>
......@@ -1033,6 +1040,61 @@ int main()
</chapter>
<chapter id="uio_hv_generic" xreflabel="Using Generic driver for Hyper-V VMBUS">
<?dbhtml filename="uio_hv_generic.html"?>
<title>Generic Hyper-V UIO driver</title>
<para>
The generic driver is a kernel module named uio_hv_generic.
It supports devices on the Hyper-V VMBus similar to uio_pci_generic
on PCI bus.
</para>
<sect1 id="uio_hv_generic_binding">
<title>Making the driver recognize the device</title>
<para>
Since the driver does not declare any device GUID's, it will not get loaded
automatically and will not automatically bind to any devices, you must load it
and allocate id to the driver yourself. For example, to use the network device
GUID:
<programlisting>
modprobe uio_hv_generic
echo &quot;f8615163-df3e-46c5-913f-f2d2f965ed0e&quot; &gt; /sys/bus/vmbus/drivers/uio_hv_generic/new_id
</programlisting>
</para>
<para>
If there already is a hardware specific kernel driver for the device, the
generic driver still won't bind to it, in this case if you want to use the
generic driver (why would you?) you'll have to manually unbind the hardware
specific driver and bind the generic driver, like this:
<programlisting>
echo -n vmbus-ed963694-e847-4b2a-85af-bc9cfc11d6f3 &gt; /sys/bus/vmbus/drivers/hv_netvsc/unbind
echo -n vmbus-ed963694-e847-4b2a-85af-bc9cfc11d6f3 &gt; /sys/bus/vmbus/drivers/uio_hv_generic/bind
</programlisting>
</para>
<para>
You can verify that the device has been bound to the driver
by looking for it in sysfs, for example like the following:
<programlisting>
ls -l /sys/bus/vmbus/devices/vmbus-ed963694-e847-4b2a-85af-bc9cfc11d6f3/driver
</programlisting>
Which if successful should print
<programlisting>
.../vmbus-ed963694-e847-4b2a-85af-bc9cfc11d6f3/driver -&gt; ../../../bus/vmbus/drivers/uio_hv_generic
</programlisting>
</para>
</sect1>
<sect1 id="uio_hv_generic_internals">
<title>Things to know about uio_hv_generic</title>
<para>
On each interrupt, uio_hv_generic sets the Interrupt Disable bit.
This prevents the device from generating further interrupts
until the bit is cleared. The userspace driver should clear this
bit before blocking and waiting for more interrupts.
</para>
</sect1>
</chapter>
<appendix id="app1">
<title>Further information</title>
<itemizedlist>
......
Documentation/DocBook/usb.tmpl 已删除 100644 → 0
浏览文件 @ f6fa11a3
此差异已折叠。
Documentation/HOWTO 已删除 100644 → 0
浏览文件 @ f6fa11a3
此差异已折叠。
Documentation/IPMI.txt
浏览文件 @ dbbc21bb
......@@ -111,6 +111,8 @@ ipmi_ssif - A driver for accessing BMCs on the SMBus. It uses the
I2C kernel driver's SMBus interfaces to send and receive IPMI messages
over the SMBus.
ipmi_powernv - A driver for access BMCs on POWERNV systems.
ipmi_watchdog - IPMI requires systems to have a very capable watchdog
timer. This driver implements the standard Linux watchdog timer
interface on top of the IPMI message handler.
......@@ -118,17 +120,15 @@ interface on top of the IPMI message handler.
ipmi_poweroff - Some systems support the ability to be turned off via
IPMI commands.
These are all individually selectable via configuration options.
bt-bmc - This is not part of the main driver, but instead a driver for
accessing a BMC-side interface of a BT interface. It is used on BMCs
running Linux to provide an interface to the host.
Note that the KCS-only interface has been removed. The af_ipmi driver
is no longer supported and has been removed because it was impossible
to do 32 bit emulation on 64-bit kernels with it.
These are all individually selectable via configuration options.
Much documentation for the interface is in the include files. The
IPMI include files are:
net/af_ipmi.h - Contains the socket interface.
linux/ipmi.h - Contains the user interface and IOCTL interface for IPMI.
linux/ipmi_smi.h - Contains the interface for system management interfaces
......@@ -245,6 +245,16 @@ addressed (because some boards actually have multiple BMCs on them)
and the user should not have to care what type of SMI is below them.
Watching For Interfaces
When your code comes up, the IPMI driver may or may not have detected
if IPMI devices exist. So you might have to defer your setup until
the device is detected, or you might be able to do it immediately.
To handle this, and to allow for discovery, you register an SMI
watcher with ipmi_smi_watcher_register() to iterate over interfaces
and tell you when they come and go.
Creating the User
To user the message handler, you must first create a user using
......@@ -263,7 +273,7 @@ closing the device automatically destroys the user.
Messaging
To send a message from kernel-land, the ipmi_request() call does
To send a message from kernel-land, the ipmi_request_settime() call does
pretty much all message handling. Most of the parameter are
self-explanatory. However, it takes a "msgid" parameter. This is NOT
the sequence number of messages. It is simply a long value that is
......@@ -352,11 +362,12 @@ that for more details.
The SI Driver
-------------
The SI driver allows up to 4 KCS or SMIC interfaces to be configured
in the system. By default, scan the ACPI tables for interfaces, and
if it doesn't find any the driver will attempt to register one KCS
interface at the spec-specified I/O port 0xca2 without interrupts.
You can change this at module load time (for a module) with:
The SI driver allows KCS, BT, and SMIC interfaces to be configured
in the system. It discovers interfaces through a host of different
methods, depending on the system.
You can specify up to four interfaces on the module load line and
control some module parameters:
modprobe ipmi_si.o type=<type1>,<type2>....
ports=<port1>,<port2>... addrs=<addr1>,<addr2>...
......@@ -367,7 +378,7 @@ You can change this at module load time (for a module) with:
force_kipmid=<enable1>,<enable2>,...
kipmid_max_busy_us=<ustime1>,<ustime2>,...
unload_when_empty=[0|1]
trydefaults=[0|1] trydmi=[0|1] tryacpi=[0|1]
trydmi=[0|1] tryacpi=[0|1]
tryplatform=[0|1] trypci=[0|1]
Each of these except try... items is a list, the first item for the
......@@ -386,10 +397,6 @@ use the I/O port given as the device address.
If you specify irqs as non-zero for an interface, the driver will
attempt to use the given interrupt for the device.
trydefaults sets whether the standard IPMI interface at 0xca2 and
any interfaces specified by ACPE are tried. By default, the driver
tries it, set this value to zero to turn this off.
The other try... items disable discovery by their corresponding
names. These are all enabled by default, set them to zero to disable
them. The tryplatform disables openfirmware.
......@@ -434,7 +441,7 @@ kernel command line as:
ipmi_si.type=<type1>,<type2>...
ipmi_si.ports=<port1>,<port2>... ipmi_si.addrs=<addr1>,<addr2>...
ipmi_si.irqs=<irq1>,<irq2>... ipmi_si.trydefaults=[0|1]
ipmi_si.irqs=<irq1>,<irq2>...
ipmi_si.regspacings=<sp1>,<sp2>,...
ipmi_si.regsizes=<size1>,<size2>,...
ipmi_si.regshifts=<shift1>,<shift2>,...
......@@ -444,11 +451,6 @@ kernel command line as:
It works the same as the module parameters of the same names.
By default, the driver will attempt to detect any device specified by
ACPI, and if none of those then a KCS device at the spec-specified
0xca2. If you want to turn this off, set the "trydefaults" option to
false.
If your IPMI interface does not support interrupts and is a KCS or
SMIC interface, the IPMI driver will start a kernel thread for the
interface to help speed things up. This is a low-priority kernel
......@@ -500,7 +502,8 @@ at module load time (for a module) with:
addr=<i2caddr1>[,<i2caddr2>[,...]]
adapter=<adapter1>[,<adapter2>[...]]
dbg=<flags1>,<flags2>...
slave_addrs=<addr1>,<addr2>,...
slave_addrs=<addr1>,<addr2>,...
tryacpi=[0|1] trydmi=[0|1]
[dbg_probe=1]
The addresses are normal I2C addresses. The adapter is the string
......@@ -513,6 +516,9 @@ spaces in kernel parameters.
The debug flags are bit flags for each BMC found, they are:
IPMI messages: 1, driver state: 2, timing: 4, I2C probe: 8
The tryxxx parameters can be used to disable detecting interfaces
from various sources.
Setting dbg_probe to 1 will enable debugging of the probing and
detection process for BMCs on the SMBusses.
......@@ -535,7 +541,8 @@ kernel command line as:
ipmi_ssif.adapter=<adapter1>[,<adapter2>[...]]
ipmi_ssif.dbg=<flags1>[,<flags2>[...]]
ipmi_ssif.dbg_probe=1
ipmi_ssif.slave_addrs=<addr1>[,<addr2>[...]]
ipmi_ssif.slave_addrs=<addr1>[,<addr2>[...]]
ipmi_ssif.tryacpi=[0|1] ipmi_ssif.trydmi=[0|1]
These are the same options as on the module command line.
......
Documentation/Makefile.sphinx
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/ManagementStyle 已删除 100644 → 0
浏览文件 @ f6fa11a3
此差异已折叠。
Documentation/RCU/Design/Requirements/Requirements.html
浏览文件 @ dbbc21bb
......@@ -547,7 +547,7 @@ The <tt>rcu_access_pointer()</tt> on line&nbsp;6 is similar to
It could reuse a value formerly fetched from this same pointer.
It could also fetch the pointer from <tt>gp</tt> in a byte-at-a-time
manner, resulting in <i>load tearing</i>, in turn resulting a bytewise
mash-up of two distince pointer values.
mash-up of two distinct pointer values.
It might even use value-speculation optimizations, where it makes
a wrong guess, but by the time it gets around to checking the
value, an update has changed the pointer to match the wrong guess.
......@@ -659,6 +659,29 @@ systems with more than one CPU:
In other words, a given instance of <tt>synchronize_rcu()</tt>
can avoid waiting on a given RCU read-side critical section only
if it can prove that <tt>synchronize_rcu()</tt> started first.
<p>
A related question is &ldquo;When <tt>rcu_read_lock()</tt>
doesn't generate any code, why does it matter how it relates
to a grace period?&rdquo;
The answer is that it is not the relationship of
<tt>rcu_read_lock()</tt> itself that is important, but rather
the relationship of the code within the enclosed RCU read-side
critical section to the code preceding and following the
grace period.
If we take this viewpoint, then a given RCU read-side critical
section begins before a given grace period when some access
preceding the grace period observes the effect of some access
within the critical section, in which case none of the accesses
within the critical section may observe the effects of any
access following the grace period.
<p>
As of late 2016, mathematical models of RCU take this
viewpoint, for example, see slides&nbsp;62 and&nbsp;63
of the
<a href="http://www2.rdrop.com/users/paulmck/scalability/paper/LinuxMM.2016.10.04c.LCE.pdf">2016 LinuxCon EU</a>
presentation.
</font></td></tr>
<tr><td>&nbsp;</td></tr>
</table>
......
Documentation/RCU/whatisRCU.txt
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/SecurityBugs 已删除 100644 → 0
浏览文件 @ f6fa11a3
此差异已折叠。
Documentation/SubmitChecklist 已删除 100644 → 0
浏览文件 @ f6fa11a3
此差异已折叠。
Documentation/SubmittingDrivers 已删除 100644 → 0
浏览文件 @ f6fa11a3
此差异已折叠。
Documentation/SubmittingPatches
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/VGA-softcursor.txt 已删除 100644 → 0
浏览文件 @ f6fa11a3
此差异已折叠。
Documentation/acpi/DSD-properties-rules.txt 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/acpi/enumeration.txt
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/acpi/osi.txt 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/adding-syscalls.txt 已删除 100644 → 0
浏览文件 @ f6fa11a3
此差异已折叠。
Documentation/admin-guide/README.rst 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/admin-guide/binfmt-misc.rst 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/admin-guide/braille-console.rst 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/admin-guide/bug-bisect.rst 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/admin-guide/bug-hunting.rst 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/admin-guide/conf.py 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/admin-guide/devices.rst 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/admin-guide/devices.txt 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/admin-guide/dynamic-debug-howto.rst 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/admin-guide/index.rst 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/admin-guide/init.rst 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/admin-guide/initrd.rst 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/admin-guide/java.rst 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/admin-guide/kernel-parameters.rst 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/admin-guide/kernel-parameters.txt 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/admin-guide/md.rst 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/admin-guide/module-signing.rst 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/admin-guide/mono.rst 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/admin-guide/parport.rst 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/admin-guide/ramoops.rst 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/admin-guide/ras.rst 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/admin-guide/reporting-bugs.rst 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/admin-guide/security-bugs.rst 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/admin-guide/serial-console.rst 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/admin-guide/sysfs-rules.rst 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/admin-guide/sysrq.rst 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/admin-guide/tainted-kernels.rst 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/admin-guide/unicode.rst 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/admin-guide/vga-softcursor.rst 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/applying-patches.txt 已删除 100644 → 0
浏览文件 @ f6fa11a3
此差异已折叠。
Documentation/arm/Booting
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/arm/stm32/stm32f746-overview.txt 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/assoc_array.txt 已删除 100644 → 0
浏览文件 @ f6fa11a3
此差异已折叠。
Documentation/atomic_ops.txt 已删除 100644 → 0
浏览文件 @ f6fa11a3
此差异已折叠。
Documentation/bad_memory.txt 已删除 100644 → 0
浏览文件 @ f6fa11a3
此差异已折叠。
Documentation/basic_profiling.txt 已删除 100644 → 0
浏览文件 @ f6fa11a3
此差异已折叠。
Documentation/binfmt_misc.txt 已删除 100644 → 0
浏览文件 @ f6fa11a3
此差异已折叠。
Documentation/block/biodoc.txt
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/block/cfq-iosched.txt
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/block/null_blk.txt
浏览文件 @ dbbc21bb
......@@ -72,4 +72,4 @@ use_per_node_hctx=[0/1]: Default: 0
queue for each CPU node in the system.
use_lightnvm=[0/1]: Default: 0
Register device with LightNVM. Requires blk-mq to be used.
Register device with LightNVM. Requires blk-mq and CONFIG_NVM to be enabled.
Documentation/block/queue-sysfs.txt
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/blockdev/cciss.txt
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/blockdev/ramdisk.txt
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/braille-console.txt 已删除 100644 → 0
浏览文件 @ f6fa11a3
此差异已折叠。
Documentation/cgroup-v1/00-INDEX
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/circular-buffers.txt
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/conf.py
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/core-api/assoc_array.rst 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/core-api/atomic_ops.rst 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/core-api/conf.py 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/core-api/debug-objects.rst 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/core-api/index.rst 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/core-api/local_ops.rst 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/core-api/tracepoint.rst 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/core-api/workqueue.rst 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/cpu-hotplug.txt
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/crypto/api-aead.rst 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/crypto/api-akcipher.rst 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/crypto/api-digest.rst 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/crypto/api-intro.txt
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/crypto/api-kpp.rst 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/crypto/api-rng.rst 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/crypto/api-samples.rst 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/crypto/api-skcipher.rst 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/crypto/api.rst 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/crypto/architecture.rst 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/crypto/devel-algos.rst 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/crypto/index.rst 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/crypto/intro.rst 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/crypto/userspace-if.rst 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/dev-tools/conf.py 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/dev-tools/gcov.rst
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/dev-tools/index.rst 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/dev-tools/kcov.rst
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/dev-tools/sparse.rst
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/dev-tools/tools.rst 已删除 100644 → 0
浏览文件 @ f6fa11a3
此差异已折叠。
Documentation/development-process/1.Intro.rst 已删除 100644 → 0
浏览文件 @ f6fa11a3
此差异已折叠。
Documentation/development-process/conf.py 已删除 100644 → 0
浏览文件 @ f6fa11a3
此差异已折叠。
Documentation/development-process/index.rst 已删除 100644 → 0
浏览文件 @ f6fa11a3
此差异已折叠。
Documentation/devices.txt 已删除 100644 → 0
浏览文件 @ f6fa11a3
此差异已折叠。
Documentation/devicetree/bindings/arm/amlogic,scpi.txt 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/devicetree/bindings/arm/cpu-capacity.txt 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/devicetree/bindings/arm/juno,scpi.txt 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/devicetree/bindings/arm/swir.txt 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/devicetree/bindings/clock/hisi-crg.txt 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/devicetree/bindings/clock/qcom,rpmcc.txt 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/devicetree/bindings/display/ht16k33.txt 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/devicetree/bindings/display/zte,vou.txt 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/devicetree/bindings/dma/st_fdma.txt 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/devicetree/bindings/fpga/fpga-region.txt 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/devicetree/bindings/hwmon/mcp3021.txt 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/devicetree/bindings/hwmon/tmp108.txt 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/devicetree/bindings/i2c/i2c-imx-lpi2c.txt 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/devicetree/bindings/iio/dac/dpot-dac.txt 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/devicetree/bindings/iio/dac/mcp4725.txt 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/devicetree/bindings/iio/light/tsl2583.txt 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/devicetree/bindings/mfd/altera-a10sr.txt 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/devicetree/bindings/mmc/sdhci-cadence.txt 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/devicetree/bindings/mmc/sdhci.txt 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/devicetree/bindings/mtd/oxnas-nand.txt 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/devicetree/bindings/mtd/tango-nand.txt 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/devicetree/bindings/net/oxnas-dwmac.txt 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/devicetree/bindings/nvmem/brcm,ocotp.txt 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/devicetree/bindings/nvmem/lpc1850-otp.txt 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/devicetree/bindings/pwm/pwm-hibvt.txt 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/devicetree/bindings/reset/renesas,rst.txt 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/devicetree/bindings/rtc/epson,rtc7301.txt 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/devicetree/bindings/soc/fsl/guts.txt 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/devicetree/bindings/spi/spi-fsl-lpspi.txt 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/devicetree/bindings/usb/da8xx-usb.txt 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/devicetree/bindings/usb/mt8173-mtu3.txt 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/devicetree/bindings/usb/ohci-da8xx.txt 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/devicetree/bindings/usb/s3c2410-usb.txt 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/dmaengine/client.txt
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/dmaengine/dmatest.txt
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/dmaengine/pxa_dma.txt
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/doc-guide/conf.py 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/doc-guide/docbook.rst 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/doc-guide/index.rst 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/doc-guide/kernel-doc.rst 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/doc-guide/parse-headers.rst 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/doc-guide/sphinx.rst 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/dontdiff
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/driver-api/80211/conf.py 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/driver-api/80211/index.rst 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/driver-api/conf.py 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/driver-api/device_link.rst 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/driver-api/dma-buf.rst 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/driver-api/edac.rst 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/driver-api/index.rst
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/driver-api/usb.rst 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/driver-api/vme.rst 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/dynamic-debug-howto.txt 已删除 100644 → 0
浏览文件 @ f6fa11a3
此差异已折叠。
Documentation/edac.txt 已删除 100644 → 0
浏览文件 @ f6fa11a3
此差异已折叠。
Documentation/filesystems/00-INDEX
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/filesystems/Locking
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/filesystems/dax.txt
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/filesystems/ext4.txt
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/filesystems/locks.txt
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/filesystems/logfs.txt 已删除 100644 → 0
浏览文件 @ f6fa11a3
此差异已折叠。
Documentation/filesystems/porting
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/filesystems/proc.txt
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/filesystems/vfs.txt
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/filesystems/xfs.txt
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/fpga/fpga-mgr.txt
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/frv/booting.txt
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/gpio/driver.txt
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/gpu/conf.py
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/gpu/drm-internals.rst
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/gpu/drm-kms.rst
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/gpu/drm-mm.rst
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/gpu/drm-uapi.rst
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/gpu/i915.rst
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/gpu/index.rst
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/hwmon/tc654 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/hwmon/tmp108 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/i2c/busses/i2c-mlxcpld 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/i2c/smbus-protocol
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/index.rst
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/init.txt 已删除 100644 → 0
浏览文件 @ f6fa11a3
此差异已折叠。
Documentation/initrd.txt 已删除 100644 → 0
浏览文件 @ f6fa11a3
此差异已折叠。
Documentation/isdn/README
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/ja_JP/HOWTO 已删除 100644 → 0
浏览文件 @ f6fa11a3
此差异已折叠。
Documentation/ja_JP/SubmitChecklist 已删除 100644 → 0
浏览文件 @ f6fa11a3
此差异已折叠。
Documentation/ja_JP/SubmittingPatches 已删除 100644 → 0
浏览文件 @ f6fa11a3
此差异已折叠。
Documentation/ja_JP/stable_api_nonsense.txt 已删除 100644 → 0
浏览文件 @ f6fa11a3
此差异已折叠。
Documentation/ja_JP/stable_kernel_rules.txt 已删除 100644 → 0
浏览文件 @ f6fa11a3
此差异已折叠。
Documentation/java.txt 已删除 100644 → 0
浏览文件 @ f6fa11a3
此差异已折叠。
Documentation/kernel-documentation.rst 已删除 100644 → 0
浏览文件 @ f6fa11a3
此差异已折叠。
Documentation/kernel-parameters.txt 已删除 100644 → 0
浏览文件 @ f6fa11a3
此差异已折叠。
Documentation/ko_KR/HOWTO 已删除 100644 → 0
浏览文件 @ f6fa11a3
此差异已折叠。
Documentation/ko_KR/memory-barriers.txt 已删除 100644 → 0
浏览文件 @ f6fa11a3
此差异已折叠。
Documentation/ko_KR/stable_api_nonsense.txt 已删除 100644 → 0
浏览文件 @ f6fa11a3
此差异已折叠。
Documentation/kselftest.txt
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/leds/leds-lp5523.txt
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/leds/uleds.txt 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/local_ops.txt 已删除 100644 → 0
浏览文件 @ f6fa11a3
此差异已折叠。
Documentation/lockup-watchdogs.txt
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/magic-number.txt 已删除 100644 → 0
浏览文件 @ f6fa11a3
此差异已折叠。
Documentation/md.txt 已删除 100644 → 0
浏览文件 @ f6fa11a3
此差异已折叠。
Documentation/media/.gitignore 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/media/Makefile
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/media/index.rst
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/media/intro.rst
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/media/kapi/csi2.rst 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/media/media_kapi.rst
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/media/typical_media_device.svg 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/media/uapi/dvb/dvbstb.svg 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/media/uapi/v4l/bayer.svg 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/media/uapi/v4l/constraints.svg 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/media/uapi/v4l/crop.svg 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/media/uapi/v4l/fieldseq_bt.svg 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/media/uapi/v4l/fieldseq_tb.svg 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/media/uapi/v4l/hsv-formats.rst 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/media/uapi/v4l/nv12mt.svg 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/media/uapi/v4l/nv12mt_example.svg 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/media/uapi/v4l/pipeline.dot 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/media/uapi/v4l/pixfmt-packed-hsv.rst 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/media/uapi/v4l/pixfmt-srggb16.rst 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/media/uapi/v4l/selection.svg 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/media/uapi/v4l/vbi_525.svg 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/media/uapi/v4l/vbi_625.svg 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/media/uapi/v4l/vbi_hsync.svg 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/media/v4l-drivers/rcar-fdp1.rst 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/memory-hotplug.txt
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/module-signing.txt 已删除 100644 → 0
浏览文件 @ f6fa11a3
此差异已折叠。
Documentation/mono.txt 已删除 100644 → 0
浏览文件 @ f6fa11a3
此差异已折叠。
Documentation/networking/l2tp.txt
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/networking/phy.txt
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/networking/seg6-sysctl.txt 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/networking/stmmac.txt
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/networking/vortex.txt
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/oops-tracing.txt 已删除 100644 → 0
浏览文件 @ f6fa11a3
此差异已折叠。
Documentation/parport.txt 已删除 100644 → 0
浏览文件 @ f6fa11a3
此差异已折叠。
Documentation/power/00-INDEX
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/power/devices.txt
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/power/pci.txt
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/power/runtime_pm.txt
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/power/states.txt
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/process/1.Intro.rst 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/process/4.Coding.rst 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/process/5.Posting.rst 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/process/7.AdvancedTopics.rst 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/process/8.Conclusion.rst 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/process/adding-syscalls.rst 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/process/applying-patches.rst 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/process/changes.rst 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/process/code-of-conflict.rst 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/process/coding-style.rst 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/process/conf.py 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/process/development-process.rst 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/process/howto.rst 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/process/index.rst 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/process/magic-number.rst 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/process/management-style.rst 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/process/stable-kernel-rules.rst 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/process/submit-checklist.rst 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/process/submitting-drivers.rst 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/process/submitting-patches.rst 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/process/volatile-considered-harmful.rst 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/ramoops.txt 已删除 100644 → 0
浏览文件 @ f6fa11a3
此差异已折叠。
Documentation/rfkill.txt
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/scsi/g_NCR5380.txt
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/scsi/sym53c8xx_2.txt
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/security/conf.py 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/security/index.rst 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/security/tpm/index.rst 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/security/tpm/tpm_vtpm_proxy.rst 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/serial-console.txt 已删除 100644 → 0
浏览文件 @ f6fa11a3
此差异已折叠。
Documentation/sound/alsa-configuration.rst 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/sound/alsa/Audigy-mixer.txt 已删除 100644 → 0
浏览文件 @ f6fa11a3
此差异已折叠。
Documentation/sound/alsa/Audiophile-Usb.txt 已删除 100644 → 0
浏览文件 @ f6fa11a3
此差异已折叠。
Documentation/sound/alsa/Bt87x.txt 已删除 100644 → 0
浏览文件 @ f6fa11a3
此差异已折叠。
Documentation/sound/alsa/CMIPCI.txt 已删除 100644 → 0
浏览文件 @ f6fa11a3
此差异已折叠。
Documentation/sound/alsa/ControlNames.txt 已删除 100644 → 0
浏览文件 @ f6fa11a3
此差异已折叠。
Documentation/sound/alsa/HD-Audio-Models.txt 已删除 100644 → 0
浏览文件 @ f6fa11a3
此差异已折叠。
Documentation/sound/alsa/HD-Audio.txt 已删除 100644 → 0
浏览文件 @ f6fa11a3
此差异已折叠。
Documentation/sound/alsa/Jack-Controls.txt 已删除 100644 → 0
浏览文件 @ f6fa11a3
此差异已折叠。
Documentation/sound/alsa/Joystick.txt 已删除 100644 → 0
浏览文件 @ f6fa11a3
此差异已折叠。
Documentation/sound/alsa/MIXART.txt 已删除 100644 → 0
浏览文件 @ f6fa11a3
此差异已折叠。
Documentation/sound/alsa/OSS-Emulation.txt 已删除 100644 → 0
浏览文件 @ f6fa11a3
此差异已折叠。
Documentation/sound/alsa/Procfile.txt 已删除 100644 → 0
浏览文件 @ f6fa11a3
此差异已折叠。
Documentation/sound/alsa/README.maya44 已删除 100644 → 0
浏览文件 @ f6fa11a3
此差异已折叠。
Documentation/sound/alsa/SB-Live-mixer.txt 已删除 100644 → 0
浏览文件 @ f6fa11a3
此差异已折叠。
Documentation/sound/alsa/VIA82xx-mixer.txt 已删除 100644 → 0
浏览文件 @ f6fa11a3
此差异已折叠。
Documentation/sound/alsa/alsa-parameters.txt 已删除 100644 → 0
浏览文件 @ f6fa11a3
此差异已折叠。
Documentation/sound/alsa/compress_offload.txt 已删除 100644 → 0
浏览文件 @ f6fa11a3
此差异已折叠。
Documentation/sound/alsa/emu10k1-jack.txt 已删除 100644 → 0
浏览文件 @ f6fa11a3
此差异已折叠。
Documentation/sound/alsa/hdspm.txt 已删除 100644 → 0
浏览文件 @ f6fa11a3
此差异已折叠。
Documentation/sound/alsa/img,spdif-in.txt 已删除 100644 → 0
浏览文件 @ f6fa11a3
此差异已折叠。
Documentation/sound/alsa/powersave.txt 已删除 100644 → 0
浏览文件 @ f6fa11a3
此差异已折叠。
Documentation/sound/alsa/seq_oss.html 已删除 100644 → 0
浏览文件 @ f6fa11a3
此差异已折叠。
Documentation/sound/alsa/serial-u16550.txt 已删除 100644 → 0
浏览文件 @ f6fa11a3
此差异已折叠。
Documentation/sound/alsa/soc/DAI.txt 已删除 100644 → 0
浏览文件 @ f6fa11a3
此差异已折叠。
Documentation/sound/alsa/soc/DPCM.txt 已删除 100644 → 0
浏览文件 @ f6fa11a3
此差异已折叠。
Documentation/sound/alsa/soc/clocking.txt 已删除 100644 → 0
浏览文件 @ f6fa11a3
此差异已折叠。
Documentation/sound/alsa/soc/codec.txt 已删除 100644 → 0
浏览文件 @ f6fa11a3
此差异已折叠。
Documentation/sound/alsa/soc/dapm.txt 已删除 100644 → 0
浏览文件 @ f6fa11a3
此差异已折叠。
Documentation/sound/alsa/soc/jack.txt 已删除 100644 → 0
浏览文件 @ f6fa11a3
此差异已折叠。
Documentation/sound/alsa/soc/machine.txt 已删除 100644 → 0
浏览文件 @ f6fa11a3
此差异已折叠。
Documentation/sound/alsa/soc/overview.txt 已删除 100644 → 0
浏览文件 @ f6fa11a3
此差异已折叠。
Documentation/sound/alsa/soc/platform.txt 已删除 100644 → 0
浏览文件 @ f6fa11a3
此差异已折叠。
Documentation/sound/alsa/soc/pops_clicks.txt 已删除 100644 → 0
浏览文件 @ f6fa11a3
此差异已折叠。
Documentation/sound/alsa/timestamping.txt 已删除 100644 → 0
浏览文件 @ f6fa11a3
此差异已折叠。
Documentation/sound/cards/audigy-mixer.rst 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/sound/cards/audiophile-usb.rst 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/sound/cards/bt87x.rst 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/sound/cards/cmipci.rst 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/sound/cards/emu10k1-jack.rst 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/sound/cards/hdspm.rst 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/sound/cards/img-spdif-in.rst 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/sound/cards/index.rst 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/sound/cards/joystick.rst 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/sound/cards/maya44.rst 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/sound/cards/mixart.rst 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/sound/cards/sb-live-mixer.rst 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/sound/cards/serial-u16550.rst 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/sound/cards/via82xx-mixer.rst 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/sound/designs/channel-mapping-api.rst 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/sound/designs/compress-offload.rst 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/sound/designs/control-names.rst 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/sound/designs/index.rst 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/sound/designs/jack-controls.rst 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/sound/designs/oss-emulation.rst 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/sound/designs/powersave.rst 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/sound/designs/procfile.rst 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/sound/designs/seq-oss.rst 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/sound/designs/timestamping.rst 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/sound/hd-audio/controls.rst 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/sound/hd-audio/dp-mst.rst 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/sound/hd-audio/index.rst 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/sound/hd-audio/models.rst 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/sound/hd-audio/notes.rst 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/sound/index.rst 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/sound/kernel-api/alsa-driver-api.rst 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/sound/kernel-api/index.rst 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/sound/soc/clocking.rst 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/sound/soc/codec-to-codec.rst 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/sound/soc/codec.rst 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/sound/soc/dai.rst 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/sound/soc/dapm.rst 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/sound/soc/dpcm.rst 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/sound/soc/index.rst 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/sound/soc/jack.rst 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/sound/soc/machine.rst 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/sound/soc/overview.rst 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/sound/soc/platform.rst 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/sound/soc/pops-clicks.rst 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/stable_kernel_rules.txt 已删除 100644 → 0
浏览文件 @ f6fa11a3
此差异已折叠。
Documentation/sync_file.txt
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/sysctl/kernel.txt
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/sysfs-rules.txt 已删除 100644 → 0
浏览文件 @ f6fa11a3
此差异已折叠。
Documentation/sysrq.txt 已删除 100644 → 0
浏览文件 @ f6fa11a3
此差异已折叠。
Documentation/tpm/tpm_vtpm_proxy.txt 已删除 100644 → 0
浏览文件 @ f6fa11a3
此差异已折叠。
Documentation/trace/events.txt
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/trace/ftrace.txt
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/trace/intel_th.txt
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/trace/stm.txt
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/translations/ja_JP/HOWTO 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/translations/ja_JP/SubmitChecklist 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/translations/ja_JP/SubmittingPatches 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/translations/ko_KR/howto.rst 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/translations/ko_KR/index.rst 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/translations/ko_KR/memory-barriers.txt 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/translations/zh_CN/CodingStyle 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/translations/zh_CN/HOWTO 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/translations/zh_CN/SecurityBugs 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/translations/zh_CN/SubmittingDrivers 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/translations/zh_CN/SubmittingPatches 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/translations/zh_CN/arm/Booting 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/translations/zh_CN/email-clients.txt 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/translations/zh_CN/oops-tracing.txt 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/translations/zh_CN/sparse.txt 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/unicode.txt 已删除 100644 → 0
浏览文件 @ f6fa11a3
此差异已折叠。
Documentation/vfio-mediated-device.txt 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/virtual/kvm/00-INDEX
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/virtual/kvm/api.txt
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/virtual/kvm/halt-polling.txt 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/virtual/kvm/msr.txt
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/vm/numa
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/vm/transhuge.txt
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/vme_api.txt 已删除 100644 → 0
浏览文件 @ f6fa11a3
此差异已折叠。
Documentation/volatile-considered-harmful.txt 已删除 100644 → 0
浏览文件 @ f6fa11a3
此差异已折叠。
Documentation/workqueue.txt 已删除 100644 → 0
浏览文件 @ f6fa11a3
此差异已折叠。
Documentation/x86/boot.txt
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/x86/intel_rdt_ui.txt 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/x86/topology.txt
浏览文件 @ dbbc21bb
此差异已折叠。
Documentation/zh_CN/CodingStyle 已删除 100644 → 0
浏览文件 @ f6fa11a3
此差异已折叠。
Documentation/zh_CN/HOWTO 已删除 100644 → 0
浏览文件 @ f6fa11a3
此差异已折叠。
Documentation/zh_CN/SecurityBugs 已删除 100644 → 0
浏览文件 @ f6fa11a3
此差异已折叠。
Documentation/zh_CN/SubmittingDrivers 已删除 100644 → 0
浏览文件 @ f6fa11a3
此差异已折叠。
Documentation/zh_CN/SubmittingPatches 已删除 100644 → 0
浏览文件 @ f6fa11a3
此差异已折叠。
Documentation/zh_CN/arm/Booting 已删除 100644 → 0
浏览文件 @ f6fa11a3
此差异已折叠。
Documentation/zh_CN/email-clients.txt 已删除 100644 → 0
浏览文件 @ f6fa11a3
此差异已折叠。
Documentation/zh_CN/oops-tracing.txt 已删除 100644 → 0
浏览文件 @ f6fa11a3
此差异已折叠。
Documentation/zh_CN/sparse.txt 已删除 100644 → 0
浏览文件 @ f6fa11a3
此差异已折叠。
Documentation/zh_CN/stable_api_nonsense.txt 已删除 100644 → 0
浏览文件 @ f6fa11a3
此差异已折叠。
Documentation/zh_CN/stable_kernel_rules.txt 已删除 100644 → 0
浏览文件 @ f6fa11a3
此差异已折叠。
MAINTAINERS
浏览文件 @ dbbc21bb
此差异已折叠。
Makefile
浏览文件 @ dbbc21bb
此差异已折叠。
README
浏览文件 @ dbbc21bb
此差异已折叠。
REPORTING-BUGS 已删除 100644 → 0
浏览文件 @ f6fa11a3
此差异已折叠。
arch/Kconfig
浏览文件 @ dbbc21bb
此差异已折叠。
arch/alpha/boot/misc.c
浏览文件 @ dbbc21bb
此差异已折叠。
arch/alpha/include/asm/mutex.h 已删除 100644 → 0
浏览文件 @ f6fa11a3
此差异已折叠。
arch/alpha/include/asm/processor.h
浏览文件 @ dbbc21bb
此差异已折叠。
arch/alpha/kernel/irq.c
浏览文件 @ dbbc21bb
此差异已折叠。
arch/alpha/kernel/osf_sys.c
浏览文件 @ dbbc21bb
此差异已折叠。
arch/alpha/kernel/process.c
浏览文件 @ dbbc21bb
此差异已折叠。
arch/alpha/kernel/ptrace.c
浏览文件 @ dbbc21bb
此差异已折叠。
arch/alpha/kernel/setup.c
浏览文件 @ dbbc21bb
此差异已折叠。
arch/alpha/kernel/signal.c
浏览文件 @ dbbc21bb
此差异已折叠。
arch/alpha/kernel/srm_env.c
浏览文件 @ dbbc21bb
此差异已折叠。
arch/alpha/kernel/srmcons.c
浏览文件 @ dbbc21bb
此差异已折叠。
arch/alpha/kernel/time.c
浏览文件 @ dbbc21bb
此差异已折叠。
arch/alpha/kernel/traps.c
浏览文件 @ dbbc21bb
此差异已折叠。
arch/alpha/lib/csum_partial_copy.c
浏览文件 @ dbbc21bb
此差异已折叠。
arch/alpha/math-emu/math.c
浏览文件 @ dbbc21bb
此差异已折叠。
arch/alpha/mm/init.c
浏览文件 @ dbbc21bb
此差异已折叠。
arch/arc/Kconfig
浏览文件 @ dbbc21bb
此差异已折叠。
arch/arc/boot/dts/abilis_tb10x.dtsi
浏览文件 @ dbbc21bb
此差异已折叠。
arch/arc/boot/dts/axs101.dts
浏览文件 @ dbbc21bb
此差异已折叠。
arch/arc/boot/dts/axs103_idu.dts
浏览文件 @ dbbc21bb
此差异已折叠。
arch/arc/configs/axs101_defconfig
浏览文件 @ dbbc21bb
此差异已折叠。
arch/arc/configs/haps_hs_defconfig 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
arch/arc/configs/haps_hs_smp_defconfig 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
arch/arc/configs/zebu_hs_defconfig 已删除 100644 → 0
浏览文件 @ f6fa11a3
此差异已折叠。
arch/arc/configs/zebu_hs_smp_defconfig 已删除 100644 → 0
浏览文件 @ f6fa11a3
此差异已折叠。
arch/arc/include/asm/arcregs.h
浏览文件 @ dbbc21bb
此差异已折叠。
arch/arc/include/asm/cacheflush.h
浏览文件 @ dbbc21bb
此差异已折叠。
arch/arc/include/asm/mcip.h 已删除 100644 → 0
浏览文件 @ f6fa11a3
此差异已折叠。
arch/arc/include/asm/mutex.h 已删除 100644 → 0
浏览文件 @ f6fa11a3
此差异已折叠。
arch/arc/include/asm/processor.h
浏览文件 @ dbbc21bb
此差异已折叠。
arch/arc/kernel/Makefile
浏览文件 @ dbbc21bb
此差异已折叠。
arch/arc/kernel/entry-arcv2.S
浏览文件 @ dbbc21bb
此差异已折叠。
arch/arc/kernel/entry-compact.S
浏览文件 @ dbbc21bb
此差异已折叠。
arch/arc/kernel/intc-arcv2.c
浏览文件 @ dbbc21bb
此差异已折叠。
arch/arc/kernel/mcip.c
浏览文件 @ dbbc21bb
此差异已折叠。
arch/arc/kernel/setup.c
浏览文件 @ dbbc21bb
此差异已折叠。
arch/arc/kernel/time.c 已删除 100644 → 0
浏览文件 @ f6fa11a3
此差异已折叠。
arch/arc/mm/cache.c
浏览文件 @ dbbc21bb
此差异已折叠。
arch/arc/mm/dma.c
浏览文件 @ dbbc21bb
此差异已折叠。
arch/arc/plat-axs10x/axs10x.c
浏览文件 @ dbbc21bb
此差异已折叠。
arch/arm/Kconfig
浏览文件 @ dbbc21bb
此差异已折叠。
arch/arm/Makefile
浏览文件 @ dbbc21bb
此差异已折叠。
arch/arm/boot/dts/Makefile
浏览文件 @ dbbc21bb
此差异已折叠。
arch/arm/boot/dts/am335x-evm.dts
浏览文件 @ dbbc21bb
此差异已折叠。
arch/arm/boot/dts/am335x-evmsk.dts
浏览文件 @ dbbc21bb
此差异已折叠。
arch/arm/boot/dts/am335x-icev2.dts
浏览文件 @ dbbc21bb
此差异已折叠。
arch/arm/boot/dts/am33xx.dtsi
浏览文件 @ dbbc21bb
此差异已折叠。
arch/arm/boot/dts/am3517.dtsi
浏览文件 @ dbbc21bb
此差异已折叠。
arch/arm/boot/dts/am4372.dtsi
浏览文件 @ dbbc21bb
此差异已折叠。
arch/arm/boot/dts/am571x-idk.dts 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
arch/arm/boot/dts/am572x-idk.dts
浏览文件 @ dbbc21bb
此差异已折叠。
arch/arm/boot/dts/armada-370-db.dts
浏览文件 @ dbbc21bb
此差异已折叠。
arch/arm/boot/dts/armada-370-rd.dts
浏览文件 @ dbbc21bb
此差异已折叠。
arch/arm/boot/dts/armada-370.dtsi
浏览文件 @ dbbc21bb
此差异已折叠。
arch/arm/boot/dts/armada-375-db.dts
浏览文件 @ dbbc21bb
此差异已折叠。
arch/arm/boot/dts/armada-375.dtsi
浏览文件 @ dbbc21bb
此差异已折叠。
arch/arm/boot/dts/armada-385-turris-omnia.dts 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
arch/arm/boot/dts/armada-38x.dtsi
浏览文件 @ dbbc21bb
此差异已折叠。
arch/arm/boot/dts/armada-39x.dtsi
浏览文件 @ dbbc21bb
此差异已折叠。
arch/arm/boot/dts/armada-xp-db.dts
浏览文件 @ dbbc21bb
此差异已折叠。
arch/arm/boot/dts/armada-xp-gp.dts
浏览文件 @ dbbc21bb
此差异已折叠。
arch/arm/boot/dts/armada-xp.dtsi
浏览文件 @ dbbc21bb
此差异已折叠。
arch/arm/boot/dts/artpec6.dtsi
浏览文件 @ dbbc21bb
此差异已折叠。
arch/arm/boot/dts/at91rm9200.dtsi
浏览文件 @ dbbc21bb
此差异已折叠。
arch/arm/boot/dts/at91sam9260.dtsi
浏览文件 @ dbbc21bb
此差异已折叠。
arch/arm/boot/dts/at91sam9260ek.dts
浏览文件 @ dbbc21bb
此差异已折叠。
arch/arm/boot/dts/at91sam9261.dtsi
浏览文件 @ dbbc21bb
此差异已折叠。
arch/arm/boot/dts/at91sam9263.dtsi
浏览文件 @ dbbc21bb
此差异已折叠。
arch/arm/boot/dts/at91sam9g45.dtsi
浏览文件 @ dbbc21bb
此差异已折叠。
arch/arm/boot/dts/at91sam9n12.dtsi
浏览文件 @ dbbc21bb
此差异已折叠。
arch/arm/boot/dts/at91sam9rl.dtsi
浏览文件 @ dbbc21bb
此差异已折叠。
arch/arm/boot/dts/at91sam9x5.dtsi
浏览文件 @ dbbc21bb
此差异已折叠。
arch/arm/boot/dts/bcm-cygnus.dtsi
浏览文件 @ dbbc21bb
此差异已折叠。
arch/arm/boot/dts/bcm-nsp.dtsi
浏览文件 @ dbbc21bb
此差异已折叠。
arch/arm/boot/dts/bcm2835-rpi-a.dts
浏览文件 @ dbbc21bb
此差异已折叠。
arch/arm/boot/dts/bcm2835-rpi-b.dts
浏览文件 @ dbbc21bb
此差异已折叠。
arch/arm/boot/dts/bcm2835-rpi.dtsi
浏览文件 @ dbbc21bb
此差异已折叠。
arch/arm/boot/dts/bcm2835.dtsi
浏览文件 @ dbbc21bb
此差异已折叠。
arch/arm/boot/dts/bcm2836.dtsi
浏览文件 @ dbbc21bb
此差异已折叠。
arch/arm/boot/dts/bcm283x.dtsi
浏览文件 @ dbbc21bb
此差异已折叠。
arch/arm/boot/dts/bcm4708-luxul-xap-1510.dts 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
arch/arm/boot/dts/bcm4709-tplink-archer-c9-v1.dts 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
arch/arm/boot/dts/bcm4709.dtsi 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
arch/arm/boot/dts/bcm47094-luxul-xwr-3100.dts 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
arch/arm/boot/dts/bcm47094-netgear-r8500.dts 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
arch/arm/boot/dts/bcm47094.dtsi 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
arch/arm/boot/dts/bcm47189-tenda-ac9.dts 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
arch/arm/boot/dts/bcm5301x-nand-cs0-bch4.dtsi 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
arch/arm/boot/dts/bcm5301x.dtsi
浏览文件 @ dbbc21bb
此差异已折叠。
arch/arm/boot/dts/bcm53573.dtsi 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
arch/arm/boot/dts/bcm958625k.dts
浏览文件 @ dbbc21bb
此差异已折叠。
arch/arm/boot/dts/cloudengines-pogoplug-series-3.dts 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
arch/arm/boot/dts/da850-lcdk.dts
浏览文件 @ dbbc21bb
此差异已折叠。
arch/arm/boot/dts/da850.dtsi
浏览文件 @ dbbc21bb
此差异已折叠。
arch/arm/boot/dts/dm814x.dtsi
浏览文件 @ dbbc21bb
此差异已折叠。
arch/arm/boot/dts/dm816x.dtsi
浏览文件 @ dbbc21bb
此差异已折叠。
arch/arm/boot/dts/dra7.dtsi
浏览文件 @ dbbc21bb
此差异已折叠。
arch/arm/boot/dts/dra71-evm.dts 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
arch/arm/boot/dts/dra72-evm-tps65917.dtsi 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
arch/arm/boot/dts/dra72-evm.dts
浏览文件 @ dbbc21bb
此差异已折叠。
arch/arm/boot/dts/emev2.dtsi
浏览文件 @ dbbc21bb
此差异已折叠。
arch/arm/boot/dts/exynos3250.dtsi
浏览文件 @ dbbc21bb
此差异已折叠。
arch/arm/boot/dts/exynos4.dtsi
浏览文件 @ dbbc21bb
此差异已折叠。
arch/arm/boot/dts/exynos4210.dtsi
浏览文件 @ dbbc21bb
此差异已折叠。
arch/arm/boot/dts/exynos4412-itop-elite.dts 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
arch/arm/boot/dts/exynos4412-itop-scp-core.dtsi 0 → 100644
浏览文件 @ dbbc21bb
此差异已折叠。
arch/arm/boot/dts/exynos4415-pinctrl.dtsi 已删除 100644 → 0
浏览文件 @ f6fa11a3
此差异已折叠。
arch/arm/boot/dts/exynos4415.dtsi 已删除 100644 → 0
浏览文件 @ f6fa11a3
此差异已折叠。
arch/arm/boot/dts/exynos4x12.dtsi
浏览文件 @ dbbc21bb
此差异已折叠。
arch/arm/boot/dts/exynos5.dtsi
浏览文件 @ dbbc21bb
此差异已折叠。
arch/arm/boot/dts/exynos5250.dtsi
浏览文件 @ dbbc21bb
此差异已折叠。
arch/arm/boot/dts/exynos5260.dtsi
浏览文件 @ dbbc21bb
此差异已折叠。
arch/arm/boot/dts/exynos5410.dtsi
浏览文件 @ dbbc21bb
此差异已折叠。
arch/arm/boot/dts/exynos5420.dtsi
浏览文件 @ dbbc21bb
此差异已折叠。
arch/arm/boot/dts/exynos5440.dtsi
浏览文件 @ dbbc21bb
此差异已折叠。
arch/arm/boot/dts/exynos54xx.dtsi
浏览文件 @ dbbc21bb
此差异已折叠。
arch/arm/boot/dts/hi3620.dtsi
浏览文件 @ dbbc21bb
此差异已折叠。
arch/arm/boot/dts/hip01.dtsi
浏览文件 @ dbbc21bb
此差异已折叠。
arch/arm/boot/dts/hisi-x5hd2.dtsi
浏览文件 @ dbbc21bb
此差异已折叠。
arch/arm/boot/dts/imx1.dtsi
浏览文件 @ dbbc21bb
此差异已折叠。
arch/arm/boot/dts/imx23.dtsi
浏览文件 @ dbbc21bb
此差异已折叠。
arch/arm/boot/dts/imx25.dtsi
浏览文件 @ dbbc21bb
此差异已折叠。
arch/arm/boot/dts/imx27.dtsi
浏览文件 @ dbbc21bb
此差异已折叠。
arch/arm/boot/dts/imx28-m28.dtsi
浏览文件 @ dbbc21bb
此差异已折叠。
arch/arm/boot/dts/imx28-m28evk.dts
浏览文件 @ dbbc21bb
此差异已折叠。
arch/arm/boot/dts/imx28.dtsi
浏览文件 @ dbbc21bb
此差异已折叠。
arch/arm/boot/dts/imx31.dtsi
浏览文件 @ dbbc21bb
此差异已折叠。
arch/arm/boot/dts/imx35.dtsi
浏览文件 @ dbbc21bb
此差异已折叠。
Markdown is supported
0% 或 .
You are about to add 0 people to the discussion. Proceed with caution.
先完成此消息的编辑！
想要评论请 注册 或