diff options
| author | Radim Krčmář <rkrcmar@redhat.com> | 2018-10-23 17:31:38 +0300 |
|---|---|---|
| committer | Radim Krčmář <rkrcmar@redhat.com> | 2018-10-23 17:34:59 +0300 |
| commit | f9dcf08e2017cad12d771cdd862c8c314b885615 (patch) | |
| tree | 1f84c5fe04a1dd5ca9bd0b9ed64f29d532d71e09 /tools/arch | |
| parent | 574c0cfbc7159c5a5a59d5608e422c95917a9b7c (diff) | |
| download | linux-f9dcf08e2017cad12d771cdd862c8c314b885615.tar.xz | |
Revert "kvm: x86: optimize dr6 restore"
This reverts commit 0e0a53c551317654e2d7885fdfd23299fee99b6b.
As Christian Ehrhardt noted:
The most common case is that vcpu->arch.dr6 and the host's %dr6 value
are not related at all because ->switch_db_regs is zero. To do this
all correctly, we must handle the case where the guest leaves an arbitrary
unused value in vcpu->arch.dr6 before disabling breakpoints again.
However, this means that vcpu->arch.dr6 is not suitable to detect the
need for a %dr6 clear.
Signed-off-by: Radim Krčmář <rkrcmar@redhat.com>
Diffstat (limited to 'tools/arch')
0 files changed, 0 insertions, 0 deletions