On Wed, May 06, 2015 at 05:23:16PM +0100, Alex Bennée wrote:
Bring into line with the comments for the other structures and their
KVM_EXIT_* cases. Also update api.txt to reflect use in kvm_run
documentation.
Signed-off-by: Alex Bennée alex.ben...@linaro.org
Reviewed-by: David Hildenbrand
On Wed, May 06, 2015 at 05:23:17PM +0100, Alex Bennée wrote:
Currently x86, powerpc and soon arm64 use the same two architecture
specific bits for guest debug support for software and hardware
breakpoints. This makes the shared values explicit while leaving the
gate open for another
On Wed, May 06, 2015 at 05:23:18PM +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
On 08/05/2015 11:23, Christoffer Dall wrote:
On Wed, May 06, 2015 at 05:23:17PM +0100, Alex Bennée wrote:
Currently x86, powerpc and soon arm64 use the same two architecture
specific bits for guest debug support for software and hardware
breakpoints. This makes the shared values explicit
On Thu, May 07, 2015 at 10:07:11AM +0100, Alex Bennée wrote:
This is a pre-cursor to sharing the code with the guest debug support.
This replaces the big macro that fishes data out of a fixed location
with a more general helper macro to restore a set of debug registers. It
uses macro
On Thu, May 07, 2015 at 10:07:15AM +0100, Alex Bennée wrote:
This includes trace points for:
kvm_arch_setup_guest_debug
kvm_arch_clear_guest_debug
kvm_handle_guest_debug
I've also added some generic register setting trace events and also a
trace point to dump the array of hardware
On Thu, May 07, 2015 at 10:07:13AM +0100, Alex Bennée wrote:
When we are using the hardware registers for guest debug we need to deal
with the guests access to them. There is already a mechanism for dealing
with these accesses so we build on top of that.
- any access to mdscr_el1 is now
BSYM() should only be used when refering to local symbols in the same
assembly file which are resolved by the assembler, and not for
linker-fixed up symbols. The use of BSYM() with panic is incorrect as
the linker is involved in fixing up this relocation, and it knows
whether panic() is ARM or
On Thu, May 07, 2015 at 10:07:12AM +0100, Alex Bennée wrote:
This adds support for userspace to control the HW debug registers for
guest debug. In the debug ioctl we copy the IMPDEF defined number of
registers into a new register set called host_debug_state. There is now
a new vcpu parameter
On Wed, May 06, 2015 at 05:23:15PM +0100, Alex Bennée wrote:
Hi,
Here is V3 of the KVM Guest Debug support for arm64.
This sees the return of hyp.S re-factoring code which has been
expanded to handle both the save and restore legs. The HW debug patch
then adds a simple indirection to
On Fri, May 08, 2015 at 05:08:42PM +0100, Russell King wrote:
BSYM() should only be used when refering to local symbols in the same
assembly file which are resolved by the assembler, and not for
linker-fixed up symbols. The use of BSYM() with panic is incorrect as
the linker is involved in
On Fri, 8 May 2015, Russell King wrote:
BSYM() should only be used when refering to local symbols in the same
assembly file which are resolved by the assembler, and not for
linker-fixed up symbols. The use of BSYM() with panic is incorrect as
the linker is involved in fixing up this
On Thu, May 07, 2015 at 10:07:14AM +0100, Alex Bennée wrote:
Finally advertise the KVM capability for SET_GUEST_DEBUG. Once arm
support is added this check can be moved to the common
kvm_vm_ioctl_check_extension() code.
Signed-off-by: Alex Bennée alex.ben...@linaro.org
Acked-by:
On Wed, May 06, 2015 at 05:23:21PM +0100, Alex Bennée wrote:
This adds support for SW breakpoints inserted by userspace.
We do this by trapping all guest software debug exceptions to the
hypervisor (MDCR_EL2.TDE). The exit handler sets an exit reason of
KVM_EXIT_DEBUG with the
On Wed, May 06, 2015 at 05:23:22PM +0100, Alex Bennée wrote:
This adds support for single-stepping the guest. To do this we need to
manipulate the guests PSTATE.SS and MDSCR_EL1.SS bits which we do in the
kvm_arm_setup/clear_debug() so we don't affect the apparent state of the
guest.
15 matches
Mail list logo