Kumar Gala writes: > global_dbcr0 needs to be a per cpu set of save areas instead of a single > global on all processors.
Looks reasonable. At some point you might want to use a per-cpu variable instead of an array in order to reduce cacheline bouncing. > Also, we switch to using DBCR0_IDM to determine if the user space app is > being debugged as its a more consistent way. In the future we should > support features like hardware breakpoint and watchpoints which will > have DBCR0_IDM set but not necessarily DBCR0_IC (single step). That should be OK. Paul. _______________________________________________ Linuxppc-dev mailing list Linuxppc-dev@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-dev
