Is this is normal behavior? Or suggest any other alternative.
Since flush_cache_all() consuming major portion of total execution time, I couldn't proceed with this. Is there any other way, which helps to clean cache area related to a particular kernel program space.
Note : Cortex A17 core, 1.25 GHz , supporting 32 KB I-cache, 32 KB D-cache, and 256 KB L2 cache, ARM@big-LITTLE architecture
CPU? Core? Mostoften you can flush only the dirty lines.
>CPU? Core?
Cortex A17 core, 1.25 GHz , supporting 32 KB I-cache, 32 KB D-cache, and 256 KB L2 cache,ARM@big-LITTLE architecture
One more core is there. But its entirely dedicated to some other processes.
>Mostoften you can flush only the dirty lines.
Could you please help me to know how to clean only dirty lines?
I suggest reading chapter "B2.2.7 Cache and branch predictor maintenance operations" of DDI0405C.d