From mboxrd@z Thu Jan  1 00:00:00 1970
From: Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: x86: Hardware breakpoints are not always triggered
Date: Thu, 28 Jan 2016 22:29:30 +0100
Message-ID: <56AA883A.5070801@redhat.com>
References: <CANaxB-wGTnLX=s9aVG4ziXVtsVn672Q4BmfEX12=398_XZdmqA@mail.gmail.com>
 <20160128205327.GA19931@redhat.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Cc: LKML <linux-kernel@vger.kernel.org>,
	Andy Lutomirski <luto@amacapital.net>,
	Cyrill Gorcunov <gorcunov@openvz.org>,
	"criu@openvz.org" <criu@openvz.org>, kvm@vger.kernel.org
To: Oleg Nesterov <oleg@redhat.com>, Andrey Wagin <avagin@gmail.com>
Return-path: <kvm-owner@vger.kernel.org>
Received: from mail-wm0-f54.google.com ([74.125.82.54]:38786 "EHLO
	mail-wm0-f54.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1752208AbcA1V3g (ORCPT <rfc822;kvm@vger.kernel.org>);
	Thu, 28 Jan 2016 16:29:36 -0500
In-Reply-To: <20160128205327.GA19931@redhat.com>
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>



On 28/01/2016 21:53, Oleg Nesterov wrote:
> > We use hardware breakpoints in CRIU and we found that sometimes we set
> > a break-point, but a process doesn't stop on it.
> 
> reproduced, and this certainly looks like kvm bug to me.

Yes, in all likelihood.  Thanks, I'll reproduce and look for a fix.

Paolo