aboutsummaryrefslogtreecommitdiff
path: root/qemu-options.h
diff options
context:
space:
mode:
authorAlex Bennée <alex.bennee@linaro.org>2017-07-12 11:52:15 +0100
committerPaolo Bonzini <pbonzini@redhat.com>2017-07-14 12:04:41 +0200
commitbd88c780e6a17188f7fd676f3a056e5db21500e0 (patch)
tree388497f55af28ffb52c4ce7f21c703682136f5b6 /qemu-options.h
parentd2a6c8570b15413f43891fbb3c41521c68ef8297 (diff)
downloadqemu-bd88c780e6a17188f7fd676f3a056e5db21500e0.zip
qemu-bd88c780e6a17188f7fd676f3a056e5db21500e0.tar.gz
qemu-bd88c780e6a17188f7fd676f3a056e5db21500e0.tar.bz2
qom/cpu: remove host_tid field
This was only used by the gdbstub and even then was only being set for subsequent threads. Rather the continue duplicating the number just make the gdbstub get the information from TaskState structure. Now the tid is correctly reported for all threads the bug I was seeing with "vCont;C04:0;c" packets is fixed as the correct tid is reported to gdb. I moved cpu_gdb_index into the gdbstub to facilitate easy access to the TaskState which is used elsewhere in gdbstub. To prevent BSD failing to build I've included ts_tid into its TaskStruct but not populated it - which was the same state as the old cpu->host_tid. I'll leave it up to the BSD maintainers to actually populate this properly if they want a working gdbstub with user-threads. Signed-off-by: Alex Bennée <alex.bennee@linaro.org> Reviewed-by: Greg Kurz <groug@kaod.org> Reviewed-by: Claudio Imbrenda <imbrenda@linux.vnet.ibm.com> Reviewed-by: Philippe Mathieu-Daudé <f4bug@amsat.org> Reviewed-by: Laurent Vivier <laurent@vivier.eu> Message-Id: <20170712105216.747-4-alex.bennee@linaro.org> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'qemu-options.h')
0 files changed, 0 insertions, 0 deletions