[ofw] RE: [PATCH] NDProvider: Use private heap for memory allocations

[Sean Hefty]

>The kernel driver is what secures the memory.  If you want to be able to use
>the SecureMemoryCacheCallback functionality provided by the OS, you must abide
>by the rules for the callback: you can't touch the heap for which memory is
>being freed.  If you don't want to play by those OS rules, you can't cache
>memory registrations.

I'm not sure I understand this correctly.  The problem is that the library doing
the caching is trying to deregister the memory from within the callback,
correct?  Would moving the deregister to a different thread solve the problem?