> Date: Mon, 10 Mar 2014 11:29:13 +
> Subject: Re: linux kernel flush_cache_all behaviour on a Big.LITTLE system
> From: karim.allah.ah...@gmail.com
> To: catalin.mari...@arm.com
> CC: linaro-dev@lists.linaro.org
>
> On Mon, Mar 10, 2014 at 10:52 AM, Catalin Marinas
>
On Mon, Mar 10, 2014 at 10:52 AM, Catalin Marinas
wrote:
> On Mon, Mar 10, 2014 at 10:44:05AM +, karim.allah.ah...@gmail.com wrote:
>> I have two questions:
>>
>> 1- I was wondering what should be the expected semantics of
>> "flush_cache_all" on a Big.LITTLE architecture.
>>
>> I can see that
On Mon, Mar 10, 2014 at 10:44:05AM +, karim.allah.ah...@gmail.com wrote:
> I have two questions:
>
> 1- I was wondering what should be the expected semantics of
> "flush_cache_all" on a Big.LITTLE architecture.
>
> I can see that the implementation of this function under linux kernel
> is doi
Hello,
I have two questions:
1- I was wondering what should be the expected semantics of
"flush_cache_all" on a Big.LITTLE architecture.
I can see that the implementation of this function under linux kernel
is doing the following:
a- Read the value of LoC ( level of coherency )
b- Flush each le
