On 03.02.2016 16:38, Peter Maydell wrote:
> System registers might have access requirements which need to
> be described via a CPAccessFn and which differ for reads and
> writes. For this to be possible we need to pass the access
> function a parameter to tell it whether the access being checked
>
On Wed, Feb 03, 2016 at 01:38:39PM +, Peter Maydell wrote:
> System registers might have access requirements which need to
> be described via a CPAccessFn and which differ for reads and
> writes. For this to be possible we need to pass the access
> function a parameter to tell it whether the ac
On 5 February 2016 at 16:17, Alex Bennée wrote:
>
> Peter Maydell writes:
>> I haven't measured, no, but since there are only 3 arguments the
>> third argument is going to be in a register on any host architecture
>> we care about, which means the overhead is just going to be a single
>> "load co
Peter Maydell writes:
> On 5 February 2016 at 16:17, Alex Bennée wrote:
>>
>> Peter Maydell writes:
>>> I haven't measured, no, but since there are only 3 arguments the
>>> third argument is going to be in a register on any host architecture
>>> we care about, which means the overhead is just
Peter Maydell writes:
> On 5 February 2016 at 14:20, Alex Bennée wrote:
>>
>> Peter Maydell writes:
>>> -typedef CPAccessResult CPAccessFn(CPUARMState *env, const ARMCPRegInfo
>>> *opaque);
>>> +typedef CPAccessResult CPAccessFn(CPUARMState *env,
>>> + const A
On 5 February 2016 at 14:20, Alex Bennée wrote:
>
> Peter Maydell writes:
>> -typedef CPAccessResult CPAccessFn(CPUARMState *env, const ARMCPRegInfo
>> *opaque);
>> +typedef CPAccessResult CPAccessFn(CPUARMState *env,
>> + const ARMCPRegInfo *opaque,
>> +
Peter Maydell writes:
> System registers might have access requirements which need to
> be described via a CPAccessFn and which differ for reads and
> writes. For this to be possible we need to pass the access
> function a parameter to tell it whether the access being checked
> is a read or a wr
System registers might have access requirements which need to
be described via a CPAccessFn and which differ for reads and
writes. For this to be possible we need to pass the access
function a parameter to tell it whether the access being checked
is a read or a write.
Signed-off-by: Peter Maydell
