All of lore.kernel.org
 help / color / mirror / Atom feed
From: Shannon Zhao <zhaoshenglong@huawei.com>
To: Marc Zyngier <marc.zyngier@arm.com>,
	kvmarm@lists.cs.columbia.edu, christoffer.dall@linaro.org
Cc: kvm@vger.kernel.org, will.deacon@arm.com,
	linux-arm-kernel@lists.infradead.org, shannon.zhao@linaro.org
Subject: Re: [PATCH v6 10/21] KVM: ARM64: Add access handler for PMEVCNTRn and PMCCNTR register
Date: Thu, 10 Dec 2015 21:23:20 +0800	[thread overview]
Message-ID: <56697CC8.40109@huawei.com> (raw)
In-Reply-To: <56696B00.6090909@arm.com>



On 2015/12/10 20:07, Marc Zyngier wrote:
> Hi Shannon,
> 
> On 10/12/15 11:36, Shannon Zhao wrote:
>> > Hi Marc,
>> > 
>> > On 2015/12/9 0:30, Marc Zyngier wrote:
>>> >> On 08/12/15 12:47, Shannon Zhao wrote:
>>>>> >>>> From: Shannon Zhao <shannon.zhao@linaro.org>
>>>>> >>>>
>>>>> >>>> Since the reset value of PMEVCNTRn or PMCCNTR is UNKNOWN, use
>>>>> >>>> reset_unknown for its reset handler. Add access handler which emulates
>>>>> >>>> writing and reading PMEVCNTRn or PMCCNTR register. When reading
>>>>> >>>> PMEVCNTRn or PMCCNTR, call perf_event_read_value to get the count value
>>>>> >>>> of the perf event.
>>>>> >>>>
>>>>> >>>> Signed-off-by: Shannon Zhao <shannon.zhao@linaro.org>
>>>>> >>>> ---
>>>>> >>>>  arch/arm64/kvm/sys_regs.c | 107 +++++++++++++++++++++++++++++++++++++++++++++-
>>>>> >>>>  1 file changed, 105 insertions(+), 2 deletions(-)
>>>>> >>>>
>>>>> >>>> diff --git a/arch/arm64/kvm/sys_regs.c b/arch/arm64/kvm/sys_regs.c
>>>>> >>>> index c116a1b..f7a73b5 100644
>>>>> >>>> --- a/arch/arm64/kvm/sys_regs.c
>>>>> >>>> +++ b/arch/arm64/kvm/sys_regs.c
>>>>> >>>> @@ -525,6 +525,12 @@ static bool access_pmu_regs(struct kvm_vcpu *vcpu,
>>>>> >>>>  
>>>>> >>>>  	if (p->is_write) {
>>>>> >>>>  		switch (r->reg) {
>>>>> >>>> +		case PMEVCNTR0_EL0 ... PMCCNTR_EL0: {
>>> >> Same problem as previously mentioned.
>>> >>
>>>>> >>>> +			val = kvm_pmu_get_counter_value(vcpu,
>>>>> >>>> +							r->reg - PMEVCNTR0_EL0);
>>>>> >>>> +			vcpu_sys_reg(vcpu, r->reg) += (s64)p->regval - val;
>>>>> >>>> +			break;
>>>>> >>>> +		}
>> > 
>> > If I use a handler to handle these accesses to PMEVCNTRn and PMCCNTR
>> > like below. It converts the register offset c14_PMEVCNTRn and c9_PMCCNTR
>> > to PMEVCNTRn_EL0 and PMCCNTR_EL0, uniformly uses vcpu_sys_reg and
>> > doesn't need to take care the big endian. What do you think about this?
>> > 
>> > static bool access_pmu_evcntr(struct kvm_vcpu *vcpu,
>> >                               struct sys_reg_params *p,
>> >                               const struct sys_reg_desc *r)
>> > {
>> >         u64 idx, reg, val;
>> > 
>> >         if (p->is_aarch32)
>> >                 reg = r->reg / 2;
> I'd prefer it if you actually decoded the reg itself. Something like:
> 
> 	if (p->is_aarch32) {
> 		if (r->CRn == 9 && r->CRm == 13)
> 			reg = (r->Op2 & 1) ? 0 : PMCCNTR_EL0;
> 		if (r->CRn == 14 && (r->CRm & 0xc) == 8) {
> 			reg = ((r->CRm & 3) << 2) & (r->Op2 & 7);
> 			reg += PMEVCNTR0_EL0;
> 		} else {
> 			BUG();
> 		}
> 	} else {
> 		....
> 	}
> 
> And then you can get rid of the c14_PMVCNTR* and c9_PMCCNTR macros.
> The only slightly ugly thing is this 0 value to represent PMXEVTYPER,
> but that's what we already have with your "default" clause below.
> 
Ok, thanks.
>> >         else
>> >                 reg = r->reg;
>> > 
>> >         switch (reg) {
>> >         case PMEVCNTR0_EL0 ... PMEVCNTR30_EL0: {
>> >                 idx = reg - PMEVCNTR0_EL0;
>> >                 break;
>> >         }
>> >         case PMCCNTR_EL0: {
>> >                 idx = ARMV8_CYCLE_IDX;
>> >                 break;
>> >         }
>> >         default:
>> >                 idx = vcpu_sys_reg(vcpu, PMSELR_EL0) & ARMV8_COUNTER_MASK;
>> >                 if (!pmu_counter_idx_valid(vcpu, idx))
>> >                         return true;
>> >                 reg = (idx == ARMV8_CYCLE_IDX) ? PMCCNTR_EL0 :
>> > PMEVCNTR0_EL0 + idx;
>> >                 break;
>> >         }
>> > 
>> >         val = kvm_pmu_get_counter_value(vcpu, idx);
>> >         if (p->is_write)
>> >                 vcpu_sys_reg(vcpu, reg) = (s64)p->regval - val;
> Maybe I don't have my head screwed in the right way, but as long as
> we're only using u64 quantities, why do we need this s64 cast?
> 
In case p->regval less than val.
For example, at the first time it writes 0x80000001 to
vcpu_sys_reg(vcpu, reg) and start a perf event which counts a value
10000. Then we want to start the same perf event with writing 0x80000001
to vcpu_sys_reg(vcpu, reg) too. At this time, p->regval(0x80000001) is
less than val(0x80000001 + 10000).

Thanks,
-- 
Shannon

WARNING: multiple messages have this Message-ID (diff)
From: zhaoshenglong@huawei.com (Shannon Zhao)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v6 10/21] KVM: ARM64: Add access handler for PMEVCNTRn and PMCCNTR register
Date: Thu, 10 Dec 2015 21:23:20 +0800	[thread overview]
Message-ID: <56697CC8.40109@huawei.com> (raw)
In-Reply-To: <56696B00.6090909@arm.com>



On 2015/12/10 20:07, Marc Zyngier wrote:
> Hi Shannon,
> 
> On 10/12/15 11:36, Shannon Zhao wrote:
>> > Hi Marc,
>> > 
>> > On 2015/12/9 0:30, Marc Zyngier wrote:
>>> >> On 08/12/15 12:47, Shannon Zhao wrote:
>>>>> >>>> From: Shannon Zhao <shannon.zhao@linaro.org>
>>>>> >>>>
>>>>> >>>> Since the reset value of PMEVCNTRn or PMCCNTR is UNKNOWN, use
>>>>> >>>> reset_unknown for its reset handler. Add access handler which emulates
>>>>> >>>> writing and reading PMEVCNTRn or PMCCNTR register. When reading
>>>>> >>>> PMEVCNTRn or PMCCNTR, call perf_event_read_value to get the count value
>>>>> >>>> of the perf event.
>>>>> >>>>
>>>>> >>>> Signed-off-by: Shannon Zhao <shannon.zhao@linaro.org>
>>>>> >>>> ---
>>>>> >>>>  arch/arm64/kvm/sys_regs.c | 107 +++++++++++++++++++++++++++++++++++++++++++++-
>>>>> >>>>  1 file changed, 105 insertions(+), 2 deletions(-)
>>>>> >>>>
>>>>> >>>> diff --git a/arch/arm64/kvm/sys_regs.c b/arch/arm64/kvm/sys_regs.c
>>>>> >>>> index c116a1b..f7a73b5 100644
>>>>> >>>> --- a/arch/arm64/kvm/sys_regs.c
>>>>> >>>> +++ b/arch/arm64/kvm/sys_regs.c
>>>>> >>>> @@ -525,6 +525,12 @@ static bool access_pmu_regs(struct kvm_vcpu *vcpu,
>>>>> >>>>  
>>>>> >>>>  	if (p->is_write) {
>>>>> >>>>  		switch (r->reg) {
>>>>> >>>> +		case PMEVCNTR0_EL0 ... PMCCNTR_EL0: {
>>> >> Same problem as previously mentioned.
>>> >>
>>>>> >>>> +			val = kvm_pmu_get_counter_value(vcpu,
>>>>> >>>> +							r->reg - PMEVCNTR0_EL0);
>>>>> >>>> +			vcpu_sys_reg(vcpu, r->reg) += (s64)p->regval - val;
>>>>> >>>> +			break;
>>>>> >>>> +		}
>> > 
>> > If I use a handler to handle these accesses to PMEVCNTRn and PMCCNTR
>> > like below. It converts the register offset c14_PMEVCNTRn and c9_PMCCNTR
>> > to PMEVCNTRn_EL0 and PMCCNTR_EL0, uniformly uses vcpu_sys_reg and
>> > doesn't need to take care the big endian. What do you think about this?
>> > 
>> > static bool access_pmu_evcntr(struct kvm_vcpu *vcpu,
>> >                               struct sys_reg_params *p,
>> >                               const struct sys_reg_desc *r)
>> > {
>> >         u64 idx, reg, val;
>> > 
>> >         if (p->is_aarch32)
>> >                 reg = r->reg / 2;
> I'd prefer it if you actually decoded the reg itself. Something like:
> 
> 	if (p->is_aarch32) {
> 		if (r->CRn == 9 && r->CRm == 13)
> 			reg = (r->Op2 & 1) ? 0 : PMCCNTR_EL0;
> 		if (r->CRn == 14 && (r->CRm & 0xc) == 8) {
> 			reg = ((r->CRm & 3) << 2) & (r->Op2 & 7);
> 			reg += PMEVCNTR0_EL0;
> 		} else {
> 			BUG();
> 		}
> 	} else {
> 		....
> 	}
> 
> And then you can get rid of the c14_PMVCNTR* and c9_PMCCNTR macros.
> The only slightly ugly thing is this 0 value to represent PMXEVTYPER,
> but that's what we already have with your "default" clause below.
> 
Ok, thanks.
>> >         else
>> >                 reg = r->reg;
>> > 
>> >         switch (reg) {
>> >         case PMEVCNTR0_EL0 ... PMEVCNTR30_EL0: {
>> >                 idx = reg - PMEVCNTR0_EL0;
>> >                 break;
>> >         }
>> >         case PMCCNTR_EL0: {
>> >                 idx = ARMV8_CYCLE_IDX;
>> >                 break;
>> >         }
>> >         default:
>> >                 idx = vcpu_sys_reg(vcpu, PMSELR_EL0) & ARMV8_COUNTER_MASK;
>> >                 if (!pmu_counter_idx_valid(vcpu, idx))
>> >                         return true;
>> >                 reg = (idx == ARMV8_CYCLE_IDX) ? PMCCNTR_EL0 :
>> > PMEVCNTR0_EL0 + idx;
>> >                 break;
>> >         }
>> > 
>> >         val = kvm_pmu_get_counter_value(vcpu, idx);
>> >         if (p->is_write)
>> >                 vcpu_sys_reg(vcpu, reg) = (s64)p->regval - val;
> Maybe I don't have my head screwed in the right way, but as long as
> we're only using u64 quantities, why do we need this s64 cast?
> 
In case p->regval less than val.
For example, at the first time it writes 0x80000001 to
vcpu_sys_reg(vcpu, reg) and start a perf event which counts a value
10000. Then we want to start the same perf event with writing 0x80000001
to vcpu_sys_reg(vcpu, reg) too. At this time, p->regval(0x80000001) is
less than val(0x80000001 + 10000).

Thanks,
-- 
Shannon

WARNING: multiple messages have this Message-ID (diff)
From: Shannon Zhao <zhaoshenglong@huawei.com>
To: Marc Zyngier <marc.zyngier@arm.com>,
	<kvmarm@lists.cs.columbia.edu>, <christoffer.dall@linaro.org>
Cc: kvm@vger.kernel.org, will.deacon@arm.com,
	linux-arm-kernel@lists.infradead.org, shannon.zhao@linaro.org
Subject: Re: [PATCH v6 10/21] KVM: ARM64: Add access handler for PMEVCNTRn and PMCCNTR register
Date: Thu, 10 Dec 2015 21:23:20 +0800	[thread overview]
Message-ID: <56697CC8.40109@huawei.com> (raw)
In-Reply-To: <56696B00.6090909@arm.com>



On 2015/12/10 20:07, Marc Zyngier wrote:
> Hi Shannon,
> 
> On 10/12/15 11:36, Shannon Zhao wrote:
>> > Hi Marc,
>> > 
>> > On 2015/12/9 0:30, Marc Zyngier wrote:
>>> >> On 08/12/15 12:47, Shannon Zhao wrote:
>>>>> >>>> From: Shannon Zhao <shannon.zhao@linaro.org>
>>>>> >>>>
>>>>> >>>> Since the reset value of PMEVCNTRn or PMCCNTR is UNKNOWN, use
>>>>> >>>> reset_unknown for its reset handler. Add access handler which emulates
>>>>> >>>> writing and reading PMEVCNTRn or PMCCNTR register. When reading
>>>>> >>>> PMEVCNTRn or PMCCNTR, call perf_event_read_value to get the count value
>>>>> >>>> of the perf event.
>>>>> >>>>
>>>>> >>>> Signed-off-by: Shannon Zhao <shannon.zhao@linaro.org>
>>>>> >>>> ---
>>>>> >>>>  arch/arm64/kvm/sys_regs.c | 107 +++++++++++++++++++++++++++++++++++++++++++++-
>>>>> >>>>  1 file changed, 105 insertions(+), 2 deletions(-)
>>>>> >>>>
>>>>> >>>> diff --git a/arch/arm64/kvm/sys_regs.c b/arch/arm64/kvm/sys_regs.c
>>>>> >>>> index c116a1b..f7a73b5 100644
>>>>> >>>> --- a/arch/arm64/kvm/sys_regs.c
>>>>> >>>> +++ b/arch/arm64/kvm/sys_regs.c
>>>>> >>>> @@ -525,6 +525,12 @@ static bool access_pmu_regs(struct kvm_vcpu *vcpu,
>>>>> >>>>  
>>>>> >>>>  	if (p->is_write) {
>>>>> >>>>  		switch (r->reg) {
>>>>> >>>> +		case PMEVCNTR0_EL0 ... PMCCNTR_EL0: {
>>> >> Same problem as previously mentioned.
>>> >>
>>>>> >>>> +			val = kvm_pmu_get_counter_value(vcpu,
>>>>> >>>> +							r->reg - PMEVCNTR0_EL0);
>>>>> >>>> +			vcpu_sys_reg(vcpu, r->reg) += (s64)p->regval - val;
>>>>> >>>> +			break;
>>>>> >>>> +		}
>> > 
>> > If I use a handler to handle these accesses to PMEVCNTRn and PMCCNTR
>> > like below. It converts the register offset c14_PMEVCNTRn and c9_PMCCNTR
>> > to PMEVCNTRn_EL0 and PMCCNTR_EL0, uniformly uses vcpu_sys_reg and
>> > doesn't need to take care the big endian. What do you think about this?
>> > 
>> > static bool access_pmu_evcntr(struct kvm_vcpu *vcpu,
>> >                               struct sys_reg_params *p,
>> >                               const struct sys_reg_desc *r)
>> > {
>> >         u64 idx, reg, val;
>> > 
>> >         if (p->is_aarch32)
>> >                 reg = r->reg / 2;
> I'd prefer it if you actually decoded the reg itself. Something like:
> 
> 	if (p->is_aarch32) {
> 		if (r->CRn == 9 && r->CRm == 13)
> 			reg = (r->Op2 & 1) ? 0 : PMCCNTR_EL0;
> 		if (r->CRn == 14 && (r->CRm & 0xc) == 8) {
> 			reg = ((r->CRm & 3) << 2) & (r->Op2 & 7);
> 			reg += PMEVCNTR0_EL0;
> 		} else {
> 			BUG();
> 		}
> 	} else {
> 		....
> 	}
> 
> And then you can get rid of the c14_PMVCNTR* and c9_PMCCNTR macros.
> The only slightly ugly thing is this 0 value to represent PMXEVTYPER,
> but that's what we already have with your "default" clause below.
> 
Ok, thanks.
>> >         else
>> >                 reg = r->reg;
>> > 
>> >         switch (reg) {
>> >         case PMEVCNTR0_EL0 ... PMEVCNTR30_EL0: {
>> >                 idx = reg - PMEVCNTR0_EL0;
>> >                 break;
>> >         }
>> >         case PMCCNTR_EL0: {
>> >                 idx = ARMV8_CYCLE_IDX;
>> >                 break;
>> >         }
>> >         default:
>> >                 idx = vcpu_sys_reg(vcpu, PMSELR_EL0) & ARMV8_COUNTER_MASK;
>> >                 if (!pmu_counter_idx_valid(vcpu, idx))
>> >                         return true;
>> >                 reg = (idx == ARMV8_CYCLE_IDX) ? PMCCNTR_EL0 :
>> > PMEVCNTR0_EL0 + idx;
>> >                 break;
>> >         }
>> > 
>> >         val = kvm_pmu_get_counter_value(vcpu, idx);
>> >         if (p->is_write)
>> >                 vcpu_sys_reg(vcpu, reg) = (s64)p->regval - val;
> Maybe I don't have my head screwed in the right way, but as long as
> we're only using u64 quantities, why do we need this s64 cast?
> 
In case p->regval less than val.
For example, at the first time it writes 0x80000001 to
vcpu_sys_reg(vcpu, reg) and start a perf event which counts a value
10000. Then we want to start the same perf event with writing 0x80000001
to vcpu_sys_reg(vcpu, reg) too. At this time, p->regval(0x80000001) is
less than val(0x80000001 + 10000).

Thanks,
-- 
Shannon

  reply	other threads:[~2015-12-10 13:25 UTC|newest]

Thread overview: 126+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-08 12:47 [PATCH v6 00/21] KVM: ARM64: Add guest PMU support Shannon Zhao
2015-12-08 12:47 ` Shannon Zhao
2015-12-08 12:47 ` Shannon Zhao
2015-12-08 12:47 ` [PATCH v6 01/21] ARM64: Move PMU register related defines to asm/pmu.h Shannon Zhao
2015-12-08 12:47   ` Shannon Zhao
2015-12-08 12:47   ` Shannon Zhao
2015-12-08 12:47 ` [PATCH v6 02/21] KVM: ARM64: Define PMU data structure for each vcpu Shannon Zhao
2015-12-08 12:47   ` Shannon Zhao
2015-12-08 12:47   ` Shannon Zhao
2015-12-08 13:37   ` Marc Zyngier
2015-12-08 13:37     ` Marc Zyngier
2015-12-08 13:53     ` Will Deacon
2015-12-08 13:53       ` Will Deacon
2015-12-08 14:10       ` Marc Zyngier
2015-12-08 14:10         ` Marc Zyngier
2015-12-08 14:14         ` Shannon Zhao
2015-12-08 14:14           ` Shannon Zhao
2015-12-08 12:47 ` [PATCH v6 03/21] KVM: ARM64: Add offset defines for PMU registers Shannon Zhao
2015-12-08 12:47   ` Shannon Zhao
2015-12-08 12:47   ` Shannon Zhao
2015-12-08 12:47 ` [PATCH v6 04/21] KVM: ARM64: Add reset and access handlers for PMCR_EL0 register Shannon Zhao
2015-12-08 12:47   ` Shannon Zhao
2015-12-08 12:47   ` Shannon Zhao
2015-12-08 12:47 ` [PATCH v6 05/21] KVM: ARM64: Add reset and access handlers for PMSELR register Shannon Zhao
2015-12-08 12:47   ` Shannon Zhao
2015-12-08 12:47   ` Shannon Zhao
2015-12-08 12:47 ` [PATCH v6 06/21] KVM: ARM64: Add reset and access handlers for PMCEID0 and PMCEID1 register Shannon Zhao
2015-12-08 12:47   ` Shannon Zhao
2015-12-08 12:47   ` Shannon Zhao
2015-12-08 14:23   ` Marc Zyngier
2015-12-08 14:23     ` Marc Zyngier
2015-12-08 12:47 ` [PATCH v6 07/21] KVM: ARM64: PMU: Add perf event map and introduce perf event creating function Shannon Zhao
2015-12-08 12:47   ` Shannon Zhao
2015-12-08 12:47   ` Shannon Zhao
2015-12-08 15:43   ` Marc Zyngier
2015-12-08 15:43     ` Marc Zyngier
2015-12-09  7:38     ` Shannon Zhao
2015-12-09  7:38       ` Shannon Zhao
2015-12-09  7:38       ` Shannon Zhao
2015-12-09  8:23       ` Marc Zyngier
2015-12-09  8:23         ` Marc Zyngier
2015-12-09  8:23         ` Marc Zyngier
2015-12-08 12:47 ` [PATCH v6 08/21] KVM: ARM64: Add access handler for PMEVTYPERn and PMCCFILTR register Shannon Zhao
2015-12-08 12:47   ` Shannon Zhao
2015-12-08 12:47   ` Shannon Zhao
2015-12-08 16:17   ` Marc Zyngier
2015-12-08 16:17     ` Marc Zyngier
2015-12-08 12:47 ` [PATCH v6 09/21] KVM: ARM64: Add access handler for PMXEVTYPER register Shannon Zhao
2015-12-08 12:47   ` Shannon Zhao
2015-12-08 12:47   ` Shannon Zhao
2015-12-08 12:47 ` [PATCH v6 10/21] KVM: ARM64: Add access handler for PMEVCNTRn and PMCCNTR register Shannon Zhao
2015-12-08 12:47   ` Shannon Zhao
2015-12-08 12:47   ` Shannon Zhao
2015-12-08 16:30   ` Marc Zyngier
2015-12-08 16:30     ` Marc Zyngier
2015-12-10 11:36     ` Shannon Zhao
2015-12-10 11:36       ` Shannon Zhao
2015-12-10 11:36       ` Shannon Zhao
2015-12-10 12:07       ` Marc Zyngier
2015-12-10 12:07         ` Marc Zyngier
2015-12-10 13:23         ` Shannon Zhao [this message]
2015-12-10 13:23           ` Shannon Zhao
2015-12-10 13:23           ` Shannon Zhao
2015-12-08 12:47 ` [PATCH v6 11/21] KVM: ARM64: Add access handler for PMXEVCNTR register Shannon Zhao
2015-12-08 12:47   ` Shannon Zhao
2015-12-08 12:47   ` Shannon Zhao
2015-12-08 16:33   ` Marc Zyngier
2015-12-08 16:33     ` Marc Zyngier
2015-12-08 12:47 ` [PATCH v6 12/21] KVM: ARM64: Add reset and access handlers for PMCNTENSET and PMCNTENCLR register Shannon Zhao
2015-12-08 12:47   ` Shannon Zhao
2015-12-08 12:47   ` Shannon Zhao
2015-12-08 16:42   ` Marc Zyngier
2015-12-08 16:42     ` Marc Zyngier
2015-12-09  8:35     ` Shannon Zhao
2015-12-09  8:35       ` Shannon Zhao
2015-12-09  8:35       ` Shannon Zhao
2015-12-09  8:56       ` Marc Zyngier
2015-12-09  8:56         ` Marc Zyngier
2015-12-08 12:47 ` [PATCH v6 13/21] KVM: ARM64: Add reset and access handlers for PMINTENSET and PMINTENCLR register Shannon Zhao
2015-12-08 12:47   ` Shannon Zhao
2015-12-08 12:47   ` Shannon Zhao
2015-12-08 12:47 ` [PATCH v6 14/21] KVM: ARM64: Add reset and access handlers for PMOVSSET and PMOVSCLR register Shannon Zhao
2015-12-08 12:47   ` Shannon Zhao
2015-12-08 12:47   ` Shannon Zhao
2015-12-08 16:59   ` Marc Zyngier
2015-12-08 16:59     ` Marc Zyngier
2015-12-09  8:47     ` Shannon Zhao
2015-12-09  8:47       ` Shannon Zhao
2015-12-09  8:47       ` Shannon Zhao
2015-12-08 12:47 ` [PATCH v6 15/21] KVM: ARM64: Add reset and access handlers for PMUSERENR register Shannon Zhao
2015-12-08 12:47   ` Shannon Zhao
2015-12-08 12:47   ` Shannon Zhao
2015-12-08 17:03   ` Marc Zyngier
2015-12-08 17:03     ` Marc Zyngier
2015-12-09  9:18     ` Shannon Zhao
2015-12-09  9:18       ` Shannon Zhao
2015-12-09  9:18       ` Shannon Zhao
2015-12-09  9:49       ` Marc Zyngier
2015-12-09  9:49         ` Marc Zyngier
2015-12-09  9:49         ` Marc Zyngier
2015-12-08 12:47 ` [PATCH v6 16/21] KVM: ARM64: Add reset and access handlers for PMSWINC register Shannon Zhao
2015-12-08 12:47   ` Shannon Zhao
2015-12-08 12:47   ` Shannon Zhao
2015-12-08 12:47 ` [PATCH v6 17/21] KVM: ARM64: Add helper to handle PMCR register bits Shannon Zhao
2015-12-08 12:47   ` Shannon Zhao
2015-12-08 12:47   ` Shannon Zhao
2015-12-08 17:36   ` Marc Zyngier
2015-12-08 17:36     ` Marc Zyngier
2015-12-08 12:47 ` [PATCH v6 18/21] KVM: ARM64: Add PMU overflow interrupt routing Shannon Zhao
2015-12-08 12:47   ` Shannon Zhao
2015-12-08 12:47   ` Shannon Zhao
2015-12-08 17:37   ` Marc Zyngier
2015-12-08 17:37     ` Marc Zyngier
2015-12-08 12:47 ` [PATCH v6 19/21] KVM: ARM64: Reset PMU state when resetting vcpu Shannon Zhao
2015-12-08 12:47   ` Shannon Zhao
2015-12-08 12:47   ` Shannon Zhao
2015-12-08 12:47 ` [PATCH v6 20/21] KVM: ARM64: Free perf event of PMU when destroying vcpu Shannon Zhao
2015-12-08 12:47   ` Shannon Zhao
2015-12-08 12:47   ` Shannon Zhao
2015-12-08 12:47 ` [PATCH v6 21/21] KVM: ARM64: Add a new kvm ARM PMU device Shannon Zhao
2015-12-08 12:47   ` Shannon Zhao
2015-12-08 12:47   ` Shannon Zhao
2015-12-08 17:43   ` Marc Zyngier
2015-12-08 17:43     ` Marc Zyngier
2015-12-08 17:56 ` [PATCH v6 00/21] KVM: ARM64: Add guest PMU support Marc Zyngier
2015-12-08 17:56   ` Marc Zyngier

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=56697CC8.40109@huawei.com \
    --to=zhaoshenglong@huawei.com \
    --cc=christoffer.dall@linaro.org \
    --cc=kvm@vger.kernel.org \
    --cc=kvmarm@lists.cs.columbia.edu \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=marc.zyngier@arm.com \
    --cc=shannon.zhao@linaro.org \
    --cc=will.deacon@arm.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.