[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5474BAD8.7010307@redhat.com>
Date: Tue, 25 Nov 2014 18:22:32 +0100
From: Paolo Bonzini <pbonzini@...hat.com>
To: Peter Maydell <peter.maydell@...aro.org>
CC: Alex Bennée <alex.bennee@...aro.org>,
kvm-devel <kvm@...r.kernel.org>,
arm-mail-list <linux-arm-kernel@...ts.infradead.org>,
"kvmarm@...ts.cs.columbia.edu" <kvmarm@...ts.cs.columbia.edu>,
Christoffer Dall <christoffer.dall@...aro.org>,
Marc Zyngier <marc.zyngier@....com>,
Alexander Graf <agraf@...e.de>,
"J. Kiszka" <jan.kiszka@...mens.com>,
David Hildenbrand <dahi@...ux.vnet.ibm.com>,
Bharat Bhushan <r65777@...escale.com>, bp@...e.de,
Catalin Marinas <catalin.marinas@....com>,
Will Deacon <will.deacon@....com>,
open list <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 2/7] KVM: arm: guest debug, define API headers
On 25/11/2014 18:13, Peter Maydell wrote:
> On 25 November 2014 at 17:05, Paolo Bonzini <pbonzini@...hat.com> 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@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists