| Message ID | 1410280039-2823-2-git-send-email-alex.bennee@linaro.org |
|---|---|
| State | Accepted |
| Commit | 4bd9d3441edadff4c8df9de4b5d5386c36667ca6 |
| Headers | show |
On Tue, Sep 09, 2014 at 05:27:18PM +0100, Alex Bennée wrote: > In preparation for working on the ARM implementation I noticed the debug > interface was missing from the API document. I've pieced together the > expected behaviour from the code and commit messages written it up as > best I can. > > Signed-off-by: Alex Bennée <alex.bennee@linaro.org> > > diff --git a/Documentation/virtual/kvm/api.txt b/Documentation/virtual/kvm/api.txt > index d3dde61..723d3f3 100644 > --- a/Documentation/virtual/kvm/api.txt > +++ b/Documentation/virtual/kvm/api.txt > @@ -2575,6 +2575,50 @@ associated with the service will be forgotten, and subsequent RTAS > calls by the guest for that service will be passed to userspace to be > handled. > > +4.87 KVM_SET_GUEST_DEBUG > + > +Capability: KVM_CAP_SET_GUEST_DEBUG > +Architectures: x86, s390, ppc > +Type: vcpu ioctl > +Parameters: struct kvm_guest_debug (in) > +Returns: 0 on success; -1 on error Any specific error codes that need explaining here? > + > +struct kvm_guest_debug { > + __u32 control; > + __u32 pad; > + struct kvm_guest_debug_arch arch; > +}; > + > +Set up the processor specific debug registers and configure vcpu for configure *the* vcpu? > +handling guest debug events. There are two parts to the structure, the handling guest debug events> does this mean whatever user space needs to configure so that the guest can deug things or is this for userspace to debug the guest execution, we could probably be more specific. > +first a control bitfield indicates the type of debug events to handle > +when running. Common control bits are: 'when running'? 'when running the vcpu'? > + > + - KVM_GUESTDBG_ENABLE: guest debugging is enabled > + - KVM_GUESTDBG_SINGLESTEP: the next run should single-step > + > +The top 16 bits of the control field are architecture specific control > +flags which can include the following: > + > + - KVM_GUESTDBG_USE_SW_BP: using software breakpoints [x86] > + - KVM_GUESTDBG_USE_HW_BP: using hardware breakpoints [x86, s390] > + - KVM_GUESTDBG_INJECT_DB: inject DB type exception [x86] > + - KVM_GUESTDBG_INJECT_BP: inject BP type exception [x86] > + - KVM_GUESTDBG_EXIT_PENDING: trigger an immediate guest exit [s390] > + > +For example KVM_GUESTDBG_USE_SW_BP indicates that software breakpoints > +are enabled in memory so we need to ensure breakpoint exceptions are > +correctly trapped and the KVM run loop exits at the breakpoint and not > +running off into the normal guest vector. For KVM_GUESTDBG_USE_HW_BP I didn't quite understand this bit, can you clarify slightly? For example, I don't know what it means that a software breakpoint is 'enabled in memory' and I'm not quite sure what the goal you are arguing for here is; is this about if this ioctl is used to set a specific breakpoint then we want to make sure that the breakpoint exception goes to KVM and not to the guest? also, are you not missing a 'that' before 'the KVM run loop...' > +we need to ensure the guest vCPUs architecture specific registers are please be consistent about the use of vcpu, VCPUs, vCPUs, etc. The document seems to prefer lowercase vcpus most places. > +updated to the correct (supplied) values. > + > +The second part of the structure is architecture specific and > +typically contains a set of debug registers. > + > +When debug events exit the main run loop with the reason I think you should just talk about then the VCPU exits the guest and not be specific about whether we have a main run loop or not. > +KVM_EXIT_DEBUG with the kvm_debug_exit_arch part of the kvm_run > +structure containing architecture specific debug information. I feel like this sentence leaves me hanging; When they exit with the debug information, then what? Or did you mean to say that when they exit, then the arch struct is filled with the debug info? > > 5. The kvm_run structure > ------------------------ > -- > 2.1.0 > Thanks for taking care of this! -Christoffer -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
diff --git a/Documentation/virtual/kvm/api.txt b/Documentation/virtual/kvm/api.txt index d3dde61..723d3f3 100644 --- a/Documentation/virtual/kvm/api.txt +++ b/Documentation/virtual/kvm/api.txt @@ -2575,6 +2575,50 @@ associated with the service will be forgotten, and subsequent RTAS calls by the guest for that service will be passed to userspace to be handled. +4.87 KVM_SET_GUEST_DEBUG + +Capability: KVM_CAP_SET_GUEST_DEBUG +Architectures: x86, s390, ppc +Type: vcpu ioctl +Parameters: struct kvm_guest_debug (in) +Returns: 0 on success; -1 on error + +struct kvm_guest_debug { + __u32 control; + __u32 pad; + struct kvm_guest_debug_arch arch; +}; + +Set up the processor specific debug registers and configure vcpu for +handling guest debug events. There are two parts to the structure, the +first a control bitfield indicates the type of debug events to handle +when running. Common control bits are: + + - KVM_GUESTDBG_ENABLE: guest debugging is enabled + - KVM_GUESTDBG_SINGLESTEP: the next run should single-step + +The top 16 bits of the control field are architecture specific control +flags which can include the following: + + - KVM_GUESTDBG_USE_SW_BP: using software breakpoints [x86] + - KVM_GUESTDBG_USE_HW_BP: using hardware breakpoints [x86, s390] + - KVM_GUESTDBG_INJECT_DB: inject DB type exception [x86] + - KVM_GUESTDBG_INJECT_BP: inject BP type exception [x86] + - KVM_GUESTDBG_EXIT_PENDING: trigger an immediate guest exit [s390] + +For example KVM_GUESTDBG_USE_SW_BP indicates that software breakpoints +are enabled in memory so we need to ensure breakpoint exceptions are +correctly trapped and the KVM run loop exits at the breakpoint and not +running off into the normal guest vector. For KVM_GUESTDBG_USE_HW_BP +we need to ensure the guest vCPUs architecture specific registers are +updated to the correct (supplied) values. + +The second part of the structure is architecture specific and +typically contains a set of debug registers. + +When debug events exit the main run loop with the reason +KVM_EXIT_DEBUG with the kvm_debug_exit_arch part of the kvm_run +structure containing architecture specific debug information. 5. The kvm_run structure ------------------------
In preparation for working on the ARM implementation I noticed the debug interface was missing from the API document. I've pieced together the expected behaviour from the code and commit messages written it up as best I can. Signed-off-by: Alex Bennée <alex.bennee@linaro.org>