Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751708AbaKYRXk (ORCPT ); Tue, 25 Nov 2014 12:23:40 -0500 Received: from mx1.redhat.com ([209.132.183.28]:48956 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751303AbaKYRXh (ORCPT ); Tue, 25 Nov 2014 12:23:37 -0500 Message-ID: <5474BAD8.7010307@redhat.com> Date: Tue, 25 Nov 2014 18:22:32 +0100 From: Paolo Bonzini User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 MIME-Version: 1.0 To: Peter Maydell CC: =?UTF-8?B?QWxleCBCZW5uw6ll?= , kvm-devel , arm-mail-list , "kvmarm@lists.cs.columbia.edu" , Christoffer Dall , Marc Zyngier , Alexander Graf , "J. Kiszka" , David Hildenbrand , Bharat Bhushan , bp@suse.de, Catalin Marinas , Will Deacon , open list Subject: Re: [PATCH 2/7] KVM: arm: guest debug, define API headers References: <1416931805-23223-1-git-send-email-alex.bennee@linaro.org> <1416931805-23223-3-git-send-email-alex.bennee@linaro.org> <5474B6BC.2060309@redhat.com> In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 25/11/2014 18:13, Peter Maydell wrote: > On 25 November 2014 at 17:05, Paolo Bonzini wrote: >> > So there is no register that says "this breakpoint has triggered" or >> > "this watchpoint has triggered"? > Nope. You take a debug exception; the syndrome register tells > you if it was a bp or a wp, and if it was a wp the fault address > register tells you the address being accessed (if it was a bp > you know the program counter, obviously). The debugger is expected > to be able to figure it out from there, if it cares. That's already good enough---do the KVM_DEBUG_EXIT_* constants match the syndrome register, or if not why? Paolo -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/