[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87ppcaknpx.fsf@linaro.org>
Date: Wed, 26 Nov 2014 15:04:10 +0000
From: Alex Bennée <alex.bennee@...aro.org>
To: Peter Maydell <peter.maydell@...aro.org>
Cc: kvm-devel <kvm@...r.kernel.org>,
arm-mail-list <linux-arm-kernel@...ts.infradead.org>,
"kvmarm\@lists.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,
Paolo Bonzini <pbonzini@...hat.com>,
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
Peter Maydell <peter.maydell@...aro.org> writes:
> On 25 November 2014 at 16:10, Alex Bennée <alex.bennee@...aro.org> wrote:
>> +/* Exit types which define why we did a debug exit */
>> +#define KVM_DEBUG_EXIT_ERROR 0x0
>> +#define KVM_DEBUG_EXIT_SINGLE_STEP 0x1
>> +#define KVM_DEBUG_EXIT_SW_BKPT 0x2
>> +#define KVM_DEBUG_EXIT_HW_BKPT 0x3
>> +#define KVM_DEBUG_EXIT_HW_WTPT 0x4
>
> The names of these imply that they're generic, but they're
> defined in an arch-specific header file...
Yeah, I think these will die and I'll just export the syndrome
information directly to QEMU.
--
Alex Bennée
--
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