No description
  • C 98.2%
  • Assembly 1%
  • Makefile 0.3%
  • Shell 0.2%
  • Python 0.1%
Find a file
Repository files (latest commit first)
Filename Latest commit message Latest commit date
Steven Rostedt (VMware) 8e5e19c1b9 selftests: ftrace: Add a way to reset triggers in the set_ftrace_filter file
Just writing into the set_ftrace_filter file does not reset triggers, even
though it can reset the function list. Triggers require writing the trigger
name with a "!" prepended. It's worse that it requires the number if the
trigger has a count associated to it.

Add a reset_ftrace_filter function to the ftrace self tests to allow for the
tests to have a generic way to clear them. It also resets any functions that
are listed in that file as well.

Signed-off-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
2017-04-18 13:48:25 -04:00
arch ftrace/x86: Do no run CPU sync when there is only one CPU online 2017-03-28 12:35:16 -04:00
block
certs
crypto
Documentation tracing/kprobes: expose maxactive for kretprobe in kprobe_events 2017-04-04 10:32:03 -04:00
drivers Merge git://git.kernel.org/pub/scm/linux/kernel/git/nab/target-pending 2017-03-19 18:06:31 -07:00
firmware
fs
include tracing: Make sure rcu_irq_enter() can work for trace_*_rcuidle() trace events 2017-04-10 15:22:17 -04:00
init ftrace: Have init/main.c call ftrace directly to free init memory 2017-04-03 14:04:00 -04:00
ipc
kernel ftrace: Add 'function-fork' trace option 2017-04-17 17:13:00 -04:00
lib
mm ftrace: Have init/main.c call ftrace directly to free init memory 2017-04-03 14:04:00 -04:00
net
samples
scripts ftrace: Allow for function tracing to record init functions on boot up 2017-03-24 20:51:49 -04:00
security
sound
tools selftests: ftrace: Add a way to reset triggers in the set_ftrace_filter file 2017-04-18 13:48:25 -04:00
usr
virt
.cocciconfig
.get_maintainer.ignore
.gitattributes
.gitignore
.mailmap
COPYING
CREDITS
Kbuild
Kconfig
MAINTAINERS
Makefile Linux 4.11-rc3 2017-03-19 19:09:39 -07:00
README

Linux kernel
============

This file was moved to Documentation/admin-guide/README.rst

Please notice that there are several guides for kernel developers and users.
These guides can be rendered in a number of formats, like HTML and PDF.

In order to build the documentation, use ``make htmldocs`` or
``make pdfdocs``.

There are various text files in the Documentation/ subdirectory,
several of them using the Restructured Text markup notation.
See Documentation/00-INDEX for a list of what is contained in each file.

Please read the Documentation/process/changes.rst file, as it contains the
requirements for building and running the kernel, and information about
the problems which may result by upgrading your kernel.