From mboxrd@z Thu Jan 1 00:00:00 1970 From: Paolo Bonzini Subject: Re: [CRIU] x86: Hardware breakpoints are not always triggered Date: Sun, 31 Jan 2016 12:01:53 +0100 Message-ID: <56ADE9A1.4080309@redhat.com> References: <56AA8928.50507@redhat.com> <20160128224224.GA10028@gmail.com> <20160129222130.GC10798@odin.com> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Cc: kvm@vger.kernel.org, Oleg Nesterov , LKML , "criu@openvz.org" , Cyrill Gorcunov To: Andrew Vagin , Andrey Wagin Return-path: In-Reply-To: <20160129222130.GC10798@odin.com> Sender: linux-kernel-owner@vger.kernel.org List-Id: kvm.vger.kernel.org On 29/01/2016 23:21, Andrew Vagin wrote: > On Thu, Jan 28, 2016 at 02:42:25PM -0800, Andrey Wagin wrote: >> On Thu, Jan 28, 2016 at 10:33:28PM +0100, Paolo Bonzini wrote: >>> >>> >>> On 28/01/2016 09:31, Andrey Wagin wrote: >>>> I tried to print drX registers after a break-point. Looks like they >>>> are set correctly. >>> >>> Can you try this KVM patch? >> >> Looks like it fixes a case when reproducers are running only in VM. > > Actually Oleg's reproducer detects the bug with this patch when they are > rinning only in VM. That's actually a good thing, because the patch was a long shot and I had no clue _why_ it would have fixed the bug. Oleg's reproducer spanning host and a VM actually gives me an idea of what is going on, I'll try to reproduce this week. Paolo