Gsoc2012: Atomic operation for RTEMS

[wei.a.yang at gmail.com]

Yeah, the implementation and interface should be separated. Most of atomic operations are used by score, so its CPU-independent interface should be defined within the score. Different architecture has different instructions to implement atomic operations, just like interrupt operations(enable and disable) which different architecture has different implementation. The interrupt implementation is placed within score/cpu, I also intend to place the implementation of atomic operations to score/cpu.

在 2012-5-22，15:14，Sebastian Huber <sebastian.huber at embedded-brains.de> 写道：

> On 05/21/2012 10:23 PM, Gedare Bloom wrote:
>> My guess is the interface will be primarily internal at first
>> (something within score) and the implementation has to live in some
>> CPU-dependent layer such as libcpu. You can refer to the "cache
>> manager" for an idea of what I mean and how you might go about
>> implementing a split interface and implementation.
> 
> We should avoid the libcpu here since the atomic operations are normally part of the instruction set and not a particular CPU core.  The right place is "cpukit/score/cpu".
> 
> -- 
> Sebastian Huber, embedded brains GmbH
> 
> Address : Obere Lagerstr. 30, D-82178 Puchheim, Germany
> Phone   : +49 89 18 90 80 79-6
> Fax     : +49 89 18 90 80 79-9
> E-Mail  : sebastian.huber at embedded-brains.de
> PGP     : Public key available on request.
> 
> Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.
> _______________________________________________
> rtems-devel mailing list
> rtems-devel at rtems.org
> http://www.rtems.org/mailman/listinfo/rtems-devel