linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: pbonzini@redhat.com (Paolo Bonzini)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/7] KVM: arm: guest debug, define API headers
Date: Tue, 25 Nov 2014 18:05:00 +0100	[thread overview]
Message-ID: <5474B6BC.2060309@redhat.com> (raw)
In-Reply-To: <1416931805-23223-3-git-send-email-alex.bennee@linaro.org>



On 25/11/2014 17:10, Alex Benn?e 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
> +
>  struct kvm_debug_exit_arch {
> +	__u64 address;
> +	__u32 exit_type;
>  };
>  

So there is no register that says "this breakpoint has triggered" or
"this watchpoint has triggered"?

Paolo

  parent reply	other threads:[~2014-11-25 17:05 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-25 16:09 [PATCH 0/7] KVM Guest Debug support for arm64 Alex Bennée
2014-11-25 16:09 ` [PATCH 1/7] KVM: add commentary for kvm_debug_exit_arch struct Alex Bennée
2014-11-26 14:20   ` Andrew Jones
2014-11-25 16:10 ` [PATCH 2/7] KVM: arm: guest debug, define API headers Alex Bennée
2014-11-25 16:19   ` Peter Maydell
2014-11-26 15:04     ` Alex Bennée
2014-11-29 16:20       ` Christoffer Dall
2014-12-01 11:30         ` Alex Bennée
2014-11-25 17:05   ` Paolo Bonzini [this message]
2014-11-25 17:13     ` Peter Maydell
2014-11-25 17:22       ` Paolo Bonzini
2014-11-26 13:13         ` Alex Bennée
2014-11-26 13:14           ` Paolo Bonzini
2014-11-26 14:31   ` Andrew Jones
2014-11-26 14:58     ` Alex Bennée
2014-11-26 16:46       ` Paolo Bonzini
2014-11-26 17:47         ` Andrew Jones
2014-11-29 16:20   ` Christoffer Dall
2014-11-25 16:10 ` [PATCH 3/7] KVM: arm: guest debug, add stub KVM_SET_GUEST_DEBUG ioctl Alex Bennée
2014-11-26 14:38   ` Andrew Jones
2014-11-26 15:03     ` Alex Bennée
2014-11-26 16:46       ` Paolo Bonzini
2014-11-29 16:21   ` Christoffer Dall
2014-11-25 16:10 ` [PATCH 4/7] KVM: arm64: guest debug, add SW break point support Alex Bennée
2014-11-26 16:07   ` Andrew Jones
2014-11-26 17:14     ` Peter Maydell
2014-11-29 16:21     ` Christoffer Dall
2014-11-29 16:21   ` Christoffer Dall
2014-12-01 11:33     ` Alex Bennée
2014-11-25 16:10 ` [PATCH 5/7] KVM: arm64: guest debug, add support for single-step Alex Bennée
2014-11-26 16:40   ` Andrew Jones
2014-11-26 18:00     ` Alex Bennée
2014-11-26 19:27   ` Peter Maydell
2014-11-30 10:10     ` Christoffer Dall
2014-11-30 10:20       ` Peter Maydell
2014-11-30 10:21   ` Christoffer Dall
2014-12-01 11:50     ` Alex Bennée
2014-12-02 13:17       ` Christoffer Dall
2014-11-25 16:10 ` [PATCH 6/7] KVM: arm64: re-factor hyp.S debug register code Alex Bennée
2014-11-26 16:49   ` Andrew Jones
2014-11-30 10:25   ` Christoffer Dall
2014-12-01 11:52     ` Alex Bennée
2014-12-02 13:23       ` Christoffer Dall
2014-11-25 16:10 ` [PATCH 7/7] KVM: arm64: guest debug, HW assisted debug support Alex Bennée
2014-11-26 17:34   ` Andrew Jones
2014-11-30 10:34   ` Christoffer Dall
2014-12-01 11:54     ` 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=5474B6BC.2060309@redhat.com \
    --to=pbonzini@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).