Merge branch 'release' of git://git.kernel.org/pub/scm/linux/kernel/git/lenb/linux...
authorLinus Torvalds <torvalds@linux-foundation.org>
Sun, 5 Apr 2009 18:16:25 +0000 (11:16 -0700)
committerLinus Torvalds <torvalds@linux-foundation.org>
Sun, 5 Apr 2009 18:16:25 +0000 (11:16 -0700)
* 'release' of git://git.kernel.org/pub/scm/linux/kernel/git/lenb/linux-acpi-2.6: (140 commits)
  ACPI: processor: use .notify method instead of installing handler directly
  ACPI: button: use .notify method instead of installing handler directly
  ACPI: support acpi_device_ops .notify methods
  toshiba-acpi: remove MAINTAINERS entry
  ACPI: battery: asynchronous init
  acer-wmi: Update copyright notice & documentation
  acer-wmi: Cleanup the failure cleanup handling
  acer-wmi: Blacklist Acer Aspire One
  video: build fix
  thinkpad-acpi: rework brightness support
  thinkpad-acpi: enhanced debugging messages for the fan subdriver
  thinkpad-acpi: enhanced debugging messages for the hotkey subdriver
  thinkpad-acpi: enhanced debugging messages for rfkill subdrivers
  thinkpad-acpi: restrict access to some firmware LEDs
  thinkpad-acpi: remove HKEY disable functionality
  thinkpad-acpi: add new debug helpers and warn of deprecated atts
  thinkpad-acpi: add missing log levels
  thinkpad-acpi: cleanup debug helpers
  thinkpad-acpi: documentation cleanup
  thinkpad-acpi: drop ibm-acpi alias
  ...

1036 files changed:
Documentation/ABI/testing/debugfs-kmemtrace [new file with mode: 0644]
Documentation/filesystems/pohmelfs/design_notes.txt [new file with mode: 0644]
Documentation/filesystems/pohmelfs/info.txt [new file with mode: 0644]
Documentation/filesystems/pohmelfs/network_protocol.txt [new file with mode: 0644]
Documentation/ftrace.txt
Documentation/kernel-parameters.txt
Documentation/sysrq.txt
Documentation/tracepoints.txt
Documentation/vm/kmemtrace.txt [new file with mode: 0644]
MAINTAINERS
arch/Kconfig
arch/alpha/include/asm/ftrace.h [new file with mode: 0644]
arch/alpha/include/asm/hardirq.h
arch/arm/boot/compressed/misc.c
arch/avr32/Kconfig
arch/avr32/Makefile
arch/avr32/boards/atngw100/evklcd10x.c
arch/avr32/boards/atngw100/setup.c
arch/avr32/boards/atstk1000/atstk1002.c
arch/avr32/boards/atstk1000/atstk1003.c
arch/avr32/boards/atstk1000/atstk1004.c
arch/avr32/boards/favr-32/setup.c
arch/avr32/boards/hammerhead/setup.c
arch/avr32/boards/merisc/Kconfig [new file with mode: 0644]
arch/avr32/boards/merisc/Makefile [new file with mode: 0644]
arch/avr32/boards/merisc/display.c [new file with mode: 0644]
arch/avr32/boards/merisc/flash.c [new file with mode: 0644]
arch/avr32/boards/merisc/merisc.h [new file with mode: 0644]
arch/avr32/boards/merisc/merisc_sysfs.c [new file with mode: 0644]
arch/avr32/boards/merisc/setup.c [new file with mode: 0644]
arch/avr32/boards/mimc200/setup.c
arch/avr32/configs/merisc_defconfig [new file with mode: 0644]
arch/avr32/include/asm/ftrace.h [new file with mode: 0644]
arch/avr32/include/asm/hardirq.h
arch/avr32/mach-at32ap/at32ap700x.c
arch/avr32/mach-at32ap/include/mach/at32ap700x.h
arch/avr32/mach-at32ap/include/mach/board.h
arch/blackfin/include/asm/ftrace.h [new file with mode: 0644]
arch/cris/include/asm/ftrace.h [new file with mode: 0644]
arch/h8300/include/asm/ftrace.h [new file with mode: 0644]
arch/ia64/Kconfig
arch/ia64/include/asm/ftrace.h [new file with mode: 0644]
arch/ia64/include/asm/hardirq.h
arch/ia64/kernel/Makefile
arch/ia64/kernel/entry.S
arch/ia64/kernel/ftrace.c [new file with mode: 0644]
arch/ia64/kernel/ia64_ksyms.c
arch/m68k/include/asm/ftrace.h [new file with mode: 0644]
arch/mips/include/asm/ftrace.h [new file with mode: 0644]
arch/powerpc/include/asm/mmzone.h
arch/powerpc/kernel/ftrace.c
arch/sh/Kconfig
arch/sh/boards/board-ap325rxa.c
arch/sh/boards/board-urquell.c
arch/sh/boards/mach-migor/setup.c
arch/sh/configs/ap325rxa_defconfig
arch/sh/configs/cayman_defconfig
arch/sh/configs/dreamcast_defconfig
arch/sh/configs/edosk7705_defconfig
arch/sh/configs/edosk7760_defconfig
arch/sh/configs/espt_defconfig
arch/sh/configs/hp6xx_defconfig
arch/sh/configs/landisk_defconfig
arch/sh/configs/lboxre2_defconfig
arch/sh/configs/magicpanelr2_defconfig
arch/sh/configs/microdev_defconfig
arch/sh/configs/migor_defconfig
arch/sh/configs/polaris_defconfig
arch/sh/configs/r7780mp_defconfig
arch/sh/configs/r7785rp_defconfig
arch/sh/configs/rsk7201_defconfig
arch/sh/configs/rsk7203_defconfig
arch/sh/configs/rts7751r2d1_defconfig
arch/sh/configs/rts7751r2dplus_defconfig
arch/sh/configs/sdk7780_defconfig
arch/sh/configs/se7206_defconfig
arch/sh/configs/se7343_defconfig
arch/sh/configs/se7619_defconfig
arch/sh/configs/se7705_defconfig
arch/sh/configs/se7712_defconfig
arch/sh/configs/se7721_defconfig
arch/sh/configs/se7722_defconfig
arch/sh/configs/se7750_defconfig
arch/sh/configs/se7751_defconfig
arch/sh/configs/se7780_defconfig
arch/sh/configs/sh03_defconfig
arch/sh/configs/sh7710voipgw_defconfig
arch/sh/configs/sh7763rdp_defconfig
arch/sh/configs/sh7785lcr_32bit_defconfig
arch/sh/configs/sh7785lcr_defconfig
arch/sh/configs/shmin_defconfig
arch/sh/configs/shx3_defconfig
arch/sh/configs/snapgear_defconfig
arch/sh/configs/systemh_defconfig
arch/sh/configs/titan_defconfig
arch/sh/configs/ul2_defconfig
arch/sh/configs/urquell_defconfig
arch/sh/drivers/dma/Kconfig
arch/sh/drivers/pci/ops-sh7785lcr.c
arch/sh/drivers/pci/pci-sh7780.c
arch/sh/include/asm/mmu.h
arch/sh/include/asm/processor_32.h
arch/sh/include/asm/ptrace.h
arch/sh/include/asm/system.h
arch/sh/include/asm/system_32.h
arch/sh/include/cpu-sh4/cpu/sh7786.h
arch/sh/kernel/cpu/sh3/entry.S
arch/sh/kernel/cpu/sh4/probe.c
arch/sh/kernel/cpu/sh4a/pinmux-sh7786.c
arch/sh/kernel/idle.c
arch/sh/kernel/io_trapped.c
arch/sh/kernel/process_32.c
arch/sh/kernel/ptrace_32.c
arch/sh/kernel/setup.c
arch/sh/kernel/traps_32.c
arch/sh/mm/Kconfig
arch/sparc/include/asm/mmzone.h
arch/um/include/asm/ftrace.h [new file with mode: 0644]
arch/x86/Kconfig
arch/x86/include/asm/cacheflush.h
arch/x86/include/asm/cpumask.h
arch/x86/include/asm/fixmap.h
arch/x86/include/asm/ftrace.h
arch/x86/include/asm/pci.h
arch/x86/include/asm/processor.h
arch/x86/include/asm/ptrace-abi.h
arch/x86/include/asm/smp.h
arch/x86/include/asm/thread_info.h
arch/x86/include/asm/topology.h
arch/x86/kernel/Makefile
arch/x86/kernel/alternative.c
arch/x86/kernel/apic/bigsmp_32.c
arch/x86/kernel/apic/es7000_32.c
arch/x86/kernel/apic/nmi.c
arch/x86/kernel/apic/numaq_32.c
arch/x86/kernel/apic/probe_32.c
arch/x86/kernel/apic/summit_32.c
arch/x86/kernel/apm_32.c
arch/x86/kernel/cpu/common.c
arch/x86/kernel/cpu/cpufreq/acpi-cpufreq.c
arch/x86/kernel/cpu/cpufreq/p4-clockmod.c
arch/x86/kernel/cpu/cpufreq/powernow-k8.c
arch/x86/kernel/cpu/cpufreq/speedstep-ich.c
arch/x86/kernel/cpu/intel_cacheinfo.c
arch/x86/kernel/cpu/mcheck/mce_64.c
arch/x86/kernel/cpu/mcheck/mce_amd_64.c
arch/x86/kernel/cpu/mcheck/mce_intel_64.c
arch/x86/kernel/cpu/proc.c
arch/x86/kernel/dumpstack.c
arch/x86/kernel/ftrace.c
arch/x86/kernel/kprobes.c
arch/x86/kernel/microcode_amd.c
arch/x86/kernel/microcode_core.c
arch/x86/kernel/microcode_intel.c
arch/x86/kernel/process.c
arch/x86/kernel/ptrace.c
arch/x86/kernel/smpboot.c
arch/x86/kernel/tlb_uv.c
arch/x86/kvm/Kconfig
arch/x86/mm/Makefile
arch/x86/mm/init_32.c
arch/x86/mm/init_64.c
arch/x86/mm/mmio-mod.c
arch/x86/mm/numa.c [new file with mode: 0644]
arch/x86/mm/numa_64.c
arch/x86/oprofile/op_model_p4.c
arch/x86/xen/smp.c
arch/xtensa/include/asm/ftrace.h [new file with mode: 0644]
block/Kconfig
block/Makefile
block/blk.h
drivers/base/node.c
drivers/char/sysrq.c
drivers/clocksource/sh_cmt.c
drivers/input/keyboard/sh_keysc.c
drivers/input/touchscreen/migor_ts.c
drivers/mmc/card/block.c
drivers/mmc/core/bus.c
drivers/mmc/core/core.c
drivers/mmc/core/debugfs.c
drivers/mmc/core/sdio_cis.c
drivers/mmc/core/sdio_ops.c
drivers/mmc/host/Kconfig
drivers/mmc/host/Makefile
drivers/mmc/host/atmel-mci.c
drivers/mmc/host/mmc_spi.c
drivers/mmc/host/mvsdio.c [new file with mode: 0644]
drivers/mmc/host/mvsdio.h [new file with mode: 0644]
drivers/mmc/host/omap_hsmmc.c
drivers/mmc/host/sdhci-of.c [new file with mode: 0644]
drivers/mmc/host/sdhci.c
drivers/mmc/host/sdhci.h
drivers/mmc/host/tmio_mmc.c
drivers/mmc/host/tmio_mmc.h
drivers/mtd/nand/nand_base.c
drivers/oprofile/buffer_sync.c
drivers/oprofile/buffer_sync.h
drivers/oprofile/cpu_buffer.c
drivers/oprofile/oprof.c
drivers/pci/pci-driver.c
drivers/rtc/rtc-sh.c
drivers/serial/atmel_serial.c
drivers/sh/intc.c
drivers/staging/Kconfig
drivers/staging/Makefile
drivers/staging/agnx/agnx.h
drivers/staging/agnx/debug.h
drivers/staging/agnx/pci.c
drivers/staging/agnx/phy.c
drivers/staging/agnx/rf.c
drivers/staging/agnx/sta.c
drivers/staging/agnx/sta.h
drivers/staging/agnx/table.c
drivers/staging/agnx/xmit.c
drivers/staging/altpciechdma/altpciechdma.c
drivers/staging/android/binder.c
drivers/staging/android/ram_console.c
drivers/staging/asus_oled/asus_oled.c
drivers/staging/at76_usb/TODO
drivers/staging/at76_usb/at76_usb.c
drivers/staging/at76_usb/at76_usb.h
drivers/staging/b3dfg/Kconfig [new file with mode: 0644]
drivers/staging/b3dfg/Makefile [new file with mode: 0644]
drivers/staging/b3dfg/TODO [new file with mode: 0644]
drivers/staging/b3dfg/b3dfg.c [new file with mode: 0644]
drivers/staging/comedi/Kconfig
drivers/staging/comedi/comedi.h
drivers/staging/comedi/comedi_compat32.c
drivers/staging/comedi/comedi_fops.c
drivers/staging/comedi/comedi_fops.h
drivers/staging/comedi/comedi_ksyms.c
drivers/staging/comedi/comedi_rt.h
drivers/staging/comedi/comedidev.h
drivers/staging/comedi/comedilib.h
drivers/staging/comedi/drivers.c
drivers/staging/comedi/drivers/8253.h [new file with mode: 0644]
drivers/staging/comedi/drivers/8255.c [new file with mode: 0644]
drivers/staging/comedi/drivers/8255.h [new file with mode: 0644]
drivers/staging/comedi/drivers/Makefile
drivers/staging/comedi/drivers/acl7225b.c [new file with mode: 0644]
drivers/staging/comedi/drivers/addi-data/APCI1710_82x54.c [new file with mode: 0644]
drivers/staging/comedi/drivers/addi-data/APCI1710_82x54.h [new file with mode: 0644]
drivers/staging/comedi/drivers/addi-data/APCI1710_Chrono.c [new file with mode: 0644]
drivers/staging/comedi/drivers/addi-data/APCI1710_Chrono.h [new file with mode: 0644]
drivers/staging/comedi/drivers/addi-data/APCI1710_Dig_io.c [new file with mode: 0644]
drivers/staging/comedi/drivers/addi-data/APCI1710_Dig_io.h [new file with mode: 0644]
drivers/staging/comedi/drivers/addi-data/APCI1710_INCCPT.c [new file with mode: 0644]
drivers/staging/comedi/drivers/addi-data/APCI1710_INCCPT.h [new file with mode: 0644]
drivers/staging/comedi/drivers/addi-data/APCI1710_Inp_cpt.c [new file with mode: 0644]
drivers/staging/comedi/drivers/addi-data/APCI1710_Inp_cpt.h [new file with mode: 0644]
drivers/staging/comedi/drivers/addi-data/APCI1710_Pwm.c [new file with mode: 0644]
drivers/staging/comedi/drivers/addi-data/APCI1710_Pwm.h [new file with mode: 0644]
drivers/staging/comedi/drivers/addi-data/APCI1710_Ssi.c [new file with mode: 0644]
drivers/staging/comedi/drivers/addi-data/APCI1710_Ssi.h [new file with mode: 0644]
drivers/staging/comedi/drivers/addi-data/APCI1710_Tor.c [new file with mode: 0644]
drivers/staging/comedi/drivers/addi-data/APCI1710_Tor.h [new file with mode: 0644]
drivers/staging/comedi/drivers/addi-data/APCI1710_Ttl.c [new file with mode: 0644]
drivers/staging/comedi/drivers/addi-data/APCI1710_Ttl.h [new file with mode: 0644]
drivers/staging/comedi/drivers/addi-data/addi_amcc_S5920.c [new file with mode: 0644]
drivers/staging/comedi/drivers/addi-data/addi_amcc_S5920.h [new file with mode: 0644]
drivers/staging/comedi/drivers/addi-data/addi_amcc_s5933.h [new file with mode: 0644]
drivers/staging/comedi/drivers/addi-data/addi_common.c [new file with mode: 0644]
drivers/staging/comedi/drivers/addi-data/addi_common.h [new file with mode: 0644]
drivers/staging/comedi/drivers/addi-data/addi_eeprom.c [new file with mode: 0644]
drivers/staging/comedi/drivers/addi-data/amcc_s5933_58.h [new file with mode: 0644]
drivers/staging/comedi/drivers/addi-data/hwdrv_APCI1710.c [new file with mode: 0644]
drivers/staging/comedi/drivers/addi-data/hwdrv_APCI1710.h [new file with mode: 0644]
drivers/staging/comedi/drivers/addi-data/hwdrv_apci035.c [new file with mode: 0644]
drivers/staging/comedi/drivers/addi-data/hwdrv_apci035.h [new file with mode: 0644]
drivers/staging/comedi/drivers/addi-data/hwdrv_apci1032.c [new file with mode: 0644]
drivers/staging/comedi/drivers/addi-data/hwdrv_apci1032.h [new file with mode: 0644]
drivers/staging/comedi/drivers/addi-data/hwdrv_apci1500.c [new file with mode: 0644]
drivers/staging/comedi/drivers/addi-data/hwdrv_apci1500.h [new file with mode: 0644]
drivers/staging/comedi/drivers/addi-data/hwdrv_apci1516.c [new file with mode: 0644]
drivers/staging/comedi/drivers/addi-data/hwdrv_apci1516.h [new file with mode: 0644]
drivers/staging/comedi/drivers/addi-data/hwdrv_apci1564.c [new file with mode: 0644]
drivers/staging/comedi/drivers/addi-data/hwdrv_apci1564.h [new file with mode: 0644]
drivers/staging/comedi/drivers/addi-data/hwdrv_apci16xx.c [new file with mode: 0644]
drivers/staging/comedi/drivers/addi-data/hwdrv_apci16xx.h [new file with mode: 0644]
drivers/staging/comedi/drivers/addi-data/hwdrv_apci2016.c [new file with mode: 0644]
drivers/staging/comedi/drivers/addi-data/hwdrv_apci2016.h [new file with mode: 0644]
drivers/staging/comedi/drivers/addi-data/hwdrv_apci2032.c [new file with mode: 0644]
drivers/staging/comedi/drivers/addi-data/hwdrv_apci2032.h [new file with mode: 0644]
drivers/staging/comedi/drivers/addi-data/hwdrv_apci2200.c [new file with mode: 0644]
drivers/staging/comedi/drivers/addi-data/hwdrv_apci2200.h [new file with mode: 0644]
drivers/staging/comedi/drivers/addi-data/hwdrv_apci3120.c [new file with mode: 0644]
drivers/staging/comedi/drivers/addi-data/hwdrv_apci3120.h [new file with mode: 0644]
drivers/staging/comedi/drivers/addi-data/hwdrv_apci3200.c [new file with mode: 0644]
drivers/staging/comedi/drivers/addi-data/hwdrv_apci3200.h [new file with mode: 0644]
drivers/staging/comedi/drivers/addi-data/hwdrv_apci3501.c [new file with mode: 0644]
drivers/staging/comedi/drivers/addi-data/hwdrv_apci3501.h [new file with mode: 0644]
drivers/staging/comedi/drivers/addi-data/hwdrv_apci3xxx.c [new file with mode: 0644]
drivers/staging/comedi/drivers/addi-data/hwdrv_apci3xxx.h [new file with mode: 0644]
drivers/staging/comedi/drivers/addi_apci_035.c [new file with mode: 0644]
drivers/staging/comedi/drivers/addi_apci_1032.c [new file with mode: 0644]
drivers/staging/comedi/drivers/addi_apci_1500.c [new file with mode: 0644]
drivers/staging/comedi/drivers/addi_apci_1516.c [new file with mode: 0644]
drivers/staging/comedi/drivers/addi_apci_1564.c [new file with mode: 0644]
drivers/staging/comedi/drivers/addi_apci_16xx.c [new file with mode: 0644]
drivers/staging/comedi/drivers/addi_apci_1710.c [new file with mode: 0644]
drivers/staging/comedi/drivers/addi_apci_2016.c [new file with mode: 0644]
drivers/staging/comedi/drivers/addi_apci_2032.c [new file with mode: 0644]
drivers/staging/comedi/drivers/addi_apci_2200.c [new file with mode: 0644]
drivers/staging/comedi/drivers/addi_apci_3001.c [new file with mode: 0644]
drivers/staging/comedi/drivers/addi_apci_3120.c [new file with mode: 0644]
drivers/staging/comedi/drivers/addi_apci_3200.c [new file with mode: 0644]
drivers/staging/comedi/drivers/addi_apci_3300.c [new file with mode: 0644]
drivers/staging/comedi/drivers/addi_apci_3501.c [new file with mode: 0644]
drivers/staging/comedi/drivers/addi_apci_3xxx.c [new file with mode: 0644]
drivers/staging/comedi/drivers/addi_apci_all.c [new file with mode: 0644]
drivers/staging/comedi/drivers/adl_pci6208.c [new file with mode: 0644]
drivers/staging/comedi/drivers/adl_pci7296.c [new file with mode: 0644]
drivers/staging/comedi/drivers/adl_pci7432.c [new file with mode: 0644]
drivers/staging/comedi/drivers/adl_pci8164.c [new file with mode: 0644]
drivers/staging/comedi/drivers/adl_pci9111.c [new file with mode: 0644]
drivers/staging/comedi/drivers/adl_pci9118.c [new file with mode: 0644]
drivers/staging/comedi/drivers/adq12b.c [new file with mode: 0644]
drivers/staging/comedi/drivers/adv_pci1710.c [new file with mode: 0644]
drivers/staging/comedi/drivers/adv_pci1723.c [new file with mode: 0644]
drivers/staging/comedi/drivers/adv_pci_dio.c [new file with mode: 0644]
drivers/staging/comedi/drivers/aio_aio12_8.c [new file with mode: 0644]
drivers/staging/comedi/drivers/aio_iiro_16.c [new file with mode: 0644]
drivers/staging/comedi/drivers/am9513.h [new file with mode: 0644]
drivers/staging/comedi/drivers/amcc_s5933.h [new file with mode: 0644]
drivers/staging/comedi/drivers/amplc_dio200.c [new file with mode: 0644]
drivers/staging/comedi/drivers/amplc_pc236.c [new file with mode: 0644]
drivers/staging/comedi/drivers/amplc_pc263.c [new file with mode: 0644]
drivers/staging/comedi/drivers/amplc_pci224.c [new file with mode: 0644]
drivers/staging/comedi/drivers/amplc_pci230.c [new file with mode: 0644]
drivers/staging/comedi/drivers/c6xdigio.c [new file with mode: 0644]
drivers/staging/comedi/drivers/cb_das16_cs.c [new file with mode: 0644]
drivers/staging/comedi/drivers/cb_pcidas.c [new file with mode: 0644]
drivers/staging/comedi/drivers/cb_pcidas64.c [new file with mode: 0644]
drivers/staging/comedi/drivers/cb_pcidda.c [new file with mode: 0644]
drivers/staging/comedi/drivers/cb_pcidio.c [new file with mode: 0644]
drivers/staging/comedi/drivers/cb_pcimdas.c [new file with mode: 0644]
drivers/staging/comedi/drivers/cb_pcimdda.c [new file with mode: 0644]
drivers/staging/comedi/drivers/comedi_bond.c
drivers/staging/comedi/drivers/comedi_fc.c
drivers/staging/comedi/drivers/comedi_fc.h
drivers/staging/comedi/drivers/comedi_parport.c
drivers/staging/comedi/drivers/comedi_rt_timer.c [new file with mode: 0644]
drivers/staging/comedi/drivers/comedi_test.c
drivers/staging/comedi/drivers/contec_pci_dio.c [new file with mode: 0644]
drivers/staging/comedi/drivers/daqboard2000.c [new file with mode: 0644]
drivers/staging/comedi/drivers/das08.c [new file with mode: 0644]
drivers/staging/comedi/drivers/das08.h [new file with mode: 0644]
drivers/staging/comedi/drivers/das08_cs.c [new file with mode: 0644]
drivers/staging/comedi/drivers/das16.c [new file with mode: 0644]
drivers/staging/comedi/drivers/das16m1.c [new file with mode: 0644]
drivers/staging/comedi/drivers/das1800.c [new file with mode: 0644]
drivers/staging/comedi/drivers/das6402.c [new file with mode: 0644]
drivers/staging/comedi/drivers/das800.c [new file with mode: 0644]
drivers/staging/comedi/drivers/dmm32at.c [new file with mode: 0644]
drivers/staging/comedi/drivers/dt2801.c [new file with mode: 0644]
drivers/staging/comedi/drivers/dt2811.c [new file with mode: 0644]
drivers/staging/comedi/drivers/dt2814.c [new file with mode: 0644]
drivers/staging/comedi/drivers/dt2815.c [new file with mode: 0644]
drivers/staging/comedi/drivers/dt2817.c [new file with mode: 0644]
drivers/staging/comedi/drivers/dt282x.c [new file with mode: 0644]
drivers/staging/comedi/drivers/dt3000.c [new file with mode: 0644]
drivers/staging/comedi/drivers/dt9812.c
drivers/staging/comedi/drivers/fl512.c [new file with mode: 0644]
drivers/staging/comedi/drivers/gsc_hpdi.c [new file with mode: 0644]
drivers/staging/comedi/drivers/icp_multi.c
drivers/staging/comedi/drivers/icp_multi.h
drivers/staging/comedi/drivers/ii_pci20kc.c [new file with mode: 0644]
drivers/staging/comedi/drivers/jr3_pci.c [new file with mode: 0644]
drivers/staging/comedi/drivers/jr3_pci.h [new file with mode: 0644]
drivers/staging/comedi/drivers/ke_counter.c [new file with mode: 0644]
drivers/staging/comedi/drivers/me4000.c
drivers/staging/comedi/drivers/me4000.h
drivers/staging/comedi/drivers/me_daq.c
drivers/staging/comedi/drivers/mite.c
drivers/staging/comedi/drivers/mite.h
drivers/staging/comedi/drivers/mpc624.c [new file with mode: 0644]
drivers/staging/comedi/drivers/mpc8260cpm.c [new file with mode: 0644]
drivers/staging/comedi/drivers/multiq3.c [new file with mode: 0644]
drivers/staging/comedi/drivers/ni_6527.c [new file with mode: 0644]
drivers/staging/comedi/drivers/ni_65xx.c [new file with mode: 0644]
drivers/staging/comedi/drivers/ni_660x.c [new file with mode: 0644]
drivers/staging/comedi/drivers/ni_670x.c [new file with mode: 0644]
drivers/staging/comedi/drivers/ni_at_a2150.c [new file with mode: 0644]
drivers/staging/comedi/drivers/ni_at_ao.c [new file with mode: 0644]
drivers/staging/comedi/drivers/ni_atmio.c [new file with mode: 0644]
drivers/staging/comedi/drivers/ni_atmio16d.c [new file with mode: 0644]
drivers/staging/comedi/drivers/ni_daq_700.c [new file with mode: 0644]
drivers/staging/comedi/drivers/ni_daq_dio24.c [new file with mode: 0644]
drivers/staging/comedi/drivers/ni_labpc.c [new file with mode: 0644]
drivers/staging/comedi/drivers/ni_labpc.h [new file with mode: 0644]
drivers/staging/comedi/drivers/ni_labpc_cs.c [new file with mode: 0644]
drivers/staging/comedi/drivers/ni_mio_common.c [new file with mode: 0644]
drivers/staging/comedi/drivers/ni_mio_cs.c [new file with mode: 0644]
drivers/staging/comedi/drivers/ni_pcidio.c [new file with mode: 0644]
drivers/staging/comedi/drivers/ni_pcimio.c [new file with mode: 0644]
drivers/staging/comedi/drivers/ni_stc.h [new file with mode: 0644]
drivers/staging/comedi/drivers/ni_tio.c [new file with mode: 0644]
drivers/staging/comedi/drivers/ni_tio.h [new file with mode: 0644]
drivers/staging/comedi/drivers/ni_tio_internal.h [new file with mode: 0644]
drivers/staging/comedi/drivers/ni_tiocmd.c [new file with mode: 0644]
drivers/staging/comedi/drivers/pcl711.c [new file with mode: 0644]
drivers/staging/comedi/drivers/pcl724.c [new file with mode: 0644]
drivers/staging/comedi/drivers/pcl725.c [new file with mode: 0644]
drivers/staging/comedi/drivers/pcl726.c [new file with mode: 0644]
drivers/staging/comedi/drivers/pcl730.c [new file with mode: 0644]
drivers/staging/comedi/drivers/pcl812.c [new file with mode: 0644]
drivers/staging/comedi/drivers/pcl816.c [new file with mode: 0644]
drivers/staging/comedi/drivers/pcl818.c [new file with mode: 0644]
drivers/staging/comedi/drivers/pcm3724.c [new file with mode: 0644]
drivers/staging/comedi/drivers/pcm3730.c [new file with mode: 0644]
drivers/staging/comedi/drivers/pcmad.c [new file with mode: 0644]
drivers/staging/comedi/drivers/pcmda12.c [new file with mode: 0644]
drivers/staging/comedi/drivers/pcmmio.c [new file with mode: 0644]
drivers/staging/comedi/drivers/pcmuio.c [new file with mode: 0644]
drivers/staging/comedi/drivers/plx9052.h [new file with mode: 0644]
drivers/staging/comedi/drivers/plx9080.h
drivers/staging/comedi/drivers/poc.c [new file with mode: 0644]
drivers/staging/comedi/drivers/quatech_daqp_cs.c [new file with mode: 0644]
drivers/staging/comedi/drivers/rtd520.c
drivers/staging/comedi/drivers/rtd520.h
drivers/staging/comedi/drivers/rti800.c [new file with mode: 0644]
drivers/staging/comedi/drivers/rti802.c [new file with mode: 0644]
drivers/staging/comedi/drivers/s526.c [new file with mode: 0644]
drivers/staging/comedi/drivers/s626.c
drivers/staging/comedi/drivers/s626.h
drivers/staging/comedi/drivers/serial2002.c [new file with mode: 0644]
drivers/staging/comedi/drivers/skel.c [new file with mode: 0644]
drivers/staging/comedi/drivers/ssv_dnp.c [new file with mode: 0644]
drivers/staging/comedi/drivers/unioxx5.c [new file with mode: 0644]
drivers/staging/comedi/drivers/usbdux.c
drivers/staging/comedi/drivers/usbduxfast.c
drivers/staging/comedi/interrupt.h
drivers/staging/comedi/kcomedilib/data.c
drivers/staging/comedi/kcomedilib/dio.c
drivers/staging/comedi/kcomedilib/get.c
drivers/staging/comedi/kcomedilib/kcomedilib_main.c
drivers/staging/comedi/kcomedilib/ksyms.c
drivers/staging/comedi/pci_ids.h
drivers/staging/comedi/proc.c
drivers/staging/comedi/range.c
drivers/staging/comedi/rt.c
drivers/staging/comedi/rt_pend_tq.c
drivers/staging/dst/Kconfig [new file with mode: 0644]
drivers/staging/dst/Makefile [new file with mode: 0644]
drivers/staging/dst/crypto.c [new file with mode: 0644]
drivers/staging/dst/dcore.c [new file with mode: 0644]
drivers/staging/dst/export.c [new file with mode: 0644]
drivers/staging/dst/state.c [new file with mode: 0644]
drivers/staging/dst/thread_pool.c [new file with mode: 0644]
drivers/staging/dst/trans.c [new file with mode: 0644]
drivers/staging/echo/bit_operations.h
drivers/staging/echo/echo.c
drivers/staging/echo/echo.h
drivers/staging/echo/fir.h
drivers/staging/echo/mmx.h
drivers/staging/epl/Benchmark.h
drivers/staging/epl/Debug.h
drivers/staging/epl/Edrv8139.c
drivers/staging/epl/EdrvFec.h
drivers/staging/epl/EdrvFec5282.h [deleted file]
drivers/staging/epl/EdrvSim.h
drivers/staging/epl/Epl.h
drivers/staging/epl/EplAmi.h
drivers/staging/epl/EplApiGeneric.c
drivers/staging/epl/EplApiLinuxKernel.c
drivers/staging/epl/EplApiProcessImage.c
drivers/staging/epl/EplDll.h
drivers/staging/epl/EplDllCal.h
drivers/staging/epl/EplDllk.c
drivers/staging/epl/EplDllkCal.c
drivers/staging/epl/EplDlluCal.c
drivers/staging/epl/EplErrorHandlerk.c
drivers/staging/epl/EplEvent.h
drivers/staging/epl/EplEventk.c
drivers/staging/epl/EplEventu.c
drivers/staging/epl/EplFrame.h
drivers/staging/epl/EplIdentu.c
drivers/staging/epl/EplInc.h
drivers/staging/epl/EplInstDef.h
drivers/staging/epl/EplNmt.h
drivers/staging/epl/EplNmtCnu.c
drivers/staging/epl/EplNmtMnu.c
drivers/staging/epl/EplNmtk.c
drivers/staging/epl/EplNmtkCal.c
drivers/staging/epl/EplNmtu.c
drivers/staging/epl/EplNmtuCal.c
drivers/staging/epl/EplObd.c
drivers/staging/epl/EplObd.h
drivers/staging/epl/EplObdMacro.h
drivers/staging/epl/EplObdkCal.c
drivers/staging/epl/EplObdu.c
drivers/staging/epl/EplObduCal.c
drivers/staging/epl/EplObjDef.h [deleted file]
drivers/staging/epl/EplPdo.h
drivers/staging/epl/EplPdok.c
drivers/staging/epl/EplPdou.c
drivers/staging/epl/EplSdo.h
drivers/staging/epl/EplSdoAsndu.c
drivers/staging/epl/EplSdoAsySequ.c
drivers/staging/epl/EplSdoComu.c
drivers/staging/epl/EplSdoUdpu.c
drivers/staging/epl/EplStatusu.c
drivers/staging/epl/EplTarget.h
drivers/staging/epl/EplTimer.h
drivers/staging/epl/EplTimeruLinuxKernel.c
drivers/staging/epl/EplTimeruNull.c [deleted file]
drivers/staging/epl/EplTimeruWin32.c [deleted file]
drivers/staging/epl/SharedBuff.c
drivers/staging/epl/SharedBuff.h
drivers/staging/epl/ShbIpc-LinuxKernel.c
drivers/staging/epl/ShbIpc-Win32.c [deleted file]
drivers/staging/epl/ShbIpc.h
drivers/staging/epl/TimerHighReskX86.c
drivers/staging/epl/VirtualEthernetLinux.c
drivers/staging/epl/amix86.c
drivers/staging/epl/demo_main.c
drivers/staging/epl/edrv.h
drivers/staging/epl/global.h
drivers/staging/epl/kernel/EplDllk.h
drivers/staging/epl/kernel/EplDllkCal.h
drivers/staging/epl/kernel/EplErrorHandlerk.h
drivers/staging/epl/kernel/EplEventk.h
drivers/staging/epl/kernel/EplNmtk.h
drivers/staging/epl/kernel/EplNmtkCal.h [deleted file]
drivers/staging/epl/kernel/EplObdk.h
drivers/staging/epl/kernel/EplObdkCal.h [deleted file]
drivers/staging/epl/kernel/EplPdok.h
drivers/staging/epl/kernel/EplPdokCal.h
drivers/staging/epl/kernel/EplTimerHighResk.h
drivers/staging/epl/kernel/EplTimerk.h
drivers/staging/epl/kernel/VirtualEthernet.h
drivers/staging/epl/proc_fs.c
drivers/staging/epl/user/EplCfgMau.h
drivers/staging/epl/user/EplDllu.h
drivers/staging/epl/user/EplDlluCal.h
drivers/staging/epl/user/EplEventu.h
drivers/staging/epl/user/EplIdentu.h
drivers/staging/epl/user/EplLedu.h
drivers/staging/epl/user/EplNmtCnu.h
drivers/staging/epl/user/EplNmtMnu.h
drivers/staging/epl/user/EplNmtu.h
drivers/staging/epl/user/EplNmtuCal.h
drivers/staging/epl/user/EplObdu.h
drivers/staging/epl/user/EplObduCal.h
drivers/staging/epl/user/EplPdou.h
drivers/staging/epl/user/EplSdoAsndu.h
drivers/staging/epl/user/EplSdoAsySequ.h
drivers/staging/epl/user/EplSdoComu.h
drivers/staging/epl/user/EplSdoUdpu.h
drivers/staging/epl/user/EplStatusu.h
drivers/staging/epl/user/EplTimeru.h
drivers/staging/et131x/et1310_rx.c
drivers/staging/frontier/README
drivers/staging/frontier/alphatrack.c
drivers/staging/frontier/alphatrack.h
drivers/staging/frontier/frontier_compat.h [deleted file]
drivers/staging/frontier/surface_sysfs.h [deleted file]
drivers/staging/frontier/tranzport.c
drivers/staging/go7007/go7007-v4l2.c
drivers/staging/go7007/s2250-board.c
drivers/staging/heci/Kconfig [new file with mode: 0644]
drivers/staging/heci/Makefile [new file with mode: 0644]
drivers/staging/heci/TODO [new file with mode: 0644]
drivers/staging/heci/heci.h [new file with mode: 0644]
drivers/staging/heci/heci_data_structures.h [new file with mode: 0644]
drivers/staging/heci/heci_init.c [new file with mode: 0644]
drivers/staging/heci/heci_interface.c [new file with mode: 0644]
drivers/staging/heci/heci_interface.h [new file with mode: 0644]
drivers/staging/heci/heci_main.c [new file with mode: 0644]
drivers/staging/heci/heci_version.h [new file with mode: 0644]
drivers/staging/heci/interrupt.c [new file with mode: 0644]
drivers/staging/heci/io_heci.c [new file with mode: 0644]
drivers/staging/line6/Kconfig [new file with mode: 0644]
drivers/staging/line6/Makefile [new file with mode: 0644]
drivers/staging/line6/audio.c [new file with mode: 0644]
drivers/staging/line6/audio.h [new file with mode: 0644]
drivers/staging/line6/capture.c [new file with mode: 0644]
drivers/staging/line6/capture.h [new file with mode: 0644]
drivers/staging/line6/config.h [new file with mode: 0644]
drivers/staging/line6/control.c [new file with mode: 0644]
drivers/staging/line6/control.h [new file with mode: 0644]
drivers/staging/line6/driver.c [new file with mode: 0644]
drivers/staging/line6/driver.h [new file with mode: 0644]
drivers/staging/line6/dumprequest.c [new file with mode: 0644]
drivers/staging/line6/dumprequest.h [new file with mode: 0644]
drivers/staging/line6/midi.c [new file with mode: 0644]
drivers/staging/line6/midi.h [new file with mode: 0644]
drivers/staging/line6/midibuf.c [new file with mode: 0644]
drivers/staging/line6/midibuf.h [new file with mode: 0644]
drivers/staging/line6/pcm.c [new file with mode: 0644]
drivers/staging/line6/pcm.h [new file with mode: 0644]
drivers/staging/line6/playback.c [new file with mode: 0644]
drivers/staging/line6/playback.h [new file with mode: 0644]
drivers/staging/line6/pod.c [new file with mode: 0644]
drivers/staging/line6/pod.h [new file with mode: 0644]
drivers/staging/line6/revision.h [new file with mode: 0644]
drivers/staging/line6/toneport.c [new file with mode: 0644]
drivers/staging/line6/toneport.h [new file with mode: 0644]
drivers/staging/line6/usbdefs.h [new file with mode: 0644]
drivers/staging/line6/variax.c [new file with mode: 0644]
drivers/staging/line6/variax.h [new file with mode: 0644]
drivers/staging/me4000/me4000.c
drivers/staging/meilhaus/me0600_device.c
drivers/staging/meilhaus/me0600_dio.c
drivers/staging/meilhaus/me0600_ext_irq.c
drivers/staging/meilhaus/me0600_optoi.c
drivers/staging/meilhaus/me0600_relay.c
drivers/staging/meilhaus/me0600_ttli.c
drivers/staging/meilhaus/me0900_device.c
drivers/staging/meilhaus/me0900_di.c
drivers/staging/meilhaus/me0900_do.c
drivers/staging/meilhaus/me1000_device.c
drivers/staging/meilhaus/me1000_dio.c
drivers/staging/meilhaus/me1400_device.c
drivers/staging/meilhaus/me1400_ext_irq.c
drivers/staging/meilhaus/me1600_ao.c
drivers/staging/meilhaus/me1600_ao.h
drivers/staging/meilhaus/me1600_device.c
drivers/staging/meilhaus/me4600_ai.c
drivers/staging/meilhaus/me4600_ai.h
drivers/staging/meilhaus/me4600_ao.c
drivers/staging/meilhaus/me4600_ao.h
drivers/staging/meilhaus/me4600_device.c
drivers/staging/meilhaus/me4600_di.c
drivers/staging/meilhaus/me4600_dio.c
drivers/staging/meilhaus/me4600_do.c
drivers/staging/meilhaus/me4600_ext_irq.c
drivers/staging/meilhaus/me6000_ao.c
drivers/staging/meilhaus/me6000_ao.h
drivers/staging/meilhaus/me6000_device.c
drivers/staging/meilhaus/me6000_dio.c
drivers/staging/meilhaus/me8100_device.c
drivers/staging/meilhaus/me8100_di.c
drivers/staging/meilhaus/me8100_do.c
drivers/staging/meilhaus/me8200_device.c
drivers/staging/meilhaus/me8200_di.c
drivers/staging/meilhaus/me8200_dio.c
drivers/staging/meilhaus/me8200_do.c
drivers/staging/meilhaus/me8254.c
drivers/staging/meilhaus/me8255.c
drivers/staging/meilhaus/mecirc_buf.h
drivers/staging/meilhaus/medevice.c
drivers/staging/meilhaus/medlist.c
drivers/staging/meilhaus/medlock.c
drivers/staging/meilhaus/medummy.c
drivers/staging/meilhaus/memain.c
drivers/staging/meilhaus/meslist.c
drivers/staging/meilhaus/meslock.c
drivers/staging/meilhaus/mesubdevice.c
drivers/staging/meilhaus/metempl_device.c
drivers/staging/meilhaus/metempl_sub.c
drivers/staging/mimio/Kconfig
drivers/staging/otus/80211core/amsdu.c
drivers/staging/otus/80211core/cmmsta.c
drivers/staging/otus/80211core/coid.c
drivers/staging/otus/80211core/cwm.c
drivers/staging/otus/TODO
drivers/staging/otus/hal/hpani.c
drivers/staging/otus/hal/hpmain.c
drivers/staging/otus/hal/hpreg.c
drivers/staging/otus/hal/hprw.c
drivers/staging/otus/hal/hpusb.c
drivers/staging/otus/ioctl.c
drivers/staging/otus/usbdrv.c
drivers/staging/otus/wwrap.c
drivers/staging/otus/zdcompat.h
drivers/staging/p9auth/Kconfig [new file with mode: 0644]
drivers/staging/p9auth/Makefile [new file with mode: 0644]
drivers/staging/p9auth/p9auth.c [new file with mode: 0644]
drivers/staging/phison/Kconfig [new file with mode: 0644]
drivers/staging/phison/Makefile [new file with mode: 0644]
drivers/staging/phison/phison.c [new file with mode: 0644]
drivers/staging/pohmelfs/Kconfig [new file with mode: 0644]
drivers/staging/pohmelfs/Makefile [new file with mode: 0644]
drivers/staging/pohmelfs/config.c [new file with mode: 0644]
drivers/staging/pohmelfs/crypto.c [new file with mode: 0644]
drivers/staging/pohmelfs/dir.c [new file with mode: 0644]
drivers/staging/pohmelfs/inode.c [new file with mode: 0644]
drivers/staging/pohmelfs/lock.c [new file with mode: 0644]
drivers/staging/pohmelfs/mcache.c [new file with mode: 0644]
drivers/staging/pohmelfs/net.c [new file with mode: 0644]
drivers/staging/pohmelfs/netfs.h [new file with mode: 0644]
drivers/staging/pohmelfs/path_entry.c [new file with mode: 0644]
drivers/staging/pohmelfs/trans.c [new file with mode: 0644]
drivers/staging/rspiusb/rspiusb.c
drivers/staging/rt2860/2860_main_dev.c
drivers/staging/rt2860/Makefile
drivers/staging/rt2860/TODO
drivers/staging/rt2860/common/cmm_data.c
drivers/staging/rt2860/common/cmm_data_2860.c
drivers/staging/rt2860/common/cmm_info.c
drivers/staging/rt2860/common/cmm_sync.c
drivers/staging/rt2860/common/cmm_wpa.c
drivers/staging/rt2860/common/mlme.c
drivers/staging/rt2860/common/rtmp_init.c
drivers/staging/rt2860/common/spectrum.c
drivers/staging/rt2860/config.mk
drivers/staging/rt2860/oid.h
drivers/staging/rt2860/rt2860.h
drivers/staging/rt2860/rt28xx.h
drivers/staging/rt2860/rt_ate.c
drivers/staging/rt2860/rt_ate.h
drivers/staging/rt2860/rt_config.h
drivers/staging/rt2860/rt_linux.c
drivers/staging/rt2860/rt_linux.h
drivers/staging/rt2860/rt_main_dev.c
drivers/staging/rt2860/rt_profile.c
drivers/staging/rt2860/rtmp.h
drivers/staging/rt2860/rtmp_def.h
drivers/staging/rt2860/sta/assoc.c
drivers/staging/rt2860/sta/connect.c
drivers/staging/rt2860/sta/dls.c
drivers/staging/rt2860/sta/rtmp_data.c
drivers/staging/rt2860/sta/sync.c
drivers/staging/rt2860/sta/wpa.c
drivers/staging/rt2860/sta_ioctl.c
drivers/staging/rt2860/wpa.h
drivers/staging/rt2870/2870_main_dev.c
drivers/staging/rt2870/TODO
drivers/staging/rt2870/common/2870_rtmp_init.c
drivers/staging/rt2870/common/cmm_data.c
drivers/staging/rt2870/common/rtmp_init.c
drivers/staging/rt2870/common/rtusb_io.c
drivers/staging/rt2870/common/spectrum.c
drivers/staging/rt2870/rt2870.h
drivers/staging/rt2870/rt_linux.c
drivers/staging/rt2870/rt_linux.h
drivers/staging/rt2870/sta_ioctl.c
drivers/staging/rt3070/2870_main_dev.c [new file with mode: 0644]
drivers/staging/rt3070/Kconfig [new file with mode: 0644]
drivers/staging/rt3070/Makefile [new file with mode: 0644]
drivers/staging/rt3070/action.h [new file with mode: 0644]
drivers/staging/rt3070/aironet.h [new file with mode: 0644]
drivers/staging/rt3070/ap.h [new file with mode: 0644]
drivers/staging/rt3070/chlist.h [new file with mode: 0644]
drivers/staging/rt3070/common/2870_rtmp_init.c [new file with mode: 0644]
drivers/staging/rt3070/common/action.c [new file with mode: 0644]
drivers/staging/rt3070/common/ba_action.c [new file with mode: 0644]
drivers/staging/rt3070/common/cmm_data.c [new file with mode: 0644]
drivers/staging/rt3070/common/cmm_data_2870.c [new file with mode: 0644]
drivers/staging/rt3070/common/cmm_info.c [new file with mode: 0644]
drivers/staging/rt3070/common/cmm_sanity.c [new file with mode: 0644]
drivers/staging/rt3070/common/cmm_sync.c [new file with mode: 0644]
drivers/staging/rt3070/common/cmm_wpa.c [new file with mode: 0644]
drivers/staging/rt3070/common/dfs.c [new file with mode: 0644]
drivers/staging/rt3070/common/eeprom.c [new file with mode: 0644]
drivers/staging/rt3070/common/md5.c [new file with mode: 0644]
drivers/staging/rt3070/common/mlme.c [new file with mode: 0644]
drivers/staging/rt3070/common/netif_block.c [new file with mode: 0644]
drivers/staging/rt3070/common/rtmp_init.c [new file with mode: 0644]
drivers/staging/rt3070/common/rtmp_tkip.c [new file with mode: 0644]
drivers/staging/rt3070/common/rtmp_wep.c [new file with mode: 0644]
drivers/staging/rt3070/common/rtusb_bulk.c [new file with mode: 0644]
drivers/staging/rt3070/common/rtusb_data.c [new file with mode: 0644]
drivers/staging/rt3070/common/rtusb_io.c [new file with mode: 0644]
drivers/staging/rt3070/common/spectrum.c [new file with mode: 0644]
drivers/staging/rt3070/dfs.h [new file with mode: 0644]
drivers/staging/rt3070/firmware.h [new file with mode: 0644]
drivers/staging/rt3070/leap.h [new file with mode: 0644]
drivers/staging/rt3070/link_list.h [new file with mode: 0644]
drivers/staging/rt3070/md4.h [new file with mode: 0644]
drivers/staging/rt3070/md5.h [new file with mode: 0644]
drivers/staging/rt3070/mlme.h [new file with mode: 0644]
drivers/staging/rt3070/netif_block.h [new file with mode: 0644]
drivers/staging/rt3070/oid.h [new file with mode: 0644]
drivers/staging/rt3070/rt2870.h [new file with mode: 0644]
drivers/staging/rt3070/rt28xx.h [new file with mode: 0644]
drivers/staging/rt3070/rt_ate.c [new file with mode: 0644]
drivers/staging/rt3070/rt_ate.h [new file with mode: 0644]
drivers/staging/rt3070/rt_config.h [new file with mode: 0644]
drivers/staging/rt3070/rt_linux.c [new file with mode: 0644]
drivers/staging/rt3070/rt_linux.h [new file with mode: 0644]
drivers/staging/rt3070/rt_main_dev.c [new file with mode: 0644]
drivers/staging/rt3070/rt_profile.c [new file with mode: 0644]
drivers/staging/rt3070/rtmp.h [new file with mode: 0644]
drivers/staging/rt3070/rtmp_ckipmic.h [new file with mode: 0644]
drivers/staging/rt3070/rtmp_def.h [new file with mode: 0644]
drivers/staging/rt3070/rtmp_type.h [new file with mode: 0644]
drivers/staging/rt3070/spectrum.h [new file with mode: 0644]
drivers/staging/rt3070/spectrum_def.h [new file with mode: 0644]
drivers/staging/rt3070/sta/aironet.c [new file with mode: 0644]
drivers/staging/rt3070/sta/assoc.c [new file with mode: 0644]
drivers/staging/rt3070/sta/auth.c [new file with mode: 0644]
drivers/staging/rt3070/sta/auth_rsp.c [new file with mode: 0644]
drivers/staging/rt3070/sta/connect.c [new file with mode: 0644]
drivers/staging/rt3070/sta/dls.c [new file with mode: 0644]
drivers/staging/rt3070/sta/rtmp_data.c [new file with mode: 0644]
drivers/staging/rt3070/sta/sanity.c [new file with mode: 0644]
drivers/staging/rt3070/sta/sync.c [new file with mode: 0644]
drivers/staging/rt3070/sta/wpa.c [new file with mode: 0644]
drivers/staging/rt3070/sta_ioctl.c [new file with mode: 0644]
drivers/staging/rt3070/wpa.h [new file with mode: 0644]
drivers/staging/rtl8187se/dot11d.h
drivers/staging/rtl8187se/ieee80211/dot11d.c
drivers/staging/rtl8187se/ieee80211/dot11d.h
drivers/staging/rtl8187se/ieee80211/ieee80211_wx.c
drivers/staging/rtl8187se/r8180_core.c
drivers/staging/rtl8187se/r8180_dm.c
drivers/staging/rtl8187se/r8180_dm.h
drivers/staging/rtl8187se/r8180_wx.c
drivers/staging/serqt_usb/Kconfig [new file with mode: 0644]
drivers/staging/serqt_usb/Makefile [new file with mode: 0644]
drivers/staging/serqt_usb/TODO [new file with mode: 0644]
drivers/staging/serqt_usb/serqt_usb.c [new file with mode: 0644]
drivers/staging/slicoss/gbdownload.h [deleted file]
drivers/staging/slicoss/gbrcvucode.h [deleted file]
drivers/staging/slicoss/oasisdbgdownload.h [deleted file]
drivers/staging/slicoss/oasisdownload.h [deleted file]
drivers/staging/slicoss/oasisrcvucode.h [deleted file]
drivers/staging/slicoss/slic.h
drivers/staging/slicoss/slic_os.h [deleted file]
drivers/staging/slicoss/slicbuild.h [deleted file]
drivers/staging/slicoss/slicdbg.h [deleted file]
drivers/staging/slicoss/slicdump.h [deleted file]
drivers/staging/slicoss/slichw.h
drivers/staging/slicoss/slicinc.h [deleted file]
drivers/staging/slicoss/slicoss.c
drivers/staging/stlc45xx/Kconfig [new file with mode: 0644]
drivers/staging/stlc45xx/Makefile [new file with mode: 0644]
drivers/staging/stlc45xx/stlc45xx.c [new file with mode: 0644]
drivers/staging/stlc45xx/stlc45xx.h [new file with mode: 0644]
drivers/staging/stlc45xx/stlc45xx_lmac.h [new file with mode: 0644]
drivers/staging/sxg/Kconfig
drivers/staging/sxg/Makefile
drivers/staging/sxg/saharadbgdownload.h [deleted file]
drivers/staging/sxg/sxg.c
drivers/staging/sxg/sxg.h
drivers/staging/sxg/sxg_ethtool.c [new file with mode: 0644]
drivers/staging/sxg/sxg_os.h
drivers/staging/sxg/sxgdbg.h
drivers/staging/sxg/sxghif.h
drivers/staging/sxg/sxghw.h
drivers/staging/sxg/sxgphycode-1.2.h [new file with mode: 0644]
drivers/staging/sxg/sxgphycode.h [deleted file]
drivers/staging/uc2322/Kconfig [new file with mode: 0644]
drivers/staging/uc2322/Makefile [new file with mode: 0644]
drivers/staging/uc2322/TODO [new file with mode: 0644]
drivers/staging/uc2322/aten2011.c [new file with mode: 0644]
drivers/staging/usbip/stub_rx.c
drivers/staging/usbip/vhci_sysfs.c
drivers/staging/winbond/bss_f.h [deleted file]
drivers/staging/winbond/bssdscpt.h [deleted file]
drivers/staging/winbond/common.h [deleted file]
drivers/staging/winbond/core.h
drivers/staging/winbond/ds_tkip.h [deleted file]
drivers/staging/winbond/gl_80211.h [deleted file]
drivers/staging/winbond/ioctls.h [deleted file]
drivers/staging/winbond/mds.c
drivers/staging/winbond/mds_s.h
drivers/staging/winbond/mlme_mib.h [deleted file]
drivers/staging/winbond/mlmetxrx.c
drivers/staging/winbond/mto.c
drivers/staging/winbond/mto.h
drivers/staging/winbond/mto_f.h [deleted file]
drivers/staging/winbond/os_common.h [deleted file]
drivers/staging/winbond/phy_calibration.c
drivers/staging/winbond/phy_calibration.h
drivers/staging/winbond/reg.c
drivers/staging/winbond/sme_api.h
drivers/staging/winbond/sme_s.h [deleted file]
drivers/staging/winbond/wb35_ver.h [deleted file]
drivers/staging/winbond/wb35reg.c
drivers/staging/winbond/wb35reg_f.h
drivers/staging/winbond/wb35rx.c
drivers/staging/winbond/wb35rx_f.h
drivers/staging/winbond/wb35rx_s.h
drivers/staging/winbond/wb35tx.c
drivers/staging/winbond/wb35tx_f.h
drivers/staging/winbond/wb35tx_s.h
drivers/staging/winbond/wbhal.c
drivers/staging/winbond/wbhal_f.h
drivers/staging/winbond/wbhal_s.h
drivers/staging/winbond/wbusb.c
drivers/staging/winbond/wbusb_s.h
drivers/staging/wlan-ng/README
drivers/staging/wlan-ng/hfa384x.h
drivers/staging/wlan-ng/hfa384x_usb.c
drivers/staging/wlan-ng/p80211conv.c
drivers/staging/wlan-ng/p80211conv.h
drivers/staging/wlan-ng/p80211hdr.h
drivers/staging/wlan-ng/p80211ioctl.h
drivers/staging/wlan-ng/p80211meta.h
drivers/staging/wlan-ng/p80211metadef.h
drivers/staging/wlan-ng/p80211metamib.h [deleted file]
drivers/staging/wlan-ng/p80211metamsg.h [deleted file]
drivers/staging/wlan-ng/p80211metastruct.h
drivers/staging/wlan-ng/p80211mgmt.h
drivers/staging/wlan-ng/p80211msg.h
drivers/staging/wlan-ng/p80211netdev.c
drivers/staging/wlan-ng/p80211netdev.h
drivers/staging/wlan-ng/p80211req.c
drivers/staging/wlan-ng/p80211req.h
drivers/staging/wlan-ng/p80211types.h
drivers/staging/wlan-ng/p80211wep.c
drivers/staging/wlan-ng/p80211wext.c
drivers/staging/wlan-ng/prism2mgmt.c
drivers/staging/wlan-ng/prism2mgmt.h
drivers/staging/wlan-ng/prism2mib.c
drivers/staging/wlan-ng/prism2sta.c
drivers/staging/wlan-ng/prism2usb.c
drivers/staging/wlan-ng/wlan_compat.h [deleted file]
drivers/usb/gadget/atmel_usba_udc.c
drivers/xen/cpu_hotplug.c
firmware/Makefile
firmware/WHENCE
firmware/slicoss/gbdownload.sys.ihex [new file with mode: 0644]
firmware/slicoss/gbrcvucode.sys.ihex [new file with mode: 0644]
firmware/slicoss/oasisdbgdownload.sys.ihex [new file with mode: 0644]
firmware/slicoss/oasisdownload.sys.ihex [new file with mode: 0644]
firmware/slicoss/oasisrcvucode.sys.ihex [new file with mode: 0644]
firmware/sxg/saharadbgdownloadB.sys.ihex [new file with mode: 0644]
firmware/sxg/saharadownloadB.sys.ihex [new file with mode: 0644]
fs/compat.c
fs/debugfs/inode.c
fs/partitions/check.c
fs/read_write.c
include/asm-frv/ftrace.h [new file with mode: 0644]
include/asm-generic/vmlinux.lds.h
include/asm-m32r/ftrace.h [new file with mode: 0644]
include/asm-mn10300/ftrace.h [new file with mode: 0644]
include/linux/blktrace_api.h
include/linux/compat.h
include/linux/compiler.h
include/linux/connector.h
include/linux/debugfs.h
include/linux/dst.h [new file with mode: 0644]
include/linux/ftrace.h
include/linux/ftrace_irq.h
include/linux/gfp.h
include/linux/hardirq.h
include/linux/interrupt.h
include/linux/kallsyms.h
include/linux/kernel.h
include/linux/kmod.h
include/linux/memory.h
include/linux/mmzone.h
include/linux/module.h
include/linux/moduleparam.h
include/linux/ring_buffer.h
include/linux/sched.h
include/linux/slab_def.h
include/linux/slob_def.h
include/linux/slub_def.h
include/linux/string.h
include/linux/syscalls.h
include/linux/topology.h
include/linux/trace_clock.h [new file with mode: 0644]
include/linux/tracepoint.h
include/trace/block.h
include/trace/irq.h [new file with mode: 0644]
include/trace/irq_event_types.h [new file with mode: 0644]
include/trace/kmemtrace.h [new file with mode: 0644]
include/trace/lockdep.h [new file with mode: 0644]
include/trace/lockdep_event_types.h [new file with mode: 0644]
include/trace/power.h [new file with mode: 0644]
include/trace/sched.h
include/trace/sched_event_types.h [new file with mode: 0644]
include/trace/skb.h
include/trace/trace_event_types.h [new file with mode: 0644]
include/trace/trace_events.h [new file with mode: 0644]
include/trace/workqueue.h [new file with mode: 0644]
init/Kconfig
init/main.c
kernel/extable.c
kernel/irq/handle.c
kernel/kallsyms.c
kernel/kmod.c
kernel/kprobes.c
kernel/lockdep.c
kernel/module.c
kernel/params.c
kernel/printk.c
kernel/relay.c
kernel/sched.c
kernel/sched_clock.c
kernel/softirq.c
kernel/trace/Kconfig
kernel/trace/Makefile
kernel/trace/blktrace.c [moved from block/blktrace.c with 52% similarity]
kernel/trace/events.c [new file with mode: 0644]
kernel/trace/ftrace.c
kernel/trace/kmemtrace.c [new file with mode: 0644]
kernel/trace/ring_buffer.c
kernel/trace/trace.c
kernel/trace/trace.h
kernel/trace/trace_boot.c
kernel/trace/trace_branch.c
kernel/trace/trace_clock.c [new file with mode: 0644]
kernel/trace/trace_event_profile.c [new file with mode: 0644]
kernel/trace/trace_event_types.h [new file with mode: 0644]
kernel/trace/trace_events.c [new file with mode: 0644]
kernel/trace/trace_events_filter.c [new file with mode: 0644]
kernel/trace/trace_events_stage_1.h [new file with mode: 0644]
kernel/trace/trace_events_stage_2.h [new file with mode: 0644]
kernel/trace/trace_events_stage_3.h [new file with mode: 0644]
kernel/trace/trace_export.c [new file with mode: 0644]
kernel/trace/trace_functions.c
kernel/trace/trace_functions_graph.c
kernel/trace/trace_hw_branches.c
kernel/trace/trace_irqsoff.c
kernel/trace/trace_mmiotrace.c
kernel/trace/trace_nop.c
kernel/trace/trace_output.c [new file with mode: 0644]
kernel/trace/trace_output.h [new file with mode: 0644]
kernel/trace/trace_power.c
kernel/trace/trace_printk.c [new file with mode: 0644]
kernel/trace/trace_sched_switch.c
kernel/trace/trace_sched_wakeup.c
kernel/trace/trace_selftest.c
kernel/trace/trace_stack.c
kernel/trace/trace_stat.c [new file with mode: 0644]
kernel/trace/trace_stat.h [new file with mode: 0644]
kernel/trace/trace_syscalls.c [new file with mode: 0644]
kernel/trace/trace_sysprof.c
kernel/trace/trace_workqueue.c [new file with mode: 0644]
kernel/tracepoint.c
kernel/workqueue.c
lib/Kconfig
lib/debugobjects.c
lib/vsprintf.c
mm/filemap.c
mm/page_alloc.c
mm/quicklist.c
mm/slab.c
mm/slob.c
mm/slub.c
mm/vmscan.c
net/sunrpc/svc.c
samples/tracepoints/tp-samples-trace.h
samples/tracepoints/tracepoint-sample.c
scripts/Makefile.build
scripts/kallsyms.c
scripts/mod/modpost.c
scripts/recordmcount.pl
usr/Kconfig
usr/Makefile

diff --git a/Documentation/ABI/testing/debugfs-kmemtrace b/Documentation/ABI/testing/debugfs-kmemtrace
new file mode 100644 (file)
index 0000000..5e6a92a
--- /dev/null
@@ -0,0 +1,71 @@
+What:          /sys/kernel/debug/kmemtrace/
+Date:          July 2008
+Contact:       Eduard - Gabriel Munteanu <eduard.munteanu@linux360.ro>
+Description:
+
+In kmemtrace-enabled kernels, the following files are created:
+
+/sys/kernel/debug/kmemtrace/
+       cpu<n>          (0400)  Per-CPU tracing data, see below. (binary)
+       total_overruns  (0400)  Total number of bytes which were dropped from
+                               cpu<n> files because of full buffer condition,
+                               non-binary. (text)
+       abi_version     (0400)  Kernel's kmemtrace ABI version. (text)
+
+Each per-CPU file should be read according to the relay interface. That is,
+the reader should set affinity to that specific CPU and, as currently done by
+the userspace application (though there are other methods), use poll() with
+an infinite timeout before every read(). Otherwise, erroneous data may be
+read. The binary data has the following _core_ format:
+
+       Event ID        (1 byte)        Unsigned integer, one of:
+               0 - represents an allocation (KMEMTRACE_EVENT_ALLOC)
+               1 - represents a freeing of previously allocated memory
+                   (KMEMTRACE_EVENT_FREE)
+       Type ID         (1 byte)        Unsigned integer, one of:
+               0 - this is a kmalloc() / kfree()
+               1 - this is a kmem_cache_alloc() / kmem_cache_free()
+               2 - this is a __get_free_pages() et al.
+       Event size      (2 bytes)       Unsigned integer representing the
+                                       size of this event. Used to extend
+                                       kmemtrace. Discard the bytes you
+                                       don't know about.
+       Sequence number (4 bytes)       Signed integer used to reorder data
+                                       logged on SMP machines. Wraparound
+                                       must be taken into account, although
+                                       it is unlikely.
+       Caller address  (8 bytes)       Return address to the caller.
+       Pointer to mem  (8 bytes)       Pointer to target memory area. Can be
+                                       NULL, but not all such calls might be
+                                       recorded.
+
+In case of KMEMTRACE_EVENT_ALLOC events, the next fields follow:
+
+       Requested bytes (8 bytes)       Total number of requested bytes,
+                                       unsigned, must not be zero.
+       Allocated bytes (8 bytes)       Total number of actually allocated
+                                       bytes, unsigned, must not be lower
+                                       than requested bytes.
+       Requested flags (4 bytes)       GFP flags supplied by the caller.
+       Target CPU      (4 bytes)       Signed integer, valid for event id 1.
+                                       If equal to -1, target CPU is the same
+                                       as origin CPU, but the reverse might
+                                       not be true.
+
+The data is made available in the same endianness the machine has.
+
+Other event ids and type ids may be defined and added. Other fields may be
+added by increasing event size, but see below for details.
+Every modification to the ABI, including new id definitions, are followed
+by bumping the ABI version by one.
+
+Adding new data to the packet (features) is done at the end of the mandatory
+data:
+       Feature size    (2 byte)
+       Feature ID      (1 byte)
+       Feature data    (Feature size - 3 bytes)
+
+
+Users:
+       kmemtrace-user - git://repo.or.cz/kmemtrace-user.git
+
diff --git a/Documentation/filesystems/pohmelfs/design_notes.txt b/Documentation/filesystems/pohmelfs/design_notes.txt
new file mode 100644 (file)
index 0000000..6d6db60
--- /dev/null
@@ -0,0 +1,70 @@
+POHMELFS: Parallel Optimized Host Message Exchange Layered File System.
+
+               Evgeniy Polyakov <zbr@ioremap.net>
+
+Homepage: http://www.ioremap.net/projects/pohmelfs
+
+POHMELFS first began as a network filesystem with coherent local data and
+metadata caches but is now evolving into a parallel distributed filesystem.
+
+Main features of this FS include:
+ * Locally coherent cache for data and metadata with (potentially) byte-range locks.
+       Since all Linux filesystems lock the whole inode during writing, algorithm
+       is very simple and does not use byte-ranges, although they are sent in
+       locking messages.
+ * Completely async processing of all events except creation of hard and symbolic
+       links, and rename events.
+       Object creation and data reading and writing are processed asynchronously.
+ * Flexible object architecture optimized for network processing.
+       Ability to create long paths to objects and remove arbitrarily huge
+       directories with a single network command.
+       (like removing the whole kernel tree via a single network command).
+ * Very high performance.
+ * Fast and scalable multithreaded userspace server. Being in userspace it works
+       with any underlying filesystem and still is much faster than async in-kernel NFS one.
+ * Client is able to switch between different servers (if one goes down, client
+       automatically reconnects to second and so on).
+ * Transactions support. Full failover for all operations.
+       Resending transactions to different servers on timeout or error.
+ * Read request (data read, directory listing, lookup requests) balancing between multiple servers.
+ * Write requests are replicated to multiple servers and completed only when all of them are acked.
+ * Ability to add and/or remove servers from the working set at run-time.
+ * Strong authentification and possible data encryption in network channel.
+ * Extended attributes support.
+
+POHMELFS is based on transactions, which are potentially long-standing objects that live
+in the client's memory. Each transaction contains all the information needed to process a given
+command (or set of commands, which is frequently used during data writing: single transactions
+can contain creation and data writing commands). Transactions are committed by all the servers
+to which they are sent and, in case of failures, are eventually resent or dropped with an error.
+For example, reading will return an error if no servers are available.
+
+POHMELFS uses a asynchronous approach to data processing. Courtesy of transactions, it is
+possible to detach replies from requests and, if the command requires data to be received, the
+caller sleeps waiting for it. Thus, it is possible to issue multiple read commands to different
+servers and async threads will pick up replies in parallel, find appropriate transactions in the
+system and put the data where it belongs (like the page or inode cache).
+
+The main feature of POHMELFS is writeback data and the metadata cache.
+Only a few non-performance critical operations use the write-through cache and
+are synchronous: hard and symbolic link creation, and object rename. Creation,
+removal of objects and data writing are asynchronous and are sent to
+the server during system writeback. Only one writer at a time is allowed for any
+given inode, which is guarded by an appropriate locking protocol.
+Because of this feature, POHMELFS is extremely fast at metadata intensive
+workloads and can fully utilize the bandwidth to the servers when doing bulk
+data transfers.
+
+POHMELFS clients operate with a working set of servers and are capable of balancing read-only
+operations (like lookups or directory listings) between them.
+Administrators can add or remove servers from the set at run-time via special commands (described
+in Documentation/pohmelfs/info.txt file). Writes are replicated to all servers.
+
+POHMELFS is capable of full data channel encryption and/or strong crypto hashing.
+One can select any kernel supported cipher, encryption mode, hash type and operation mode
+(hmac or digest). It is also possible to use both or neither (default). Crypto configuration
+is checked during mount time and, if the server does not support it, appropriate capabilities
+will be disabled or mount will fail (if 'crypto_fail_unsupported' mount option is specified).
+Crypto performance heavily depends on the number of crypto threads, which asynchronously perform
+crypto operations and send the resulting data to server or submit it up the stack. This number
+can be controlled via a mount option.
diff --git a/Documentation/filesystems/pohmelfs/info.txt b/Documentation/filesystems/pohmelfs/info.txt
new file mode 100644 (file)
index 0000000..4e3d501
--- /dev/null
@@ -0,0 +1,86 @@
+POHMELFS usage information.
+
+Mount options:
+idx=%u
+ Each mountpoint is associated with a special index via this option.
+ Administrator can add or remove servers from the given index, so all mounts,
+ which were attached to it, are updated.
+ Default it is 0.
+
+trans_scan_timeout=%u
+ This timeout, expressed in milliseconds, specifies time to scan transaction
+ trees looking for stale requests, which have to be resent, or if number of
+ retries exceed specified limit, dropped with error.
+ Default is 5 seconds.
+
+drop_scan_timeout=%u
+ Internal timeout, expressed in milliseconds, which specifies how frequently
+ inodes marked to be dropped are freed. It also specifies how frequently
+ the system checks that servers have to be added or removed from current working set.
+ Default is 1 second.
+
+wait_on_page_timeout=%u
+ Number of milliseconds to wait for reply from remote server for data reading command.
+ If this timeout is exceeded, reading returns an error.
+ Default is 5 seconds.
+
+trans_retries=%u
+ This is the number of times that a transaction will be resent to a server that did
+ not answer for the last @trans_scan_timeout milliseconds.
+ When the number of resends exceeds this limit, the transaction is completed with error.
+ Default is 5 resends.
+
+crypto_thread_num=%u
+ Number of crypto processing threads. Threads are used both for RX and TX traffic.
+ Default is 2, or no threads if crypto operations are not supported.
+
+trans_max_pages=%u
+ Maximum number of pages in a single transaction. This parameter also controls
+ the number of pages,  allocated for crypto processing (each crypto thread has
+ pool of pages, the number of which is equal to 'trans_max_pages'.
+ Default is 100 pages.
+
+crypto_fail_unsupported
+ If specified, mount will fail if the server does not support requested crypto operations.
+ By default mount will disable non-matching crypto operations.
+
+mcache_timeout=%u
+ Maximum number of milliseconds to wait for the mcache objects to be processed.
+ Mcache includes locks (given lock should be granted by server), attributes (they should be
+ fully received in the given timeframe).
+ Default is 5 seconds.
+
+Usage examples.
+
+Add (or remove if it already exists) server server1.net:1025 into the working set with index $idx
+with appropriate hash algorithm and key file and cipher algorithm, mode and key file:
+$cfg -a server1.net -p 1025 -i $idx -K $hash_key -k $cipher_key
+
+Mount filesystem with given index $idx to /mnt mountpoint.
+Client will connect to all servers specified in the working set via previous command:
+mount -t pohmel -o idx=$idx q /mnt
+
+One can add or remove servers from working set after mounting too.
+
+
+Server installation.
+
+Creating a server, which listens at port 1025 and 0.0.0.0 address.
+Working root directory (note, that server chroots there, so you have to have appropriate permissions)
+is set to /mnt, server will negotiate hash/cipher with client, in case client requested it, there
+are appropriate key files.
+Number of working threads is set to 10.
+
+# ./fserver -a 0.0.0.0 -p 1025 -r /mnt -w 10 -K hash_key -k cipher_key
+
+ -A 6                   - listen on ipv6 address. Default: Disabled.
+ -r root                 - path to root directory. Default: /tmp.
+ -a addr                 - listen address. Default: 0.0.0.0.
+ -p port                 - listen port. Default: 1025.
+ -w workers              - number of workers per connected client. Default: 1.
+ -K file                - hash key size. Default: none.
+ -k file                - cipher key size. Default: none.
+ -h                      - this help.
+
+Number of worker threads specifies how many workers will be created for each client.
+Bulk single-client transafers usually are better handled with smaller number (like 1-3).
diff --git a/Documentation/filesystems/pohmelfs/network_protocol.txt b/Documentation/filesystems/pohmelfs/network_protocol.txt
new file mode 100644 (file)
index 0000000..40ea6c2
--- /dev/null
@@ -0,0 +1,227 @@
+POHMELFS network protocol.
+
+Basic structure used in network communication is following command:
+
+struct netfs_cmd
+{
+       __u16                   cmd;    /* Command number */
+       __u16                   csize;  /* Attached crypto information size */
+       __u16                   cpad;   /* Attached padding size */
+       __u16                   ext;    /* External flags */
+       __u32                   size;   /* Size of the attached data */
+       __u32                   trans;  /* Transaction id */
+       __u64                   id;     /* Object ID to operate on. Used for feedback.*/
+       __u64                   start;  /* Start of the object. */
+       __u64                   iv;     /* IV sequence */
+       __u8                    data[0];
+};
+
+Commands can be embedded into transaction command (which in turn has own command),
+so one can extend protocol as needed without breaking backward compatibility as long
+as old commands are supported. All string lengths include tail 0 byte.
+
+All commans are transfered over the network in big-endian. CPU endianess is used at the end peers.
+
+@cmd - command number, which specifies command to be processed. Following
+       commands are used currently:
+
+       NETFS_READDIR   = 1,    /* Read directory for given inode number */
+       NETFS_READ_PAGE,        /* Read data page from the server */
+       NETFS_WRITE_PAGE,       /* Write data page to the server */
+       NETFS_CREATE,           /* Create directory entry */
+       NETFS_REMOVE,           /* Remove directory entry */
+       NETFS_LOOKUP,           /* Lookup single object */
+       NETFS_LINK,             /* Create a link */
+       NETFS_TRANS,            /* Transaction */
+       NETFS_OPEN,             /* Open intent */
+       NETFS_INODE_INFO,       /* Metadata cache coherency synchronization message */
+       NETFS_PAGE_CACHE,       /* Page cache invalidation message */
+       NETFS_READ_PAGES,       /* Read multiple contiguous pages in one go */
+       NETFS_RENAME,           /* Rename object */
+       NETFS_CAPABILITIES,     /* Capabilities of the client, for example supported crypto */
+       NETFS_LOCK,             /* Distributed lock message */
+       NETFS_XATTR_SET,        /* Set extended attribute */
+       NETFS_XATTR_GET,        /* Get extended attribute */
+
+@ext - external flags. Used by different commands to specify some extra arguments
+       like partial size of the embedded objects or creation flags.
+
+@size - size of the attached data. For NETFS_READ_PAGE and NETFS_READ_PAGES no data is attached,
+       but size of the requested data is incorporated here. It does not include size of the command
+       header (struct netfs_cmd) itself.
+
+@id - id of the object this command operates on. Each command can use it for own purpose.
+
+@start - start of the object this command operates on. Each command can use it for own purpose.
+
+@csize, @cpad - size and padding size of the (attached if needed) crypto information.
+
+Command specifications.
+
+@NETFS_READDIR
+This command is used to sync content of the remote dir to the client.
+
+@ext - length of the path to object.
+@size - the same.
+@id - local inode number of the directory to read.
+@start - zero.
+
+
+@NETFS_READ_PAGE
+This command is used to read data from remote server.
+Data size does not exceed local page cache size.
+
+@id - inode number.
+@start - first byte offset.
+@size - number of bytes to read plus length of the path to object.
+@ext - object path length.
+
+
+@NETFS_CREATE
+Used to create object.
+It does not require that all directories on top of the object were
+already created, it will create them automatically. Each object has
+associated @netfs_path_entry data structure, which contains creation
+mode (permissions and type) and length of the name as long as name itself.
+
+@start - 0
+@size - size of the all data structures needed to create a path
+@id - local inode number
+@ext - 0
+
+
+@NETFS_REMOVE
+Used to remove object.
+
+@ext - length of the path to object.
+@size - the same.
+@id - local inode number.
+@start - zero.
+
+
+@NETFS_LOOKUP
+Lookup information about object on server.
+
+@ext - length of the path to object.
+@size - the same.
+@id - local inode number of the directory to look object in.
+@start - local inode number of the object to look at.
+
+
+@NETFS_LINK
+Create hard of symlink.
+Command is sent as "object_path|target_path".
+
+@size - size of the above string.
+@id - parent local inode number.
+@start - 1 for symlink, 0 for hardlink.
+@ext - size of the "object_path" above.
+
+
+@NETFS_TRANS
+Transaction header.
+
+@size - incorporates all embedded command sizes including theirs header sizes.
+@start - transaction generation number - unique id used to find transaction.
+@ext - transaction flags. Unused at the moment.
+@id - 0.
+
+
+@NETFS_OPEN
+Open intent for given transaction.
+
+@id - local inode number.
+@start - 0.
+@size - path length to the object.
+@ext - open flags (O_RDWR and so on).
+
+
+@NETFS_INODE_INFO
+Metadata update command.
+It is sent to servers when attributes of the object are changed and received
+when data or metadata were updated. It operates with the following structure:
+
+struct netfs_inode_info
+{
+       unsigned int            mode;
+       unsigned int            nlink;
+       unsigned int            uid;
+       unsigned int            gid;
+       unsigned int            blocksize;
+       unsigned int            padding;
+       __u64                   ino;
+       __u64                   blocks;
+       __u64                   rdev;
+       __u64                   size;
+       __u64                   version;
+};
+
+It effectively mirrors stat(2) returned data.
+
+
+@ext - path length to the object.
+@size - the same plus size of the netfs_inode_info structure.
+@id - local inode number.
+@start - 0.
+
+
+@NETFS_PAGE_CACHE
+Command is only received by clients. It contains information about
+page to be marked as not up-to-date.
+
+@id - client's inode number.
+@start - last byte of the page to be invalidated. If it is not equal to
+       current inode size, it will be vmtruncated().
+@size - 0
+@ext - 0
+
+
+@NETFS_READ_PAGES
+Used to read multiple contiguous pages in one go.
+
+@start - first byte of the contiguous region to read.
+@size - contains of two fields: lower 8 bits are used to represent page cache shift
+       used by client, another 3 bytes are used to get number of pages.
+@id - local inode number.
+@ext - path length to the object.
+
+
+@NETFS_RENAME
+Used to rename object.
+Attached data is formed into following string: "old_path|new_path".
+
+@id - local inode number.
+@start - parent inode number.
+@size - length of the above string.
+@ext - length of the old path part.
+
+
+@NETFS_CAPABILITIES
+Used to exchange crypto capabilities with server.
+If crypto capabilities are not supported by server, then client will disable it
+or fail (if 'crypto_fail_unsupported' mount options was specified).
+
+@id - superblock index. Used to specify crypto information for group of servers.
+@size - size of the attached capabilities structure.
+@start - 0.
+@size - 0.
+@scsize - 0.
+
+@NETFS_LOCK
+Used to send lock request/release messages. Although it sends byte range request
+and is capable of flushing pages based on that, it is not used, since all Linux
+filesystems lock the whole inode.
+
+@id - lock generation number.
+@start - start of the locked range.
+@size - size of the locked range.
+@ext - lock type: read/write. Not used actually. 15'th bit is used to determine,
+       if it is lock request (1) or release (0).
+
+@NETFS_XATTR_SET
+@NETFS_XATTR_GET
+Used to set/get extended attributes for given inode.
+@id - attribute generation number or xattr setting type
+@start - size of the attribute (request or attached)
+@size - name length, path len and data size for given attribute
+@ext - path length for given object
index 803b1318b13da11242a3558123d28293d3ee4378..fd9a3e69381351aeeaa6712d07c5170aa7dca1a4 100644 (file)
@@ -15,31 +15,31 @@ Introduction
 
 Ftrace is an internal tracer designed to help out developers and
 designers of systems to find what is going on inside the kernel.
-It can be used for debugging or analyzing latencies and performance
-issues that take place outside of user-space.
+It can be used for debugging or analyzing latencies and
+performance issues that take place outside of user-space.
 
 Although ftrace is the function tracer, it also includes an
-infrastructure that allows for other types of tracing. Some of the
-tracers that are currently in ftrace include a tracer to trace
-context switches, the time it takes for a high priority task to
-run after it was woken up, the time interrupts are disabled, and
-more (ftrace allows for tracer plugins, which means that the list of
-tracers can always grow).
+infrastructure that allows for other types of tracing. Some of
+the tracers that are currently in ftrace include a tracer to
+trace context switches, the time it takes for a high priority
+task to run after it was woken up, the time interrupts are
+disabled, and more (ftrace allows for tracer plugins, which
+means that the list of tracers can always grow).
 
 
 The File System
 ---------------
 
-Ftrace uses the debugfs file system to hold the control files as well
-as the files to display output.
+Ftrace uses the debugfs file system to hold the control files as
+well as the files to display output.
 
 To mount the debugfs system:
 
   # mkdir /debug
   # mount -t debugfs nodev /debug
 
-(Note: it is more common to mount at /sys/kernel/debug, but for simplicity
- this document will use /debug)
+( Note: it is more common to mount at /sys/kernel/debug, but for
 simplicity this document will use /debug)
 
 That's it! (assuming that you have ftrace configured into your kernel)
 
@@ -50,90 +50,124 @@ of ftrace. Here is a list of some of the key files:
 
  Note: all time values are in microseconds.
 
-  current_tracer: This is used to set or display the current tracer
-               that is configured.
-
-  available_tracers: This holds the different types of tracers that
-               have been compiled into the kernel. The tracers
-               listed here can be configured by echoing their name
-               into current_tracer.
-
-  tracing_enabled: This sets or displays whether the current_tracer
-               is activated and tracing or not. Echo 0 into this
-               file to disable the tracer or 1 to enable it.
-
-  trace: This file holds the output of the trace in a human readable
-               format (described below).
-
-  latency_trace: This file shows the same trace but the information
-               is organized more to display possible latencies
-               in the system (described below).
-
-  trace_pipe: The output is the same as the "trace" file but this
-               file is meant to be streamed with live tracing.
-               Reads from this file will block until new data
-               is retrieved. Unlike the "trace" and "latency_trace"
-               files, this file is a consumer. This means reading
-               from this file causes sequential reads to display
-               more current data. Once data is read from this
-               file, it is consumed, and will not be read
-               again with a sequential read. The "trace" and
-               "latency_trace" files are static, and if the
-               tracer is not adding more data, they will display
-               the same information every time they are read.
-
-  trace_options: This file lets the user control the amount of data
-               that is displayed in one of the above output
-               files.
-
-  trace_max_latency: Some of the tracers record the max latency.
-               For example, the time interrupts are disabled.
-               This time is saved in this file. The max trace
-               will also be stored, and displayed by either
-               "trace" or "latency_trace".  A new max trace will
-               only be recorded if the latency is greater than
-               the value in this file. (in microseconds)
-
-  buffer_size_kb: This sets or displays the number of kilobytes each CPU
-               buffer can hold. The tracer buffers are the same size
-               for each CPU. The displayed number is the size of the
-               CPU buffer and not total size of all buffers. The
-               trace buffers are allocated in pages (blocks of memory
-               that the kernel uses for allocation, usually 4 KB in size).
-               If the last page allocated has room for more bytes
-               than requested, the rest of the page will be used,
-               making the actual allocation bigger than requested.
-               (Note, the size may not be a multiple of the page size due
-               to buffer managment overhead.)
-
-               This can only be updated when the current_tracer
-               is set to "nop".
-
-  tracing_cpumask: This is a mask that lets the user only trace
-               on specified CPUS. The format is a hex string
-               representing the CPUS.
-
-  set_ftrace_filter: When dynamic ftrace is configured in (see the
-               section below "dynamic ftrace"), the code is dynamically
-               modified (code text rewrite) to disable calling of the
-               function profiler (mcount). This lets tracing be configured
-               in with practically no overhead in performance.  This also
-               has a side effect of enabling or disabling specific functions
-               to be traced. Echoing names of functions into this file
-               will limit the trace to only those functions.
-
-  set_ftrace_notrace: This has an effect opposite to that of
-               set_ftrace_filter. Any function that is added here will not
-               be traced. If a function exists in both set_ftrace_filter
-               and set_ftrace_notrace, the function will _not_ be traced.
-
-  set_ftrace_pid: Have the function tracer only trace a single thread.
-
-  available_filter_functions: This lists the functions that ftrace
-               has processed and can trace. These are the function
-               names that you can pass to "set_ftrace_filter" or
-               "set_ftrace_notrace". (See the section "dynamic ftrace"
-               below for more details.)
+  current_tracer:
+
+       This is used to set or display the current tracer
+       that is configured.
+
+  available_tracers:
+
+       This holds the different types of tracers that
+       have been compiled into the kernel. The
+       tracers listed here can be configured by
+       echoing their name into current_tracer.
+
+  tracing_enabled:
+
+       This sets or displays whether the current_tracer
+       is activated and tracing or not. Echo 0 into this
+       file to disable the tracer or 1 to enable it.
+
+  trace:
+
+       This file holds the output of the trace in a human
+       readable format (described below).
+
+  latency_trace:
+
+       This file shows the same trace but the information
+       is organized more to display possible latencies
+       in the system (described below).
+
+  trace_pipe:
+
+       The output is the same as the "trace" file but this
+       file is meant to be streamed with live tracing.
+       Reads from this file will block until new data
+       is retrieved. Unlike the "trace" and "latency_trace"
+       files, this file is a consumer. This means reading
+       from this file causes sequential reads to display
+       more current data. Once data is read from this
+       file, it is consumed, and will not be read
+       again with a sequential read. The "trace" and
+       "latency_trace" files are static, and if the
+       tracer is not adding more data, they will display
+       the same information every time they are read.
+
+  trace_options:
+
+       This file lets the user control the amount of data
+       that is displayed in one of the above output
+       files.
+
+  tracing_max_latency:
+
+       Some of the tracers record the max latency.
+       For example, the time interrupts are disabled.
+       This time is saved in this file. The max trace
+       will also be stored, and displayed by either
+       "trace" or "latency_trace".  A new max trace will
+       only be recorded if the latency is greater than
+       the value in this file. (in microseconds)
+
+  buffer_size_kb:
+
+       This sets or displays the number of kilobytes each CPU
+       buffer can hold. The tracer buffers are the same size
+       for each CPU. The displayed number is the size of the
+       CPU buffer and not total size of all buffers. The
+       trace buffers are allocated in pages (blocks of memory
+       that the kernel uses for allocation, usually 4 KB in size).
+       If the last page allocated has room for more bytes
+       than requested, the rest of the page will be used,
+       making the actual allocation bigger than requested.
+       ( Note, the size may not be a multiple of the page size
+         due to buffer managment overhead. )
+
+       This can only be updated when the current_tracer
+       is set to "nop".
+
+  tracing_cpumask:
+
+       This is a mask that lets the user only trace
+       on specified CPUS. The format is a hex string
+       representing the CPUS.
+
+  set_ftrace_filter:
+
+       When dynamic ftrace is configured in (see the
+       section below "dynamic ftrace"), the code is dynamically
+       modified (code text rewrite) to disable calling of the
+       function profiler (mcount). This lets tracing be configured
+       in with practically no overhead in performance.  This also
+       has a side effect of enabling or disabling specific functions
+       to be traced. Echoing names of functions into this file
+       will limit the trace to only those functions.
+
+  set_ftrace_notrace:
+
+       This has an effect opposite to that of
+       set_ftrace_filter. Any function that is added here will not
+       be traced. If a function exists in both set_ftrace_filter
+       and set_ftrace_notrace, the function will _not_ be traced.
+
+  set_ftrace_pid:
+
+       Have the function tracer only trace a single thread.
+
+  set_graph_function:
+
+       Set a "trigger" function where tracing should start
+       with the function graph tracer (See the section
+       "dynamic ftrace" for more details).
+
+  available_filter_functions:
+
+       This lists the functions that ftrace
+       has processed and can trace. These are the function
+       names that you can pass to "set_ftrace_filter" or
+       "set_ftrace_notrace". (See the section "dynamic ftrace"
+       below for more details.)
 
 
 The Tracers
@@ -141,36 +175,66 @@ The Tracers
 
 Here is the list of current tracers that may be configured.
 
-  function - function tracer that uses mcount to trace all functions.
+  "function"
+
+       Function call tracer to trace all kernel functions.
+
+  "function_graph_tracer"
+
+       Similar to the function tracer except that the
+       function tracer probes the functions on their entry
+       whereas the function graph tracer traces on both entry
+       and exit of the functions. It then provides the ability
+       to draw a graph of function calls similar to C code
+       source.
 
-  sched_switch - traces the context switches between tasks.
+  "sched_switch"
 
-  irqsoff - traces the areas that disable interrupts and saves
-               the trace with the longest max latency.
-               See tracing_max_latency.  When a new max is recorded,
-               it replaces the old trace. It is best to view this
-               trace via the latency_trace file.
+       Traces the context switches and wakeups between tasks.
 
-  preemptoff - Similar to irqsoff but traces and records the amount of
-               time for which preemption is disabled.
+  "irqsoff"
 
-  preemptirqsoff - Similar to irqsoff and preemptoff, but traces and
-                records the largest time for which irqs and/or preemption
-                is disabled.
+       Traces the areas that disable interrupts and saves
+       the trace with the longest max latency.
+       See tracing_max_latency. When a new max is recorded,
+       it replaces the old trace. It is best to view this
+       trace via the latency_trace file.
 
-  wakeup - Traces and records the max latency that it takes for
-               the highest priority task to get scheduled after
-               it has been woken up.
+  "preemptoff"
 
-  nop - This is not a tracer. To remove all tracers from tracing
-               simply echo "nop" into current_tracer.
+       Similar to irqsoff but traces and records the amount of
+       time for which preemption is disabled.
+
+  "preemptirqsoff"
+
+       Similar to irqsoff and preemptoff, but traces and
+       records the largest time for which irqs and/or preemption
+       is disabled.
+
+  "wakeup"
+
+       Traces and records the max latency that it takes for
+       the highest priority task to get scheduled after
+       it has been woken up.
+
+  "hw-branch-tracer"
+
+       Uses the BTS CPU feature on x86 CPUs to traces all
+       branches executed.
+
+  "nop"
+
+       This is the "trace nothing" tracer. To remove all
+       tracers from tracing simply echo "nop" into
+       current_tracer.
 
 
 Examples of using the tracer
 ----------------------------
 
-Here are typical examples of using the tracers when controlling them only
-with the debugfs interface (without using any user-land utilities).
+Here are typical examples of using the tracers when controlling
+them only with the debugfs interface (without using any
+user-land utilities).
 
 Output format:
 --------------
@@ -187,16 +251,16 @@ Here is an example of the output format of the file "trace"
             bash-4251  [01] 10152.583855: _atomic_dec_and_lock <-dput
                              --------
 
-A header is printed with the tracer name that is represented by the trace.
-In this case the tracer is "function". Then a header showing the format. Task
-name "bash", the task PID "4251", the CPU that it was running on
-"01", the timestamp in <secs>.<usecs> format, the function name that was
-traced "path_put" and the parent function that called this function
-"path_walk". The timestamp is the time at which the function was
-entered.
+A header is printed with the tracer name that is represented by
+the trace. In this case the tracer is "function". Then a header
+showing the format. Task name "bash", the task PID "4251", the
+CPU that it was running on "01", the timestamp in <secs>.<usecs>
+format, the function name that was traced "path_put" and the
+parent function that called this function "path_walk". The
+timestamp is the time at which the function was entered.
 
-The sched_switch tracer also includes tracing of task wakeups and
-context switches.
+The sched_switch tracer also includes tracing of task wakeups
+and context switches.
 
      ksoftirqd/1-7     [01]  1453.070013:      7:115:R   +  2916:115:S
      ksoftirqd/1-7     [01]  1453.070013:      7:115:R   +    10:115:S
@@ -205,8 +269,8 @@ context switches.
      kondemand/1-2916  [01]  1453.070013:   2916:115:S ==>     7:115:R
      ksoftirqd/1-7     [01]  1453.070013:      7:115:S ==>     0:140:R
 
-Wake ups are represented by a "+" and the context switches are shown as
-"==>".  The format is:
+Wake ups are represented by a "+" and the context switches are
+shown as "==>".  The format is:
 
  Context switches:
 
@@ -220,19 +284,20 @@ Wake ups are represented by a "+" and the context switches are shown as
 
   <pid>:<prio>:<state>    +  <pid>:<prio>:<state>
 
-The prio is the internal kernel priority, which is the inverse of the
-priority that is usually displayed by user-space tools. Zero represents
-the highest priority (99). Prio 100 starts the "nice" priorities with
-100 being equal to nice -20 and 139 being nice 19. The prio "140" is
-reserved for the idle task which is the lowest priority thread (pid 0).
+The prio is the internal kernel priority, which is the inverse
+of the priority that is usually displayed by user-space tools.
+Zero represents the highest priority (99). Prio 100 starts the
+"nice" priorities with 100 being equal to nice -20 and 139 being
+nice 19. The prio "140" is reserved for the idle task which is
+the lowest priority thread (pid 0).
 
 
 Latency trace format
 --------------------
 
-For traces that display latency times, the latency_trace file gives
-somewhat more information to see why a latency happened. Here is a typical
-trace.
+For traces that display latency times, the latency_trace file
+gives somewhat more information to see why a latency happened.
+Here is a typical trace.
 
 # tracer: irqsoff
 #
@@ -259,20 +324,20 @@ irqsoff latency trace v1.1.5 on 2.6.26-rc8
   <idle>-0     0d.s1   98us : trace_hardirqs_on (do_softirq)
 
 
+This shows that the current tracer is "irqsoff" tracing the time
+for which interrupts were disabled. It gives the trace version
+and the version of the kernel upon which this was executed on
+(2.6.26-rc8). Then it displays the max latency in microsecs (97
+us). The number of trace entries displayed and the total number
+recorded (both are three: #3/3). The type of preemption that was
+used (PREEMPT). VP, KP, SP, and HP are always zero and are
+reserved for later use. #P is the number of online CPUS (#P:2).
 
-This shows that the current tracer is "irqsoff" tracing the time for which
-interrupts were disabled. It gives the trace version and the version
-of the kernel upon which this was executed on (2.6.26-rc8). Then it displays
-the max latency in microsecs (97 us). The number of trace entries displayed
-and the total number recorded (both are three: #3/3). The type of
-preemption that was used (PREEMPT). VP, KP, SP, and HP are always zero
-and are reserved for later use. #P is the number of online CPUS (#P:2).
-
-The task is the process that was running when the latency occurred.
-(swapper pid: 0).
+The task is the process that was running when the latency
+occurred. (swapper pid: 0).
 
-The start and stop (the functions in which the interrupts were disabled and
-enabled respectively) that caused the latencies:
+The start and stop (the functions in which the interrupts were
+disabled and enabled respectively) that caused the latencies:
 
   apic_timer_interrupt is where the interrupts were disabled.
   do_softirq is where they were enabled again.
@@ -308,12 +373,12 @@ The above is mostly meaningful for kernel developers.
        latency_trace file is relative to the start of the trace.
 
   delay: This is just to help catch your eye a bit better. And
-       needs to be fixed to be only relative to the same CPU.
-       The marks are determined by the difference between this
-       current trace and the next trace.
-        '!' - greater than preempt_mark_thresh (default 100)
-        '+' - greater than 1 microsecond
-        ' ' - less than or equal to 1 microsecond.
+        needs to be fixed to be only relative to the same CPU.
+        The marks are determined by the difference between this
+        current trace and the next trace.
+         '!' - greater than preempt_mark_thresh (default 100)
+         '+' - greater than 1 microsecond
+         ' ' - less than or equal to 1 microsecond.
 
   The rest is the same as the 'trace' file.
 
@@ -321,14 +386,15 @@ The above is mostly meaningful for kernel developers.
 trace_options
 -------------
 
-The trace_options file is used to control what gets printed in the trace
-output. To see what is available, simply cat the file:
+The trace_options file is used to control what gets printed in
+the trace output. To see what is available, simply cat the file:
 
   cat /debug/tracing/trace_options
   print-parent nosym-offset nosym-addr noverbose noraw nohex nobin \
- noblock nostacktrace nosched-tree nouserstacktrace nosym-userobj
 noblock nostacktrace nosched-tree nouserstacktrace nosym-userobj
 
-To disable one of the options, echo in the option prepended with "no".
+To disable one of the options, echo in the option prepended with
+"no".
 
   echo noprint-parent > /debug/tracing/trace_options
 
@@ -338,8 +404,8 @@ To enable an option, leave off the "no".
 
 Here are the available options:
 
-  print-parent - On function traces, display the calling function
-               as well as the function being traced.
+  print-parent - On function traces, display the calling (parent)
+                function as well as the function being traced.
 
   print-parent:
    bash-4000  [01]  1477.606694: simple_strtoul <-strict_strtoul
@@ -348,15 +414,16 @@ Here are the available options:
    bash-4000  [01]  1477.606694: simple_strtoul
 
 
-  sym-offset - Display not only the function name, but also the offset
-               in the function. For example, instead of seeing just
-               "ktime_get", you will see "ktime_get+0xb/0x20".
+  sym-offset - Display not only the function name, but also the
+              offset in the function. For example, instead of
+              seeing just "ktime_get", you will see
+              "ktime_get+0xb/0x20".
 
   sym-offset:
    bash-4000  [01]  1477.606694: simple_strtoul+0x6/0xa0
 
-  sym-addr - this will also display the function address as well as
-               the function name.
+  sym-addr - this will also display the function address as well
+            as the function name.
 
   sym-addr:
    bash-4000  [01]  1477.606694: simple_strtoul <c0339346>
@@ -366,35 +433,41 @@ Here are the available options:
     bash  4000 1 0 00000000 00010a95 [58127d26] 1720.415ms \
     (+0.000ms): simple_strtoul (strict_strtoul)
 
-  raw - This will display raw numbers. This option is best for use with
-       user applications that can translate the raw numbers better than
-       having it done in the kernel.
+  raw - This will display raw numbers. This option is best for
+       use with user applications that can translate the raw
+       numbers better than having it done in the kernel.
 
-  hex - Similar to raw, but the numbers will be in a hexadecimal format.
+  hex - Similar to raw, but the numbers will be in a hexadecimal
+       format.
 
   bin - This will print out the formats in raw binary.
 
   block - TBD (needs update)
 
-  stacktrace - This is one of the options that changes the trace itself.
-               When a trace is recorded, so is the stack of functions.
-               This allows for back traces of trace sites.
+  stacktrace - This is one of the options that changes the trace
+              itself. When a trace is recorded, so is the stack
+              of functions. This allows for back traces of
+              trace sites.
 
-  userstacktrace - This option changes the trace.
-                  It records a stacktrace of the current userspace thread.
+  userstacktrace - This option changes the trace. It records a
+                  stacktrace of the current userspace thread.
 
-  sym-userobj - when user stacktrace are enabled, look up which object the
-               address belongs to, and print a relative address
-               This is especially useful when ASLR is on, otherwise you don't
-               get a chance to resolve the address to object/file/line after the app is no
-               longer running
+  sym-userobj - when user stacktrace are enabled, look up which
+               object the address belongs to, and print a
+               relative address. This is especially useful when
+               ASLR is on, otherwise you don't get a chance to
+               resolve the address to object/file/line after
+               the app is no longer running
 
-               The lookup is performed when you read trace,trace_pipe,latency_trace. Example:
+               The lookup is performed when you read
+               trace,trace_pipe,latency_trace. Example:
 
                a.out-1623  [000] 40874.465068: /root/a.out[+0x480] <-/root/a.out[+0
 x494] <- /root/a.out[+0x4a8] <- /lib/libc-2.7.so[+0x1e1a6]
 
-  sched-tree - TBD (any users??)
+  sched-tree - trace all tasks that are on the runqueue, at
+              every scheduling event. Will add overhead if
+              there's a lot of tasks running at once.
 
 
 sched_switch
@@ -431,18 +504,19 @@ of how to use it.
  [...]
 
 
-As we have discussed previously about this format, the header shows
-the name of the trace and points to the options. The "FUNCTION"
-is a misnomer since here it represents the wake ups and context
-switches.
+As we have discussed previously about this format, the header
+shows the name of the trace and points to the options. The
+"FUNCTION" is a misnomer since here it represents the wake ups
+and context switches.
 
-The sched_switch file only lists the wake ups (represented with '+')
-and context switches ('==>') with the previous task or current task
-first followed by the next task or task waking up. The format for both
-of these is PID:KERNEL-PRIO:TASK-STATE. Remember that the KERNEL-PRIO
-is the inverse of the actual priority with zero (0) being the highest
-priority and the nice values starting at 100 (nice -20). Below is
-a quick chart to map the kernel priority to user land priorities.
+The sched_switch file only lists the wake ups (represented with
+'+') and context switches ('==>') with the previous task or
+current task first followed by the next task or task waking up.
+The format for both of these is PID:KERNEL-PRIO:TASK-STATE.
+Remember that the KERNEL-PRIO is the inverse of the actual
+priority with zero (0) being the highest priority and the nice
+values starting at 100 (nice -20). Below is a quick chart to map
+the kernel priority to user land priorities.
 
   Kernel priority: 0 to 99    ==> user RT priority 99 to 0
   Kernel priority: 100 to 139 ==> user nice -20 to 19
@@ -463,10 +537,10 @@ The task states are:
 ftrace_enabled
 --------------
 
-The following tracers (listed below) give different output depending
-on whether or not the sysctl ftrace_enabled is set. To set ftrace_enabled,
-one can either use the sysctl function or set it via the proc
-file system interface.
+The following tracers (listed below) give different output
+depending on whether or not the sysctl ftrace_enabled is set. To
+set ftrace_enabled, one can either use the sysctl function or
+set it via the proc file system interface.
 
   sysctl kernel.ftrace_enabled=1
 
@@ -474,12 +548,12 @@ file system interface.
 
   echo 1 > /proc/sys/kernel/ftrace_enabled
 
-To disable ftrace_enabled simply replace the '1' with '0' in
-the above commands.
+To disable ftrace_enabled simply replace the '1' with '0' in the
+above commands.
 
-When ftrace_enabled is set the tracers will also record the functions
-that are within the trace. The descriptions of the tracers
-will also show an example with ftrace enabled.
+When ftrace_enabled is set the tracers will also record the
+functions that are within the trace. The descriptions of the
+tracers will also show an example with ftrace enabled.
 
 
 irqsoff
@@ -487,17 +561,18 @@ irqsoff
 
 When interrupts are disabled, the CPU can not react to any other
 external event (besides NMIs and SMIs). This prevents the timer
-interrupt from triggering or the mouse interrupt from letting the
-kernel know of a new mouse event. The result is a latency with the
-reaction time.
+interrupt from triggering or the mouse interrupt from letting
+the kernel know of a new mouse event. The result is a latency
+with the reaction time.
 
-The irqsoff tracer tracks the time for which interrupts are disabled.
-When a new maximum latency is hit, the tracer saves the trace leading up
-to that latency point so that every time a new maximum is reached, the old
-saved trace is discarded and the new trace is saved.
+The irqsoff tracer tracks the time for which interrupts are
+disabled. When a new maximum latency is hit, the tracer saves
+the trace leading up to that latency point so that every time a
+new maximum is reached, the old saved trace is discarded and the
+new trace is saved.
 
-To reset the maximum, echo 0 into tracing_max_latency. Here is an
-example:
+To reset the maximum, echo 0 into tracing_max_latency. Here is
+an example:
 
  # echo irqsoff > /debug/tracing/current_tracer
  # echo 0 > /debug/tracing/tracing_max_latency
@@ -532,10 +607,11 @@ irqsoff latency trace v1.1.5 on 2.6.26
 
 
 Here we see that that we had a latency of 12 microsecs (which is
-very good). The _write_lock_irq in sys_setpgid disabled interrupts.
-The difference between the 12 and the displayed timestamp 14us occurred
-because the clock was incremented between the time of recording the max
-latency and the time of recording the function that had that latency.
+very good). The _write_lock_irq in sys_setpgid disabled
+interrupts. The difference between the 12 and the displayed
+timestamp 14us occurred because the clock was incremented
+between the time of recording the max latency and the time of
+recording the function that had that latency.
 
 Note the above example had ftrace_enabled not set. If we set the
 ftrace_enabled, we get a much larger output:
@@ -586,24 +662,24 @@ irqsoff latency trace v1.1.5 on 2.6.26-rc8
 
 
 Here we traced a 50 microsecond latency. But we also see all the
-functions that were called during that time. Note that by enabling
-function tracing, we incur an added overhead. This overhead may
-extend the latency times. But nevertheless, this trace has provided
-some very helpful debugging information.
+functions that were called during that time. Note that by
+enabling function tracing, we incur an added overhead. This
+overhead may extend the latency times. But nevertheless, this
+trace has provided some very helpful debugging information.
 
 
 preemptoff
 ----------
 
-When preemption is disabled, we may be able to receive interrupts but
-the task cannot be preempted and a higher priority task must wait
-for preemption to be enabled again before it can preempt a lower
-priority task.
+When preemption is disabled, we may be able to receive
+interrupts but the task cannot be preempted and a higher
+priority task must wait for preemption to be enabled again
+before it can preempt a lower priority task.
 
 The preemptoff tracer traces the places that disable preemption.
-Like the irqsoff tracer, it records the maximum latency for which preemption
-was disabled. The control of preemptoff tracer is much like the irqsoff
-tracer.
+Like the irqsoff tracer, it records the maximum latency for
+which preemption was disabled. The control of preemptoff tracer
+is much like the irqsoff tracer.
 
  # echo preemptoff > /debug/tracing/current_tracer
  # echo 0 > /debug/tracing/tracing_max_latency
@@ -637,11 +713,12 @@ preemptoff latency trace v1.1.5 on 2.6.26-rc8
     sshd-4261  0d.s1   30us : trace_preempt_on (__do_softirq)
 
 
-This has some more changes. Preemption was disabled when an interrupt
-came in (notice the 'h'), and was enabled while doing a softirq.
-(notice the 's'). But we also see that interrupts have been disabled
-when entering the preempt off section and leaving it (the 'd').
-We do not know if interrupts were enabled in the mean time.
+This has some more changes. Preemption was disabled when an
+interrupt came in (notice the 'h'), and was enabled while doing
+a softirq. (notice the 's'). But we also see that interrupts
+have been disabled when entering the preempt off section and
+leaving it (the 'd'). We do not know if interrupts were enabled
+in the mean time.
 
 # tracer: preemptoff
 #
@@ -700,28 +777,30 @@ preemptoff latency trace v1.1.5 on 2.6.26-rc8
     sshd-4261  0d.s1   64us : trace_preempt_on (__do_softirq)
 
 
-The above is an example of the preemptoff trace with ftrace_enabled
-set. Here we see that interrupts were disabled the entire time.
-The irq_enter code lets us know that we entered an interrupt 'h'.
-Before that, the functions being traced still show that it is not
-in an interrupt, but we can see from the functions themselves that
-this is not the case.
+The above is an example of the preemptoff trace with
+ftrace_enabled set. Here we see that interrupts were disabled
+the entire time. The irq_enter code lets us know that we entered
+an interrupt 'h'. Before that, the functions being traced still
+show that it is not in an interrupt, but we can see from the
+functions themselves that this is not the case.
 
-Notice that __do_softirq when called does not have a preempt_count.
-It may seem that we missed a preempt enabling. What really happened
-is that the preempt count is held on the thread's stack and we
-switched to the softirq stack (4K stacks in effect). The code
-does not copy the preempt count, but because interrupts are disabled,
-we do not need to worry about it. Having a tracer like this is good
-for letting people know what really happens inside the kernel.
+Notice that __do_softirq when called does not have a
+preempt_count. It may seem that we missed a preempt enabling.
+What really happened is that the preempt count is held on the
+thread's stack and we switched to the softirq stack (4K stacks
+in effect). The code does not copy the preempt count, but
+because interrupts are disabled, we do not need to worry about
+it. Having a tracer like this is good for letting people know
+what really happens inside the kernel.
 
 
 preemptirqsoff
 --------------
 
-Knowing the locations that have interrupts disabled or preemption
-disabled for the longest times is helpful. But sometimes we would
-like to know when either preemption and/or interrupts are disabled.
+Knowing the locations that have interrupts disabled or
+preemption disabled for the longest times is helpful. But
+sometimes we would like to know when either preemption and/or
+interrupts are disabled.
 
 Consider the following code:
 
@@ -741,11 +820,13 @@ The preemptoff tracer will record the total length of
 call_function_with_irqs_and_preemption_off() and
 call_function_with_preemption_off().
 
-But neither will trace the time that interrupts and/or preemption
-is disabled. This total time is the time that we can not schedule.
-To record this time, use the preemptirqsoff tracer.
+But neither will trace the time that interrupts and/or
+preemption is disabled. This total time is the time that we can
+not schedule. To record this time, use the preemptirqsoff
+tracer.
 
-Again, using this trace is much like the irqsoff and preemptoff tracers.
+Again, using this trace is much like the irqsoff and preemptoff
+tracers.
 
  # echo preemptirqsoff > /debug/tracing/current_tracer
  # echo 0 > /debug/tracing/tracing_max_latency
@@ -781,9 +862,10 @@ preemptirqsoff latency trace v1.1.5 on 2.6.26-rc8
 
 
 The trace_hardirqs_off_thunk is called from assembly on x86 when
-interrupts are disabled in the assembly code. Without the function
-tracing, we do not know if interrupts were enabled within the preemption
-points. We do see that it started with preemption enabled.
+interrupts are disabled in the assembly code. Without the
+function tracing, we do not know if interrupts were enabled
+within the preemption points. We do see that it started with
+preemption enabled.
 
 Here is a trace with ftrace_enabled set:
 
@@ -871,40 +953,42 @@ preemptirqsoff latency trace v1.1.5 on 2.6.26-rc8
     sshd-4261  0d.s1  105us : trace_preempt_on (__do_softirq)
 
 
-This is a very interesting trace. It started with the preemption of
-the ls task. We see that the task had the "need_resched" bit set
-via the 'N' in the trace.  Interrupts were disabled before the spin_lock
-at the beginning of the trace. We see that a schedule took place to run
-sshd.  When the interrupts were enabled, we took an interrupt.
-On return from the interrupt handler, the softirq ran. We took another
-interrupt while running the softirq as we see from the capital 'H'.
+This is a very interesting trace. It started with the preemption
+of the ls task. We see that the task had the "need_resched" bit
+set via the 'N' in the trace.  Interrupts were disabled before
+the spin_lock at the beginning of the trace. We see that a
+schedule took place to run sshd.  When the interrupts were
+enabled, we took an interrupt. On return from the interrupt
+handler, the softirq ran. We took another interrupt while
+running the softirq as we see from the capital 'H'.
 
 
 wakeup
 ------
 
-In a Real-Time environment it is very important to know the wakeup
-time it takes for the highest priority task that is woken up to the
-time that it executes. This is also known as "schedule latency".
-I stress the point that this is about RT tasks. It is also important
-to know the scheduling latency of non-RT tasks, but the average
-schedule latency is better for non-RT tasks. Tools like
-LatencyTop are more appropriate for such measurements.
+In a Real-Time environment it is very important to know the
+wakeup time it takes for the highest priority task that is woken
+up to the time that it executes. This is also known as "schedule
+latency". I stress the point that this is about RT tasks. It is
+also important to know the scheduling latency of non-RT tasks,
+but the average schedule latency is better for non-RT tasks.
+Tools like LatencyTop are more appropriate for such
+measurements.
 
 Real-Time environments are interested in the worst case latency.
-That is the longest latency it takes for something to happen, and
-not the average. We can have a very fast scheduler that may only
-have a large latency once in a while, but that would not work well
-with Real-Time tasks.  The wakeup tracer was designed to record
-the worst case wakeups of RT tasks. Non-RT tasks are not recorded
-because the tracer only records one worst case and tracing non-RT
-tasks that are unpredictable will overwrite the worst case latency
-of RT tasks.
-
-Since this tracer only deals with RT tasks, we will run this slightly
-differently than we did with the previous tracers. Instead of performing
-an 'ls', we will run 'sleep 1' under 'chrt' which changes the
-priority of the task.
+That is the longest latency it takes for something to happen,
+and not the average. We can have a very fast scheduler that may
+only have a large latency once in a while, but that would not
+work well with Real-Time tasks.  The wakeup tracer was designed
+to record the worst case wakeups of RT tasks. Non-RT tasks are
+not recorded because the tracer only records one worst case and
+tracing non-RT tasks that are unpredictable will overwrite the
+worst case latency of RT tasks.
+
+Since this tracer only deals with RT tasks, we will run this
+slightly differently than we did with the previous tracers.
+Instead of performing an 'ls', we will run 'sleep 1' under
+'chrt' which changes the priority of the task.
 
  # echo wakeup > /debug/tracing/current_tracer
  # echo 0 > /debug/tracing/tracing_max_latency
@@ -934,17 +1018,16 @@ wakeup latency trace v1.1.5 on 2.6.26-rc8
   <idle>-0     1d..4    4us : schedule (cpu_idle)
 
 
+Running this on an idle system, we see that it only took 4
+microseconds to perform the task switch.  Note, since the trace
+marker in the schedule is before the actual "switch", we stop
+the tracing when the recorded task is about to schedule in. This
+may change if we add a new marker at the end of the scheduler.
 
-Running this on an idle system, we see that it only took 4 microseconds
-to perform the task switch.  Note, since the trace marker in the
-schedule is before the actual "switch", we stop the tracing when
-the recorded task is about to schedule in. This may change if
-we add a new marker at the end of the scheduler.
-
-Notice that the recorded task is 'sleep' with the PID of 4901 and it
-has an rt_prio of 5. This priority is user-space priority and not
-the internal kernel priority. The policy is 1 for SCHED_FIFO and 2
-for SCHED_RR.
+Notice that the recorded task is 'sleep' with the PID of 4901
+and it has an rt_prio of 5. This priority is user-space priority
+and not the internal kernel priority. The policy is 1 for
+SCHED_FIFO and 2 for SCHED_RR.
 
 Doing the same with chrt -r 5 and ftrace_enabled set.
 
@@ -1001,24 +1084,25 @@ ksoftirq-7     1d..6   49us : _spin_unlock (tracing_record_cmdline)
 ksoftirq-7     1d..6   49us : sub_preempt_count (_spin_unlock)
 ksoftirq-7     1d..4   50us : schedule (__cond_resched)
 
-The interrupt went off while running ksoftirqd. This task runs at
-SCHED_OTHER. Why did not we see the 'N' set early? This may be
-a harmless bug with x86_32 and 4K stacks. On x86_32 with 4K stacks
-configured, the interrupt and softirq run with their own stack.
-Some information is held on the top of the task's stack (need_resched
-and preempt_count are both stored there). The setting of the NEED_RESCHED
-bit is done directly to the task's stack, but the reading of the
-NEED_RESCHED is done by looking at the current stack, which in this case
-is the stack for the hard interrupt. This hides the fact that NEED_RESCHED
-has been set. We do not see the 'N' until we switch back to the task's
+The interrupt went off while running ksoftirqd. This task runs
+at SCHED_OTHER. Why did not we see the 'N' set early? This may
+be a harmless bug with x86_32 and 4K stacks. On x86_32 with 4K
+stacks configured, the interrupt and softirq run with their own
+stack. Some information is held on the top of the task's stack
+(need_resched and preempt_count are both stored there). The
+setting of the NEED_RESCHED bit is done directly to the task's
+stack, but the reading of the NEED_RESCHED is done by looking at
+the current stack, which in this case is the stack for the hard
+interrupt. This hides the fact that NEED_RESCHED has been set.
+We do not see the 'N' until we switch back to the task's
 assigned stack.
 
 function
 --------
 
 This tracer is the function tracer. Enabling the function tracer
-can be done from the debug file system. Make sure the ftrace_enabled is
-set; otherwise this tracer is a nop.
+can be done from the debug file system. Make sure the
+ftrace_enabled is set; otherwise this tracer is a nop.
 
  # sysctl kernel.ftrace_enabled=1
  # echo function > /debug/tracing/current_tracer
@@ -1048,14 +1132,15 @@ set; otherwise this tracer is a nop.
 [...]
 
 
-Note: function tracer uses ring buffers to store the above entries.
-The newest data may overwrite the oldest data. Sometimes using echo to
-stop the trace is not sufficient because the tracing could have overwritten
-the data that you wanted to record. For this reason, it is sometimes better to
-disable tracing directly from a program. This allows you to stop the
-tracing at the point that you hit the part that you are interested in.
-To disable the tracing directly from a C program, something like following
-code snippet can be used:
+Note: function tracer uses ring buffers to store the above
+entries. The newest data may overwrite the oldest data.
+Sometimes using echo to stop the trace is not sufficient because
+the tracing could have overwritten the data that you wanted to
+record. For this reason, it is sometimes better to disable
+tracing directly from a program. This allows you to stop the
+tracing at the point that you hit the part that you are
+interested in. To disable the tracing directly from a C program,
+something like following code snippet can be used:
 
 int trace_fd;
 [...]
@@ -1070,10 +1155,10 @@ int main(int argc, char *argv[]) {
 }
 
 Note: Here we hard coded the path name. The debugfs mount is not
-guaranteed to be at /debug (and is more commonly at /sys/kernel/debug).
-For simple one time traces, the above is sufficent. For anything else,
-a search through /proc/mounts may be needed to find where the debugfs
-file-system is mounted.
+guaranteed to be at /debug (and is more commonly at
+/sys/kernel/debug). For simple one time traces, the above is
+sufficent. For anything else, a search through /proc/mounts may
+be needed to find where the debugfs file-system is mounted.
 
 
 Single thread tracing
@@ -1152,49 +1237,297 @@ int main (int argc, char **argv)
         return 0;
 }
 
+
+hw-branch-tracer (x86 only)
+---------------------------
+
+This tracer uses the x86 last branch tracing hardware feature to
+collect a branch trace on all cpus with relatively low overhead.
+
+The tracer uses a fixed-size circular buffer per cpu and only
+traces ring 0 branches. The trace file dumps that buffer in the
+following format:
+
+# tracer: hw-branch-tracer
+#
+# CPU#        TO  <-  FROM
+   0  scheduler_tick+0xb5/0x1bf          <-  task_tick_idle+0x5/0x6
+   2  run_posix_cpu_timers+0x2b/0x72a    <-  run_posix_cpu_timers+0x25/0x72a
+   0  scheduler_tick+0x139/0x1bf         <-  scheduler_tick+0xed/0x1bf
+   0  scheduler_tick+0x17c/0x1bf         <-  scheduler_tick+0x148/0x1bf
+   2  run_posix_cpu_timers+0x9e/0x72a    <-  run_posix_cpu_timers+0x5e/0x72a
+   0  scheduler_tick+0x1b6/0x1bf         <-  scheduler_tick+0x1aa/0x1bf
+
+
+The tracer may be used to dump the trace for the oops'ing cpu on
+a kernel oops into the system log. To enable this,
+ftrace_dump_on_oops must be set. To set ftrace_dump_on_oops, one
+can either use the sysctl function or set it via the proc system
+interface.
+
+  sysctl kernel.ftrace_dump_on_oops=1
+
+or
+
+  echo 1 > /proc/sys/kernel/ftrace_dump_on_oops
+
+
+Here's an example of such a dump after a null pointer
+dereference in a kernel module:
+
+[57848.105921] BUG: unable to handle kernel NULL pointer dereference at 0000000000000000
+[57848.106019] IP: [<ffffffffa0000006>] open+0x6/0x14 [oops]
+[57848.106019] PGD 2354e9067 PUD 2375e7067 PMD 0
+[57848.106019] Oops: 0002 [#1] SMP
+[57848.106019] last sysfs file: /sys/devices/pci0000:00/0000:00:1e.0/0000:20:05.0/local_cpus
+[57848.106019] Dumping ftrace buffer:
+[57848.106019] ---------------------------------
+[...]
+[57848.106019]    0  chrdev_open+0xe6/0x165      <-  cdev_put+0x23/0x24
+[57848.106019]    0  chrdev_open+0x117/0x165     <-  chrdev_open+0xfa/0x165
+[57848.106019]    0  chrdev_open+0x120/0x165     <-  chrdev_open+0x11c/0x165
+[57848.106019]    0  chrdev_open+0x134/0x165     <-  chrdev_open+0x12b/0x165
+[57848.106019]    0  open+0x0/0x14 [oops]        <-  chrdev_open+0x144/0x165
+[57848.106019]    0  page_fault+0x0/0x30         <-  open+0x6/0x14 [oops]
+[57848.106019]    0  error_entry+0x0/0x5b        <-  page_fault+0x4/0x30
+[57848.106019]    0  error_kernelspace+0x0/0x31          <-  error_entry+0x59/0x5b
+[57848.106019]    0  error_sti+0x0/0x1   <-  error_kernelspace+0x2d/0x31
+[57848.106019]    0  page_fault+0x9/0x30         <-  error_sti+0x0/0x1
+[57848.106019]    0  do_page_fault+0x0/0x881     <-  page_fault+0x1a/0x30
+[...]
+[57848.106019]    0  do_page_fault+0x66b/0x881   <-  is_prefetch+0x1ee/0x1f2
+[57848.106019]    0  do_page_fault+0x6e0/0x881   <-  do_page_fault+0x67a/0x881
+[57848.106019]    0  oops_begin+0x0/0x96         <-  do_page_fault+0x6e0/0x881
+[57848.106019]    0  trace_hw_branch_oops+0x0/0x2d       <-  oops_begin+0x9/0x96
+[...]
+[57848.106019]    0  ds_suspend_bts+0x2a/0xe3    <-  ds_suspend_bts+0x1a/0xe3
+[57848.106019] ---------------------------------
+[57848.106019] CPU 0
+[57848.106019] Modules linked in: oops
+[57848.106019] Pid: 5542, comm: cat Tainted: G        W  2.6.28 #23
+[57848.106019] RIP: 0010:[<ffffffffa0000006>]  [<ffffffffa0000006>] open+0x6/0x14 [oops]
+[57848.106019] RSP: 0018:ffff880235457d48  EFLAGS: 00010246
+[...]
+
+
+function graph tracer
+---------------------------
+
+This tracer is similar to the function tracer except that it
+probes a function on its entry and its exit. This is done by
+using a dynamically allocated stack of return addresses in each
+task_struct. On function entry the tracer overwrites the return
+address of each function traced to set a custom probe. Thus the
+original return address is stored on the stack of return address
+in the task_struct.
+
+Probing on both ends of a function leads to special features
+such as:
+
+- measure of a function's time execution
+- having a reliable call stack to draw function calls graph
+
+This tracer is useful in several situations:
+
+- you want to find the reason of a strange kernel behavior and
+  need to see what happens in detail on any areas (or specific
+  ones).
+
+- you are experiencing weird latencies but it's difficult to
+  find its origin.
+
+- you want to find quickly which path is taken by a specific
+  function
+
+- you just want to peek inside a working kernel and want to see
+  what happens there.
+
+# tracer: function_graph
+#
+# CPU  DURATION                  FUNCTION CALLS
+# |     |   |                     |   |   |   |
+
+ 0)               |  sys_open() {
+ 0)               |    do_sys_open() {
+ 0)               |      getname() {
+ 0)               |        kmem_cache_alloc() {
+ 0)   1.382 us    |          __might_sleep();
+ 0)   2.478 us    |        }
+ 0)               |        strncpy_from_user() {
+ 0)               |          might_fault() {
+ 0)   1.389 us    |            __might_sleep();
+ 0)   2.553 us    |          }
+ 0)   3.807 us    |        }
+ 0)   7.876 us    |      }
+ 0)               |      alloc_fd() {
+ 0)   0.668 us    |        _spin_lock();
+ 0)   0.570 us    |        expand_files();
+ 0)   0.586 us    |        _spin_unlock();
+
+
+There are several columns that can be dynamically
+enabled/disabled. You can use every combination of options you
+want, depending on your needs.
+
+- The cpu number on which the function executed is default
+  enabled.  It is sometimes better to only trace one cpu (see
+  tracing_cpu_mask file) or you might sometimes see unordered
+  function calls while cpu tracing switch.
+
+       hide: echo nofuncgraph-cpu > /debug/tracing/trace_options
+       show: echo funcgraph-cpu > /debug/tracing/trace_options
+
+- The duration (function's time of execution) is displayed on
+  the closing bracket line of a function or on the same line
+  than the current function in case of a leaf one. It is default
+  enabled.
+
+       hide: echo nofuncgraph-duration > /debug/tracing/trace_options
+       show: echo funcgraph-duration > /debug/tracing/trace_options
+
+- The overhead field precedes the duration field in case of
+  reached duration thresholds.
+
+       hide: echo nofuncgraph-overhead > /debug/tracing/trace_options
+       show: echo funcgraph-overhead > /debug/tracing/trace_options
+       depends on: funcgraph-duration
+
+  ie:
+
+  0)               |    up_write() {
+  0)   0.646 us    |      _spin_lock_irqsave();
+  0)   0.684 us    |      _spin_unlock_irqrestore();
+  0)   3.123 us    |    }
+  0)   0.548 us    |    fput();
+  0) + 58.628 us   |  }
+
+  [...]
+
+  0)               |      putname() {
+  0)               |        kmem_cache_free() {
+  0)   0.518 us    |          __phys_addr();
+  0)   1.757 us    |        }
+  0)   2.861 us    |      }
+  0) ! 115.305 us  |    }
+  0) ! 116.402 us  |  }
+
+  + means that the function exceeded 10 usecs.
+  ! means that the function exceeded 100 usecs.
+
+
+- The task/pid field displays the thread cmdline and pid which
+  executed the function. It is default disabled.
+
+       hide: echo nofuncgraph-proc > /debug/tracing/trace_options
+       show: echo funcgraph-proc > /debug/tracing/trace_options
+
+  ie:
+
+  # tracer: function_graph
+  #
+  # CPU  TASK/PID        DURATION                  FUNCTION CALLS
+  # |    |    |           |   |                     |   |   |   |
+  0)    sh-4802     |               |                  d_free() {
+  0)    sh-4802     |               |                    call_rcu() {
+  0)    sh-4802     |               |                      __call_rcu() {
+  0)    sh-4802     |   0.616 us    |                        rcu_process_gp_end();
+  0)    sh-4802     |   0.586 us    |                        check_for_new_grace_period();
+  0)    sh-4802     |   2.899 us    |                      }
+  0)    sh-4802     |   4.040 us    |                    }
+  0)    sh-4802     |   5.151 us    |                  }
+  0)    sh-4802     | + 49.370 us   |                }
+
+
+- The absolute time field is an absolute timestamp given by the
+  system clock since it started. A snapshot of this time is
+  given on each entry/exit of functions
+
+       hide: echo nofuncgraph-abstime > /debug/tracing/trace_options
+       show: echo funcgraph-abstime > /debug/tracing/trace_options
+
+  ie:
+
+  #
+  #      TIME       CPU  DURATION                  FUNCTION CALLS
+  #       |         |     |   |                     |   |   |   |
+  360.774522 |   1)   0.541 us    |                                          }
+  360.774522 |   1)   4.663 us    |                                        }
+  360.774523 |   1)   0.541 us    |                                        __wake_up_bit();
+  360.774524 |   1)   6.796 us    |                                      }
+  360.774524 |   1)   7.952 us    |                                    }
+  360.774525 |   1)   9.063 us    |                                  }
+  360.774525 |   1)   0.615 us    |                                  journal_mark_dirty();
+  360.774527 |   1)   0.578 us    |                                  __brelse();
+  360.774528 |   1)               |                                  reiserfs_prepare_for_journal() {
+  360.774528 |   1)               |                                    unlock_buffer() {
+  360.774529 |   1)               |                                      wake_up_bit() {
+  360.774529 |   1)               |                                        bit_waitqueue() {
+  360.774530 |   1)   0.594 us    |                                          __phys_addr();
+
+
+You can put some comments on specific functions by using
+trace_printk() For example, if you want to put a comment inside
+the __might_sleep() function, you just have to include
+<linux/ftrace.h> and call trace_printk() inside __might_sleep()
+
+trace_printk("I'm a comment!\n")
+
+will produce:
+
+ 1)               |             __might_sleep() {
+ 1)               |                /* I'm a comment! */
+ 1)   1.449 us    |             }
+
+
+You might find other useful features for this tracer in the
+following "dynamic ftrace" section such as tracing only specific
+functions or tasks.
+
 dynamic ftrace
 --------------
 
 If CONFIG_DYNAMIC_FTRACE is set, the system will run with
 virtually no overhead when function tracing is disabled. The way
 this works is the mcount function call (placed at the start of
-every kernel function, produced by the -pg switch in gcc), starts
-of pointing to a simple return. (Enabling FTRACE will include the
--pg switch in the compiling of the kernel.)
+every kernel function, produced by the -pg switch in gcc),
+starts of pointing to a simple return. (Enabling FTRACE will
+include the -pg switch in the compiling of the kernel.)
 
 At compile time every C file object is run through the
 recordmcount.pl script (located in the scripts directory). This
 script will process the C object using objdump to find all the
-locations in the .text section that call mcount. (Note, only
-the .text section is processed, since processing other sections
-like .init.text may cause races due to those sections being freed).
+locations in the .text section that call mcount. (Note, only the
+.text section is processed, since processing other sections like
+.init.text may cause races due to those sections being freed).
 
-A new section called "__mcount_loc" is created that holds references
-to all the mcount call sites in the .text section. This section is
-compiled back into the original object. The final linker will add
-all these references into a single table.
+A new section called "__mcount_loc" is created that holds
+references to all the mcount call sites in the .text section.
+This section is compiled back into the original object. The
+final linker will add all these references into a single table.
 
 On boot up, before SMP is initialized, the dynamic ftrace code
-scans this table and updates all the locations into nops. It also
-records the locations, which are added to the available_filter_functions
-list.  Modules are processed as they are loaded and before they are
-executed.  When a module is unloaded, it also removes its functions from
-the ftrace function list. This is automatic in the module unload
-code, and the module author does not need to worry about it.
-
-When tracing is enabled, kstop_machine is called to prevent races
-with the CPUS executing code being modified (which can cause the
-CPU to do undesireable things), and the nops are patched back
-to calls. But this time, they do not call mcount (which is just
-a function stub). They now call into the ftrace infrastructure.
+scans this table and updates all the locations into nops. It
+also records the locations, which are added to the
+available_filter_functions list.  Modules are processed as they
+are loaded and before they are executed.  When a module is
+unloaded, it also removes its functions from the ftrace function
+list. This is automatic in the module unload code, and the
+module author does not need to worry about it.
+
+When tracing is enabled, kstop_machine is called to prevent
+races with the CPUS executing code being modified (which can
+cause the CPU to do undesireable things), and the nops are
+patched back to calls. But this time, they do not call mcount
+(which is just a function stub). They now call into the ftrace
+infrastructure.
 
 One special side-effect to the recording of the functions being
 traced is that we can now selectively choose which functions we
-wish to trace and which ones we want the mcount calls to remain as
-nops.
+wish to trace and which ones we want the mcount calls to remain
+as nops.
 
-Two files are used, one for enabling and one for disabling the tracing
-of specified functions. They are:
+Two files are used, one for enabling and one for disabling the
+tracing of specified functions. They are:
 
   set_ftrace_filter
 
@@ -1202,8 +1535,8 @@ and
 
   set_ftrace_notrace
 
-A list of available functions that you can add to these files is listed
-in:
+A list of available functions that you can add to these files is
+listed in:
 
    available_filter_functions
 
@@ -1240,8 +1573,8 @@ hrtimer_interrupt
 sys_nanosleep
 
 
-Perhaps this is not enough. The filters also allow simple wild cards.
-Only the following are currently available
+Perhaps this is not enough. The filters also allow simple wild
+cards. Only the following are currently available
 
   <match>*  - will match functions that begin with <match>
   *<match>  - will match functions that end with <match>
@@ -1251,9 +1584,9 @@ These are the only wild cards which are supported.
 
   <match>*<match> will not work.
 
-Note: It is better to use quotes to enclose the wild cards, otherwise
-  the shell may expand the parameters into names of files in the local
-  directory.
+Note: It is better to use quotes to enclose the wild cards,
+      otherwise the shell may expand the parameters into names
+      of files in the local directory.
 
  # echo 'hrtimer_*' > /debug/tracing/set_ftrace_filter
 
@@ -1299,7 +1632,8 @@ This is because the '>' and '>>' act just like they do in bash.
 To rewrite the filters, use '>'
 To append to the filters, use '>>'
 
-To clear out a filter so that all functions will be recorded again:
+To clear out a filter so that all functions will be recorded
+again:
 
  # echo > /debug/tracing/set_ftrace_filter
  # cat /debug/tracing/set_ftrace_filter
@@ -1331,7 +1665,8 @@ hrtimer_get_res
 hrtimer_init_sleeper
 
 
-The set_ftrace_notrace prevents those functions from being traced.
+The set_ftrace_notrace prevents those functions from being
+traced.
 
  # echo '*preempt*' '*lock*' > /debug/tracing/set_ftrace_notrace
 
@@ -1353,13 +1688,75 @@ Produces:
 
 We can see that there's no more lock or preempt tracing.
 
+
+Dynamic ftrace with the function graph tracer
+---------------------------------------------
+
+Although what has been explained above concerns both the
+function tracer and the function-graph-tracer, there are some
+special features only available in the function-graph tracer.
+
+If you want to trace only one function and all of its children,
+you just have to echo its name into set_graph_function:
+
+ echo __do_fault > set_graph_function
+
+will produce the following "expanded" trace of the __do_fault()
+function:
+
+ 0)               |  __do_fault() {
+ 0)               |    filemap_fault() {
+ 0)               |      find_lock_page() {
+ 0)   0.804 us    |        find_get_page();
+ 0)               |        __might_sleep() {
+ 0)   1.329 us    |        }
+ 0)   3.904 us    |      }
+ 0)   4.979 us    |    }
+ 0)   0.653 us    |    _spin_lock();
+ 0)   0.578 us    |    page_add_file_rmap();
+ 0)   0.525 us    |    native_set_pte_at();
+ 0)   0.585 us    |    _spin_unlock();
+ 0)               |    unlock_page() {
+ 0)   0.541 us    |      page_waitqueue();
+ 0)   0.639 us    |      __wake_up_bit();
+ 0)   2.786 us    |    }
+ 0) + 14.237 us   |  }
+ 0)               |  __do_fault() {
+ 0)               |    filemap_fault() {
+ 0)               |      find_lock_page() {
+ 0)   0.698 us    |        find_get_page();
+ 0)               |        __might_sleep() {
+ 0)   1.412 us    |        }
+ 0)   3.950 us    |      }
+ 0)   5.098 us    |    }
+ 0)   0.631 us    |    _spin_lock();
+ 0)   0.571 us    |    page_add_file_rmap();
+ 0)   0.526 us    |    native_set_pte_at();
+ 0)   0.586 us    |    _spin_unlock();
+ 0)               |    unlock_page() {
+ 0)   0.533 us    |      page_waitqueue();
+ 0)   0.638 us    |      __wake_up_bit();
+ 0)   2.793 us    |    }
+ 0) + 14.012 us   |  }
+
+You can also expand several functions at once:
+
+ echo sys_open > set_graph_function
+ echo sys_close >> set_graph_function
+
+Now if you want to go back to trace all functions you can clear
+this special filter via:
+
+ echo > set_graph_function
+
+
 trace_pipe
 ----------
 
-The trace_pipe outputs the same content as the trace file, but the effect
-on the tracing is different. Every read from trace_pipe is consumed.
-This means that subsequent reads will be different. The trace
-is live.
+The trace_pipe outputs the same content as the trace file, but
+the effect on the tracing is different. Every read from
+trace_pipe is consumed. This means that subsequent reads will be
+different. The trace is live.
 
  # echo function > /debug/tracing/current_tracer
  # cat /debug/tracing/trace_pipe > /tmp/trace.out &
@@ -1387,38 +1784,45 @@ is live.
             bash-4043  [00] 41.267111: select_task_rq_rt <-try_to_wake_up
 
 
-Note, reading the trac