On 2016/1/26 0:53, Peter Maydell wrote:
> On 15 January 2016 at 06:27, Shannon Zhao wrote:
>> > From: Shannon Zhao
>> >
>> > To configure the virtual PMUv3 overflow interrupt number, we use the
>> > vcpu kvm_device ioctl, encapsulating the KVM_ARM_VCPU_PMU_V3_IRQ
>> > attribute within the KVM_A
On 15 January 2016 at 06:27, Shannon Zhao wrote:
> From: Shannon Zhao
>
> To configure the virtual PMUv3 overflow interrupt number, we use the
> vcpu kvm_device ioctl, encapsulating the KVM_ARM_VCPU_PMU_V3_IRQ
> attribute within the KVM_ARM_VCPU_PMU_V3_CTRL group.
>
> After configuring the PMUv3,
On 2016/1/15 21:28, Andrew Jones wrote:
On Fri, Jan 15, 2016 at 02:27:55PM +0800, Shannon Zhao wrote:
From: Shannon Zhao
To configure the virtual PMUv3 overflow interrupt number, we use the
vcpu kvm_device ioctl, encapsulating the KVM_ARM_VCPU_PMU_V3_IRQ
attribute within the KVM_ARM_VCPU_PMU
On Fri, Jan 15, 2016 at 02:27:55PM +0800, Shannon Zhao wrote:
> From: Shannon Zhao
>
> To configure the virtual PMUv3 overflow interrupt number, we use the
> vcpu kvm_device ioctl, encapsulating the KVM_ARM_VCPU_PMU_V3_IRQ
> attribute within the KVM_ARM_VCPU_PMU_V3_CTRL group.
>
> After configur
From: Shannon Zhao
To configure the virtual PMUv3 overflow interrupt number, we use the
vcpu kvm_device ioctl, encapsulating the KVM_ARM_VCPU_PMU_V3_IRQ
attribute within the KVM_ARM_VCPU_PMU_V3_CTRL group.
After configuring the PMUv3, call the vcpu iotcl with attribute
KVM_ARM_VCPU_PMU_V3_INIT t