Re: [Openocd-development] [PATCH] process reset - keep alive - necessary evil?

[Duane E. <op...@du...>]

Øyvind Harboe wrote:

> - Having given it some thought, I would like to make it the C code's
> responsibility to invoke keep_alive and target_call_timer_callbacks_now() Is there any
> reason we can't do this? Really in a perfect world(or ultimately w/OpenOCD),
> keep_alive & target_call_timer_callbacks_now() would go away. I've also
> formulated a patch that makes keep_alive() invokoe
> target_call_tiemr_callbacks_now().
>   
What C code?  Where?

Which C functions should and should not invoke "keep alive"?

How do we decide _this_one_ needs it - and _that_one_ does not?

And - do we start renaming functions so that they describe their 
complete function by tacking "_and_calls_keep_alive" on the function name?

As we discussed - the goal was - to translate the target_process_reset() 
into TCL - and periodically - something in the TCL may have to 'help a 
little bit'

Today - we have no idea what somebody might need to do in an event proc, 
or during the reset process.

Today - openocd does not use "pthreads()" and I don't want to even go 
near that.

Thus - "keep_alive" might well be an evil we must live with :-(

-Duane.