> Am 24.11.2014 um 13:32 schrieb Peter Maydell <peter.mayd...@linaro.org>: > >> On 24 November 2014 at 12:26, Alexander Graf <ag...@suse.de> wrote: >> On 24.11.14 12:35, Alex Bennée wrote: >>>> * KVM ioctl GET_ONE_REG(ID_AA64DFR0_EL1) >>> Nope, guest state API >> >> What's the problem with using ONE_REG for this? After all, the total >> number of available guest debug register is a guest vcpu property of >> some sort. > > Yes, but we don't want to know about properties of the guest > vCPU. In an ideal world QEMU could reserve say half the debug > registers for debugging the VM on startup and have KVM expose > ID registers indicating to the guest that it only had the > other half... Yup, so create another (read-only) ONE_REG that exposes the number of actual guest debug registers. Alex > > -- PMM -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
- Exposing host debug capabilities to userspace Alex Bennée
- Re: Exposing host debug capabilities to userspace Christoffer Dall
- Re: Exposing host debug capabilities to userspace Peter Maydell
- Re: Exposing host debug capabilities to userspac... Christoffer Dall
- Re: Exposing host debug capabilities to userspace Alex Bennée
- Re: Exposing host debug capabilities to userspac... Alexander Graf
- Re: Exposing host debug capabilities to user... Peter Maydell
- Re: Exposing host debug capabilities to ... Alexander Graf
- Re: Exposing host debug capabilitie... Peter Maydell
- Re: Exposing host debug capabil... Alexander Graf
- Re: Exposing host debug cap... Christoffer Dall
- Re: Exposing host debug cap... Alexander Graf
- Re: Exposing host debug cap... Christoffer Dall
- Re: Exposing host debug cap... Alexander Graf
- Re: Exposing host debug cap... Christoffer Dall
- Re: Exposing host debug cap... Paolo Bonzini
- Re: Exposing host debug capabilitie... Alex Bennée
- Re: Exposing host debug capabil... Christoffer Dall