summaryrefslogtreecommitdiffstats
path: root/include
diff options
context:
space:
mode:
authorMichael Matz2018-02-23 18:29:56 +0100
committerDavid Gibson2018-04-27 10:05:22 +0200
commita2f04333a340282c0842e76c055297cb7ba56f0f (patch)
tree7fd654c43d4e4d06249c7fde54d542d0802824d2 /include
parentuninorth: rename UNINState to UNINHostState (diff)
downloadqemu-a2f04333a340282c0842e76c055297cb7ba56f0f.tar.gz
qemu-a2f04333a340282c0842e76c055297cb7ba56f0f.tar.xz
qemu-a2f04333a340282c0842e76c055297cb7ba56f0f.zip
ppc: Fix size of ppc64 xer register
The normal gdb definition of the XER registers is only 32 bit, and that's what the current version of power64-core.xml also says (seems copied from gdb's). But qemu's idea of the XER register is target_ulong (in CPUPPCState, ppc_gdb_register_len and ppc_cpu_gdb_read_register) That mismatch leads to the following message when attaching with gdb: Truncated register 32 in remote 'g' packet (and following on that qemu stops responding). The simple fix is to say the truth in the .xml file. But the better fix is to actually make it 32bit on the wire, as old gdbs don't support XML files for describing registers. Also the XER state in qemu doesn't seem to use the high 32 bits, so sending it off to gdb doesn't seem worthwhile. Signed-off-by: Michael Matz <matz@suse.de> Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Diffstat (limited to 'include')
0 files changed, 0 insertions, 0 deletions