For the short answer, no, I'd like not to extend PTRACE_SET_DEBUGREG in
the simple fashion. The direction I want to move with this is away from
providing the hardware register formats directly as the user ABI.
What I mean is resurrecting, finishing, and porting the "hw_breakpoint"
work that Alan
It looks like when Anton added the PTRACE_GET_DEBUGREG/
PTRACE_SET_DEBUGREG he envisioned future chips having more than one
IABR/DABR.
I'm wondering what the feeling is about using the commands for
handling some of the sub-arch variants we have:
e300 (603 style machine) - adds IABR2, DABR2
