• Locked Locked
  • Replies 8 replies
  • Subscribers 120 subscribers
  • Views 5159 views
  • Users 0 members are here
Options
Related
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Cortex A8 preload engine (PLE) error

Ted Middleton
Note: This was originally posted on 24th November 2011 at http://forums.arm.com

I have a user-mode Linux application running on a Cortex-A8 (a TI 8148 Davinci chip). I have a shared memory region that I'm using to communicate data back and forth between the ARM core and the TI c674x DSP. The shared memory region is a ring buffer made of 32k segments (the size of the 8148's L2 cache ways). I've locked down 3 of the L2 cache ways and I'm trying to use the L2 PLE (preload engine) - the L2 feature accessed through coprocessor 15 c11 - to asynchronously preload and writeback the ring buffer segments. The ring buffer itself is located in physically and virtually contiguous memory - we're using TI's cmem module to allocate out of a memory hole. Moreover, I've checked the linux struct page flags for the ring buffer pages and they seem to all be uniform and fairly kosher. Plain-vanilla loads and stores from the ring buffer work just fine, as do coprocessor 15 based cache writeback operations (performed in privileged mode, of course).

Anyways, everything goes quite nicely for a while (anywhere from 3 to 10 PLE transfers complete successfully), until a PLE transfer errors-out at a page boundary. It's a different page boundary (both virtual and physical address) each time, and it's a different number of ring buffer segments and a different number of pages into the ring buffer segment each time this happens. The error itself, from table 3-132 in the ARM Cortex-A8 Technical Reference Manual, is "b1000101", or "translation fault, section".

Does anyone know what this error means? At first I thought that maybe it was because the page was marked as uncached, but looking at the page properties (with /proc/kpageflags), that doesn't seem to be the case.

Edit: One more detail - this failure only happens with preload operations - not writebacks. Or at least I haven't seen it happen with a writeback yet.
Parents
  • Note: This was originally posted on 29th November 2011 at http://forums.arm.com


    Or you can  allocate the shared memory in the kernel space, since for every Linux process, the kernel space shared the same MMU table entries.


    Yes - I considered this too, but I'm not sure my Linux kernel-fu is quite advanced enough yet to accomplish this. We've been using a /dev/mem -like tool that TI provides called cmem to map contiguous memory chunks, and it doesn't provide the ability to use kernel logical mappings - just user mappings.
Reply
  • Note: This was originally posted on 29th November 2011 at http://forums.arm.com


    Or you can  allocate the shared memory in the kernel space, since for every Linux process, the kernel space shared the same MMU table entries.


    Yes - I considered this too, but I'm not sure my Linux kernel-fu is quite advanced enough yet to accomplish this. We've been using a /dev/mem -like tool that TI provides called cmem to map contiguous memory chunks, and it doesn't provide the ability to use kernel logical mappings - just user mappings.
Children
No data