summaryrefslogtreecommitdiff
path: root/Documentation/virtual
diff options
context:
space:
mode:
authorJim Mattson <jmattson@google.com>2018-10-17 00:29:23 +0300
committerPaolo Bonzini <pbonzini@redhat.com>2018-10-17 20:07:43 +0300
commitf10c729ff965283d2086aa03d139dcf82da86a96 (patch)
tree1fb0a85cd6ecf0f9f21726bc87da7a030bc3738b /Documentation/virtual
parentda998b46d244767505e41d050dcac5e4d03ba96f (diff)
downloadlinux-f10c729ff965283d2086aa03d139dcf82da86a96.tar.xz
kvm: vmx: Defer setting of DR6 until #DB delivery
When exception payloads are enabled by userspace (which is not yet possible) and a #DB is raised in L2, defer the setting of DR6 until later. Under VMX, this allows the L1 hypervisor to intercept the fault before DR6 is modified. Under SVM, DR6 is modified before L1 can intercept the fault (as has always been the case with DR7). Note that the payload associated with a #DB exception includes only the "new DR6 bits." When the payload is delievered, DR6.B0-B3 will be cleared and DR6.RTM will be set prior to merging in the new DR6 bits. Also note that bit 16 in the "new DR6 bits" is set to indicate that a debug exception (#DB) or a breakpoint exception (#BP) occurred inside an RTM region while advanced debugging of RTM transactional regions was enabled. Though the reverse of DR6.RTM, this makes the #DB payload field compatible with both the pending debug exceptions field under VMX and the exit qualification for #DB exceptions under VMX. Reported-by: Jim Mattson <jmattson@google.com> Suggested-by: Paolo Bonzini <pbonzini@redhat.com> Signed-off-by: Jim Mattson <jmattson@google.com> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'Documentation/virtual')
0 files changed, 0 insertions, 0 deletions