From: drjones@redhat.com (Andrew Jones)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v5 03/12] KVM: arm64: guest debug, define API headers
Date: Thu, 4 Jun 2015 16:40:54 +0200 [thread overview]
Message-ID: <20150604144054.GD2860@hawk.localdomain> (raw)
In-Reply-To: <878ubzbn36.fsf@linaro.org>
On Thu, Jun 04, 2015 at 02:49:17PM +0100, Alex Benn?e wrote:
>
> Christoffer Dall <christoffer.dall@linaro.org> writes:
>
> > On Fri, May 29, 2015 at 10:30:19AM +0100, Alex Benn?e wrote:
> >> This commit defines the API headers for guest debugging. There are two
> >> architecture specific debug structures:
> >>
> >> - kvm_guest_debug_arch, allows us to pass in HW debug registers
> >> - kvm_debug_exit_arch, signals exception and possible faulting address
> >>
> >> The type of debugging being used is controlled by the architecture
> >> specific control bits of the kvm_guest_debug->control flags in the ioctl
> >> structure.
> >>
> >> Signed-off-by: Alex Benn?e <alex.bennee@linaro.org>
> >> Reviewed-by: David Hildenbrand <dahi@linux.vnet.ibm.com>
> >> Reviewed-by: Andrew Jones <drjones@redhat.com>
> >> Acked-by: Christoffer Dall <christoffer.dall@linaro.org>
> >
> > I can re-confirm my ack despite the changes in v4, but this really is
> > borderline to keep exiting r-b and a-b tags around from previous patches
> > I would think, but ok.
>
> I was wondering how much a patch has to change for the r-b tags to
> become invalid. The meat of the API hasn't changed much though.
>
> Drew/David,
>
> Are you still happy with this patch?
I'm fine with it. Sorry I haven't had time to look over the rest of the
series yet this round.
drew
>
> >
> > -Christoffer
> >
> >>
> >> ---
> >> v2
> >> - expose hsr and pc directly to user-space
> >> v3
> >> - s/control/controlled/ in commit message
> >> - add v8 to ARM ARM comment (ARM Architecture Reference Manual)
> >> - add rb tag
> >> - rm pc, add far
> >> - re-word comments on alignment
> >> - rename KVM_ARM_NDBG_REGS -> KVM_ARM_MAX_DBG_REGS
> >> v4
> >> - now uses common HW/SW BP define
> >> - add a-b-tag
> >> - use u32 for control regs
> >> v5
> >> - revert to have arch specific KVM_GUESTDBG_USE_SW/HW_BP
> >> - rm stale comments dbgctrl was stored as u64
> >> ---
> >> arch/arm64/include/uapi/asm/kvm.h | 20 ++++++++++++++++++++
> >> 1 file changed, 20 insertions(+)
> >>
> >> diff --git a/arch/arm64/include/uapi/asm/kvm.h b/arch/arm64/include/uapi/asm/kvm.h
> >> index d268320..43758e7 100644
> >> --- a/arch/arm64/include/uapi/asm/kvm.h
> >> +++ b/arch/arm64/include/uapi/asm/kvm.h
> >> @@ -100,12 +100,32 @@ struct kvm_sregs {
> >> struct kvm_fpu {
> >> };
> >>
> >> +/*
> >> + * See v8 ARM ARM D7.3: Debug Registers
> >> + *
> >> + * The architectural limit is 16 debug registers of each type although
> >> + * in practice there are usually less (see ID_AA64DFR0_EL1).
> >> + */
> >> +#define KVM_ARM_MAX_DBG_REGS 16
> >> struct kvm_guest_debug_arch {
> >> + __u32 dbg_bcr[KVM_ARM_MAX_DBG_REGS];
> >> + __u64 dbg_bvr[KVM_ARM_MAX_DBG_REGS];
> >> + __u32 dbg_wcr[KVM_ARM_MAX_DBG_REGS];
> >> + __u64 dbg_wvr[KVM_ARM_MAX_DBG_REGS];
> >> };
> >>
> >> struct kvm_debug_exit_arch {
> >> + __u32 hsr;
> >> + __u64 far;
> >> };
> >>
> >> +/*
> >> + * Architecture specific defines for kvm_guest_debug->control
> >> + */
> >> +
> >> +#define KVM_GUESTDBG_USE_SW_BP (1 << 16)
> >> +#define KVM_GUESTDBG_USE_HW_BP (1 << 17)
> >> +
> >> struct kvm_sync_regs {
> >> };
> >>
> >> --
> >> 2.4.1
> >>
>
> --
> Alex Benn?e
> --
> To unsubscribe from this list: send the line "unsubscribe kvm" in
> the body of a message to majordomo at vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
next prev parent reply other threads:[~2015-06-04 14:40 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-29 9:30 [PATCH v5 00/12] KVM Guest Debug support for arm64 Alex Bennée
2015-05-29 9:30 ` [PATCH v5 01/12] KVM: add comments for kvm_debug_exit_arch struct Alex Bennée
2015-05-29 9:30 ` [PATCH v5 02/12] KVM: arm64: fix misleading comments in save/restore Alex Bennée
2015-05-29 9:30 ` [PATCH v5 03/12] KVM: arm64: guest debug, define API headers Alex Bennée
2015-06-04 11:07 ` Christoffer Dall
2015-06-04 13:49 ` Alex Bennée
2015-06-04 14:40 ` Andrew Jones [this message]
2015-05-29 9:30 ` [PATCH v5 04/12] KVM: arm: guest debug, add stub KVM_SET_GUEST_DEBUG ioctl Alex Bennée
2015-05-29 9:30 ` [PATCH v5 05/12] KVM: arm: introduce kvm_arm_init/setup/clear_debug Alex Bennée
2015-06-04 11:07 ` Christoffer Dall
2015-05-29 9:30 ` [PATCH v5 06/12] KVM: arm64: guest debug, add SW break point support Alex Bennée
2015-05-29 9:30 ` [PATCH v5 07/12] KVM: arm64: guest debug, add support for single-step Alex Bennée
2015-06-04 11:07 ` Christoffer Dall
2015-06-04 13:46 ` Alex Bennée
2015-05-29 9:30 ` [PATCH v5 08/12] KVM: arm64: re-factor hyp.S debug register code Alex Bennée
2015-06-04 10:23 ` Christoffer Dall
2015-06-04 10:34 ` Alex Bennée
2015-06-04 11:12 ` Christoffer Dall
2015-05-29 9:30 ` [PATCH v5 09/12] KVM: arm64: introduce vcpu->arch.debug_ptr Alex Bennée
2015-06-04 10:56 ` Christoffer Dall
2015-05-29 9:30 ` [PATCH v5 10/12] KVM: arm64: guest debug, HW assisted debug support Alex Bennée
2015-06-01 9:15 ` Will Deacon
2015-06-01 12:41 ` Alex Bennée
2015-06-04 11:06 ` Christoffer Dall
2015-05-29 9:30 ` [PATCH v5 11/12] KVM: arm64: enable KVM_CAP_SET_GUEST_DEBUG Alex Bennée
2015-05-29 9:30 ` [PATCH v5 12/12] KVM: arm64: add trace points for guest_debug debug Alex Bennée
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150604144054.GD2860@hawk.localdomain \
--to=drjones@redhat.com \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).