On 8/03/2014 3:45 am, Gedare Bloom wrote:
This will make the protected Chain API stuck (for now, possibly
forever) with coarse-grained locks,
Yeap.
but users can define their own
fine-grained locking implementations of chains using unprotected chain
API calls?
Working is the first thing the
This will make the protected Chain API stuck (for now, possibly
forever) with coarse-grained locks, but users can define their own
fine-grained locking implementations of chains using unprotected chain
API calls?
I think this is acceptable.
Gedare
On Fri, Mar 7, 2014 at 11:12 AM, Sebastian Huber
Hello,
I am glad that we had no RTEMS 4.11 release yet. I have to revisit the
RTEMS chain API.
This solution was a bad mistake as it runs out now:
http://git.rtems.org/rtems/commit/cpukit/sapi/include/rtems/chain.h?id=1215fd4d9426a59d568560e9a485628560363133
In order to support profiling of
