Thread (15 messages) 15 messages, 2 authors, 2025-09-17

Re: [PATCH v4 1/8] tracing: wprobe: Add watchpoint probe event based on hardware breakpoint

From: Randy Dunlap <hidden>
Date: 2025-09-17 17:13:45
Also in: linux-doc, linux-perf-users, lkml


On 9/17/25 7:38 AM, Masami Hiramatsu (Google) wrote:
quoted
+  #           TASK-PID     CPU#  |||||  TIMESTAMP  FUNCTION
+  #              | |         |   |||||     |         |
+           <idle>-0       [000] d.Z1.  717.026259: my_jiffies: (tick_do_update_jiffies64+0xbe/0x130)
+           <idle>-0       [000] d.Z1.  717.026373: my_jiffies: (tick_do_update_jiffies64+0xbe/0x130)
+
+You can see the code which writes to `jiffies` is `do_timer()`.
I'm having trouble getting from tick_do_update_jiffies64+0xbe/0x130,
which I expect is
	jiffies_64 += ticks;
in that function, over to do_timer(), which also updates jiffies_64,
but is not called by tick_do_update_jiffies64(). AFAICT, there are
no calls to do_timer() in the file (kernel/time/tick-sched.c).

Can you explain, please?
Let me try this again.

I understand the stack (call) trace/dump and your explanation, but
then your next comment says:

+You can see the code which writes to `jiffies` is `do_timer()`.

Does that need to be corrected?

thanks.
-- 
~Randy
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help