doc: tracing: Fix a number of typos (2a1e03ca) · Commits · 戴 / test

Documentation/trace/ftrace.rst

+7 −7

Original line number	Diff line number	Diff line
		@@ -462,7 +462,7 @@ of ftrace. Here is a list of some of the key files:

		mono_raw:
		This is the raw monotonic clock (CLOCK_MONOTONIC_RAW)
		which is montonic but is not subject to any rate adjustments
		which is monotonic but is not subject to any rate adjustments
		and ticks at the same rate as the hardware clocksource.

		boot:
		@@ -914,8 +914,8 @@ The above is mostly meaningful for kernel developers.
		current trace and the next trace.

		- '$' - greater than 1 second
		- '@' - greater than 100 milisecond
		- '*' - greater than 10 milisecond
		- '@' - greater than 100 millisecond
		- '*' - greater than 10 millisecond
		- '#' - greater than 1000 microsecond
		- '!' - greater than 100 microsecond
		- '+' - greater than 10 microsecond
		@@ -2541,7 +2541,7 @@ At compile time every C file object is run through the
		recordmcount program (located in the scripts directory). This
		program will parse the ELF headers in the C object to find all
		the locations in the .text section that call mcount. Starting
		with gcc verson 4.6, the -mfentry has been added for x86, which
		with gcc version 4.6, the -mfentry has been added for x86, which
		calls "__fentry__" instead of "mcount". Which is called before
		the creation of the stack frame.

		@@ -2978,7 +2978,7 @@ The following commands are supported:
		When the function is hit, it will dump the contents of the ftrace
		ring buffer to the console. This is useful if you need to debug
		something, and want to dump the trace when a certain function
		is hit. Perhaps its a function that is called before a tripple
		is hit. Perhaps it's a function that is called before a triple
		fault happens and does not allow you to get a regular dump.

		- cpudump:

Admin message