GSoC 2018 (x86_64, pc386, SMP improvements, rump kernels)

[Joel Sherrill]

On Mar 13, 2018 1:36 AM, "Sebastian Huber" <
sebastian.huber at embedded-brains.de> wrote:

On 12/03/18 21:20, Gedare Bloom wrote:

> Since I'm pretty keen on RTEMS, I think I'll have a 2nd proposal too, which
>> I'll decide and discuss with you guys soon, hopefully! (Perhaps the
>> tracing
>> or the APA scheduling projects).
>>
>> That's fine.  I don't think APA by itself is enough for the summer.
>
>
The strong APA scheduler was a GSoC project last year. Unfortunately the
student got ill and could not really work on it.

I think a ready to use tracing framework with good support from standard
tools would be quite nice for RTEMS application development. I have some
network stack performance issues which are probably more easy to track down
with such a tool ;-)


The  Common Trace Format (CTF) project is the one I steering students to
for this use case. It is what integrates into Eclipse and lets you use the
Linux Trace Toolkit (LTTNG). That tool visualizes trace logs, can do it
live or from logs, and has built-in capability to detect some behavioral
errors based on logged event patterns.

The cousin of this is the TCF project for remote debugging and target
interaction. Also used by Eclipse.

As far as I can tell, those are the two pieces required to give us a really
nice and complete Eclipse environment.


-- 
Sebastian Huber, embedded brains GmbH

Address : Dornierstr. 4, D-82178 Puchhe
<https://maps.google.com/?q=%0AAddress+:+Dornierstr.+4,+D-82178+Puchhe&entry=gmail&source=g>im,
Germany
Phone   : +49 89 189 47 41-16
Fax     : +49 89 189 47 41-09
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.

_______________________________________________
devel mailing list
devel at rtems.org
http://lists.rtems.org/mailman/listinfo/devel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/devel/attachments/20180313/8e9ee21f/attachment-0002.html>