From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755937AbcA1V3m (ORCPT ); Thu, 28 Jan 2016 16:29:42 -0500 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 ); Thu, 28 Jan 2016 16:29:36 -0500 Subject: Re: x86: Hardware breakpoints are not always triggered To: Oleg Nesterov , Andrey Wagin References: <20160128205327.GA19931@redhat.com> Cc: LKML , Andy Lutomirski , Cyrill Gorcunov , "criu@openvz.org" , kvm@vger.kernel.org From: Paolo Bonzini Message-ID: <56AA883A.5070801@redhat.com> Date: Thu, 28 Jan 2016 22:29:30 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.5.0 MIME-Version: 1.0 In-Reply-To: <20160128205327.GA19931@redhat.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@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