Re: [PATCH 2/3] skip_prolgoue (amd64)

Yao Qi
2013-12-09T13:58:11Z

On 12/09/2013 09:13 PM, Pedro Alves wrote:
> We can have more stops than resumes.
>
> #1 - resume everything (1000 threads)
> #2 - event in one thread triggers, we call target_wait
> #3 - gdb decides to leave thread stopped.
> #4 - one hour passes, while threads poke at memory.
> #5 - another event triggers, and we call target_wait again
>
> No resume happened between #2 and #5.

Thanks for the explanation. IIUC, #2, #3, and #5 are the result of
handle_inferior_event, where cache is flushed (with my patch applied).

"wait -> handle event -> wait" is like a loop or circle to me, and we
can flush at any point(s) of this circle, depending on what heuristic
we are using.

--
Yao (é½å°§)