Re: Exposing host debug capabilities to userspace

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 24 November 2014 at 12:41, Alexander Graf <agraf@xxxxxxx> wrote:
>> Am 24.11.2014 um 13:32 schrieb Peter Maydell <peter.maydell@xxxxxxxxxx>:
>> 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.

I'm confused. ONE_REG is for guest state, and the ID register
by definition is how we tell the guest how many debug registers
it has. What we want to know (and perhaps even control) for
debugging the VM is how many debug registers the host has.

-- PMM
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [KVM ARM]     [KVM ia64]     [KVM ppc]     [Virtualization Tools]     [Spice Development]     [Libvirt]     [Libvirt Users]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite Questions]     [Linux Kernel]     [Linux SCSI]     [XFree86]
  Powered by Linux