On Fri, 30 Oct 2015 14:21:50 +0800
Shannon Zhao wrote:
> From: Shannon Zhao
>
> Since the reset value of PMXEVTYPER is UNKNOWN, use reset_unknown or
> reset_unknown_cp15 for its reset handler. Add access handler which
> emulates writing and
On 2015/12/1 2:12, Marc Zyngier wrote:
> On Fri, 30 Oct 2015 14:21:50 +0800
> Shannon Zhao wrote:
>
>> > From: Shannon Zhao
>> >
>> > Since the reset value of PMXEVTYPER is UNKNOWN, use reset_unknown or
>> > reset_unknown_cp15 for its reset
Hi Shannon,
On 10/30/2015 02:21 AM, Shannon Zhao wrote:
> From: Shannon Zhao
>
> Since the reset value of PMXEVTYPER is UNKNOWN, use reset_unknown or
> reset_unknown_cp15 for its reset handler. Add access handler which
> emulates writing and reading PMXEVTYPER register.
On 2015/11/3 4:54, Christopher Covington wrote:
> Hi Shannon,
>
> On 10/30/2015 02:21 AM, Shannon Zhao wrote:
>> From: Shannon Zhao
>>
>> Since the reset value of PMXEVTYPER is UNKNOWN, use reset_unknown or
>> reset_unknown_cp15 for its reset handler. Add access
From: Shannon Zhao
Since the reset value of PMXEVTYPER is UNKNOWN, use reset_unknown or
reset_unknown_cp15 for its reset handler. Add access handler which
emulates writing and reading PMXEVTYPER register. When writing to
PMXEVTYPER, call kvm_pmu_set_counter_event_type to