Hello all,
Software breakpoint is a instruction which should make guest exit.
We replace guest code with software breakpoint instruction so that we can stop at anywhere we want.
In my previous guest debug patches for e500, I used instruction (sc 64) as software breakpoint.
Seem this was not good, since (sc 64) maybe defined in future.
also this instruction has uncertain effective on E.HV platform such as e500mc.
Another choice is to use trap instruction.
In order to distinguish between real guest trap and software breakpoint trap.
It's needed to trace software breakpoint addressed in kernel,
and we need to create ioctls to add/remove software point.
So guys, which way should we choose?
Or is there any other better idea?
Thanks,
Yu
ÿô.nlj·Ÿ®‰†+%ŠË±é¥Šwÿº{.nlj·¤¾oéâ^n‡r¡öë¨è&£ûz¹Þúzf£¢·hšˆ§~††Ûÿÿïÿ‘ê_èæ+v‰¨þ)ßø
