aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorSeongJae Park <sj38.park@gmail.com>2024-03-03 11:35:58 -0800
committerSeongJae Park <sj38.park@gmail.com>2024-03-03 11:35:58 -0800
commit20bb0275d61fdad743cd316de099b6d7f44685e6 (patch)
tree15e4658ef22443692ff8e7598f2a6e7c035b1911
parent3cea69177559974ba7e9f26d3476dbf3e6ea8747 (diff)
downloaddamo-20bb0275d61fdad743cd316de099b6d7f44685e6.tar.gz
USAGE: Add --sz_snapshot on 'damo report profile' example
Signed-off-by: SeongJae Park <sj38.park@gmail.com>
-rw-r--r--USAGE.md8
1 files changed, 5 insertions, 3 deletions
diff --git a/USAGE.md b/USAGE.md
index a5aade1f..52e67f94 100644
--- a/USAGE.md
+++ b/USAGE.md
@@ -637,11 +637,13 @@ access pattern happened, collect profiling information for the time ranges, and
generate the report with the filtered information.
For example, below shows what was consuming CPU while 50% or more rate of
-access to 50 MiB size address range starting from `139,798,348,038,144`
-happened.
+access was made towards 50 MiB size address range starting from
+`139,798,348,038,144`, and the total size of the memory regions that got the
+access in the address range was 40 or more MiB.
$ sudo ./damo report profile --access_rate 50% 100% \
- --address 139798348038144 $((139798348038144 + 50 * 1024 * 1024))
+ --address 139798348038144 $((139798348038144 + 50 * 1024 * 1024)) \
+ --sz_snapshot 40MiB max
Samples: 69K of event 'cpu-clock:pppH', Event count (approx.): 17449500000
Overhead Command Shared Object Symbol
70.32% swapper [kernel.vmlinux] [k] pv_native_safe_halt