517b731477
This adds new debug feature information so that the DAWR can be identified by userspace tools like GDB. Unfortunately the DAWR doesn't sit nicely into the current description that ptrace provides to userspace via struct ppc_debug_info. It doesn't allow for specifying that only some ranges are possible or even the end alignment constraints (DAWR only allows 512 byte wide ranges which can't cross a 512 byte boundary). After talking to Edjunior Machado (GDB ppc developer), it was decided this was the best approach. Just mark it as debug feature DAWR and tools like GDB can internally decide the constraints. Signed-off-by: Michael Neuling <mikey@neuling.org> Signed-off-by: Michael Ellerman <michael@ellerman.id.au> |
||
|---|---|---|
| .. | ||
| 00-INDEX | ||
| bootwrapper.txt | ||
| cpu_features.txt | ||
| eeh-pci-error-recovery.txt | ||
| firmware-assisted-dump.txt | ||
| hvcs.txt | ||
| kvm_440.txt | ||
| mpc52xx.txt | ||
| ptrace.txt | ||
| qe_firmware.txt | ||
| transactional_memory.txt | ||