summaryrefslogtreecommitdiffstats
path: root/contrib/llvm/tools/lldb/source/Plugins/Process/gdb-remote/ProcessGDBRemote.cpp
diff options
context:
space:
mode:
authorjhb <jhb@FreeBSD.org>2014-02-18 03:07:36 +0000
committerjhb <jhb@FreeBSD.org>2014-02-18 03:07:36 +0000
commit521737384dcc8c078e0c9624cdc4d5f72e11b80d (patch)
tree7ec2b07434d283aaf8e0dae230ad67d81d75094e /contrib/llvm/tools/lldb/source/Plugins/Process/gdb-remote/ProcessGDBRemote.cpp
parentea7ce4c7d3afc6c94d6c7777f03916c8296a56b4 (diff)
downloadFreeBSD-src-521737384dcc8c078e0c9624cdc4d5f72e11b80d.zip
FreeBSD-src-521737384dcc8c078e0c9624cdc4d5f72e11b80d.tar.gz
A first pass at adding support for injecting hardware exceptions for
emulated instructions. - Add helper routines to inject interrupt information for a hardware exception from the VM exit callback routines. - Use the new routines to inject GP and UD exceptions for invalid operations when emulating the xsetbv instruction. - Don't directly manipulate the entry interrupt info when a user event is injected. Instead, store the event info in the vmx state and only apply it during a VM entry if a hardware exception or NMI is not already pending. - While here, use HANDLED/UNHANDLED instead of 1/0 in a couple of routines. Reviewed by: neel
Diffstat (limited to 'contrib/llvm/tools/lldb/source/Plugins/Process/gdb-remote/ProcessGDBRemote.cpp')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud