linux-kernel - Re: [CRIU] x86: Hardware breakpoints are not always triggered

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <56B335D6.2020701@redhat.com>
Date:	Thu, 4 Feb 2016 12:28:22 +0100
From:	Paolo Bonzini <pbonzini@...hat.com>
To:	Nadav Amit <nadav.amit@...il.com>
Cc:	Andrew Vagin <avagin@...tuozzo.com>,
	Andrey Wagin <avagin@...il.com>, kvm@...r.kernel.org,
	Oleg Nesterov <oleg@...hat.com>,
	LKML <linux-kernel@...r.kernel.org>,
	"criu@...nvz.org" <criu@...nvz.org>,
	Cyrill Gorcunov <gorcunov@...nvz.org>
Subject: Re: [CRIU] x86: Hardware breakpoints are not always triggered



On 04/02/2016 00:32, Nadav Amit wrote:
> Sorry for spamming. The correct fix appears to reload the DRs (set
> KVM_DEBUGREG_RELOAD) in kvm_arch_vcpu_load .

Yup, that was my intended thing to test, but unfortunately I'm
travelling and doing all the testing on the laptop is a bit hard.

Thanks Nadav!!!

Paolo