Delete duplicate words from kernel docs

I have deleted duplicate words like

to, guest, trace, when, we

Signed-off-by: Akhil Raj <lf32.dev@gmail.com>
Link: https://lore.kernel.org/r/20220829065239.4531-1-lf32.dev@gmail.com
Signed-off-by: Jonathan Corbet <corbet@lwn.net>
This commit is contained in:
Akhil Raj 2022-08-29 12:22:39 +05:30 committed by Jonathan Corbet
parent 32a3a9db16
commit 7f77ebbf75
6 changed files with 6 additions and 6 deletions

View File

@ -477,6 +477,6 @@ over a rather long period of time, but improvements are always welcome!
So if you need to wait for both an RCU grace period and for So if you need to wait for both an RCU grace period and for
all pre-existing call_rcu() callbacks, you will need to execute all pre-existing call_rcu() callbacks, you will need to execute
both rcu_barrier() and synchronize_rcu(), if necessary, using both rcu_barrier() and synchronize_rcu(), if necessary, using
something like workqueues to to execute them concurrently. something like workqueues to execute them concurrently.
See rcubarrier.rst for more information. See rcubarrier.rst for more information.

View File

@ -61,7 +61,7 @@ checking of rcu_dereference() primitives:
rcu_access_pointer(p): rcu_access_pointer(p):
Return the value of the pointer and omit all barriers, Return the value of the pointer and omit all barriers,
but retain the compiler constraints that prevent duplicating but retain the compiler constraints that prevent duplicating
or coalescsing. This is useful when when testing the or coalescsing. This is useful when testing the
value of the pointer itself, for example, against NULL. value of the pointer itself, for example, against NULL.
The rcu_dereference_check() check expression can be any boolean The rcu_dereference_check() check expression can be any boolean

View File

@ -133,7 +133,7 @@ code field of ``BPF_END``.
The byte swap instructions operate on the destination register The byte swap instructions operate on the destination register
only and do not use a separate source register or immediate value. only and do not use a separate source register or immediate value.
The 1-bit source operand field in the opcode is used to to select what byte The 1-bit source operand field in the opcode is used to select what byte
order the operation convert from or to: order the operation convert from or to:
========= ===== ================================================= ========= ===== =================================================

View File

@ -412,7 +412,7 @@ Extended error information
Because the default sort key above is 'hitcount', the above shows a Because the default sort key above is 'hitcount', the above shows a
the list of call_sites by increasing hitcount, so that at the bottom the list of call_sites by increasing hitcount, so that at the bottom
we see the functions that made the most kmalloc calls during the we see the functions that made the most kmalloc calls during the
run. If instead we we wanted to see the top kmalloc callers in run. If instead we wanted to see the top kmalloc callers in
terms of the number of bytes requested rather than the number of terms of the number of bytes requested rather than the number of
calls, and we wanted the top caller to appear at the top, we can use calls, and we wanted the top caller to appear at the top, we can use
the 'sort' parameter, along with the 'descending' modifier:: the 'sort' parameter, along with the 'descending' modifier::

View File

@ -20,7 +20,7 @@ For example::
[root@f32 ~]# cd /sys/kernel/tracing/ [root@f32 ~]# cd /sys/kernel/tracing/
[root@f32 tracing]# echo timerlat > current_tracer [root@f32 tracing]# echo timerlat > current_tracer
It is possible to follow the trace by reading the trace trace file:: It is possible to follow the trace by reading the trace file::
[root@f32 tracing]# cat trace [root@f32 tracing]# cat trace
# tracer: timerlat # tracer: timerlat

View File

@ -377,7 +377,7 @@ Emulating cr0.wp
================ ================
If tdp is not enabled, the host must keep cr0.wp=1 so page write protection If tdp is not enabled, the host must keep cr0.wp=1 so page write protection
works for the guest kernel, not guest guest userspace. When the guest works for the guest kernel, not guest userspace. When the guest
cr0.wp=1, this does not present a problem. However when the guest cr0.wp=0, cr0.wp=1, this does not present a problem. However when the guest cr0.wp=0,
we cannot map the permissions for gpte.u=1, gpte.w=0 to any spte (the we cannot map the permissions for gpte.u=1, gpte.w=0 to any spte (the
semantics require allowing any guest kernel access plus user read access). semantics require allowing any guest kernel access plus user read access).