On Tue, Nov 20, 2007 at 08:29:19PM -0800, Roland McGrath wrote:
> Here are the steps I have in mind.  I think this work should be pretty well
> clear to merge upstream without much controversy.  Basically, this is the
> arch parts now done in the tracehook and regset patches, with a little
> sugar.  Several of these steps can be done in parallel and merged upstream
> independently.

Thanks for kicking this off and the detailed mail.

<snip>
 
> 1. asm/tracehook.h functions, i.e. single_step et al.

<snip>
 
>    #1 depends on nothing else.
> 
> 2. arch regset functions, and define task_user_regset_view (new name for
>    utrace_native_view).  This is in the utrace-regset patch for your arch
>    now.  How to organize this for upstream submission will depend on the
>    details of the code for your arch and what your arch maintainers want.

<snip>

>    #2 depends on nothing else but the generic patch adding linux/regset.h
> 
> 3. Use regset functions for core dump.

<snip>
 
>    #3 depends on #2
> 
> 4. Use regset functions for ptrace.

<snip>
> 
>    #4 depends on #2 and the generic patches providing the ptrace_layout 
> helpers
> 
> 5. arch cruft removal.

<snip>

At what step do you envisage the core utrace bits (engine, etc), be
merged? From a pure utrace client (!ptrace) perspective, it'd be
important to be able to do things as attach an engine, quiesce a thread
and the like.

<snip>

> I will get started on the groundwork patches and do x86 to set the
> example.  I think I can get this going in the next few days (next few
> business days anyway, not sure about the holiday weekend right now).

Looking forward to this...

Thanks,
Ananth

Reply via email to