diff options
| author | Andrew Kreimer <algonell@gmail.com> | 2024-12-09 15:06:00 +0200 |
|---|---|---|
| committer | Jonathan Corbet <corbet@lwn.net> | 2024-12-13 08:42:23 -0700 |
| commit | 09cbeb5b301585343985e3b60d41425ff45d5961 (patch) | |
| tree | b11b942ce92e48e58ba849472d43cd5e896cf80f /Documentation/trace | |
| parent | bbf5254a5ab18b5a17e0c11a91a42d50a92bb5e1 (diff) | |
| download | linux-next-09cbeb5b301585343985e3b60d41425ff45d5961.tar.gz linux-next-09cbeb5b301585343985e3b60d41425ff45d5961.zip | |
Documentation/rv: Fix typos
There are some typos in the documentation: 'a' -> 'at', missing 'to'.
Fix them.
Signed-off-by: Andrew Kreimer <algonell@gmail.com>
Acked-by: Steven Rostedt (Google) <rostedt@goodmis.org>
Signed-off-by: Jonathan Corbet <corbet@lwn.net>
Link: https://lore.kernel.org/r/20241209130640.10954-1-algonell@gmail.com
Diffstat (limited to 'Documentation/trace')
| -rw-r--r-- | Documentation/trace/rv/runtime-verification.rst | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/Documentation/trace/rv/runtime-verification.rst b/Documentation/trace/rv/runtime-verification.rst index dae78dfa7cdc..c700dde9259c 100644 --- a/Documentation/trace/rv/runtime-verification.rst +++ b/Documentation/trace/rv/runtime-verification.rst @@ -8,14 +8,14 @@ checking* and *theorem proving*) with a more practical approach for complex systems. Instead of relying on a fine-grained model of a system (e.g., a -re-implementation a instruction level), RV works by analyzing the trace of the +re-implementation at instruction level), RV works by analyzing the trace of the system's actual execution, comparing it against a formal specification of the system behavior. The main advantage is that RV can give precise information on the runtime behavior of the monitored system, without the pitfalls of developing models that require a re-implementation of the entire system in a modeling language. -Moreover, given an efficient monitoring method, it is possible execute an +Moreover, given an efficient monitoring method, it is possible to execute an *online* verification of a system, enabling the *reaction* for unexpected events, avoiding, for example, the propagation of a failure on safety-critical systems. |