GSoC 2016 Interested in Tracing was Re:

[vivek kukreja]

Hello All,

I am very sorry for the late response. I have my exams starting this week,
until the end of the month. I should be able to contribute full-time to the
project during my vacations after the exam.

I have made changes to the document to provide more details about my
approach and deliverables in each phase. I hope I have answered most of the
questions from Joel.

Isaac, I have finally managed to download the source code from GIT on my
laptop. It seems that the university network was blocking traffic over GIT
protocol. I am now using a private internet connection to download source
code. So far, I was using the 4.11 code that I had downloaded from FTP. I
will soon port my changes to 4.12 and provide you a patch to look at.

Please let me know any concerns you might have, that I can resolve before
the acceptance deadline. I am really hoping to get accepted, and am looking
forward to working with you on this project.

Regards,
Vivek

On Mon, Apr 4, 2016 at 2:48 PM, Isaac Gutekunst <isaac.gutekunst at vecna.com>
wrote:

> Hi Vivek,
>
> Awesome progress! Sorry if I missed this, but do you have a GitHub
> repository, or some location where we can take a look at your work? I'm
> excited to see what changes you've made, even if they are not final yet.
>
> Isaac
>
>
> On 04/02/2016 10:30 AM, vivek kukreja wrote:
>
>> Hi Joel
>>
>> Sorry for the delay in responding and thank you for your comments on my
>> proposal.
>>
>> I would like to share my progress so far. I ran the fileio trace example
>> as described on the Trace Buffering page and started studying rtems-tld. I
>> made changes so that rtems-tld command auto-generates a CTF metadata file
>> for a given .ini file. I assumed each buffer as a different stream
>> containing events like buffer entry/exit, buffer argument, return values
>> etc.
>> Then i modified the buffer functions so they produce trace described by
>> above metadata.
>> I have also made changes to RTEMS shell utility rtrace so it can print
>> trace in CTF format for analysis.
>>
>> Thank you for highlighting user extensions. I haven't looked into these
>> yet. Can you point me to an example or a test where these are being used? I
>> will study these and update the document soon.
>>
>> Also, as you mentioned currently capture has to be paused for generating
>> trace. Im investigating how this can be addressed in the capture engine.
>> Any suggestions are appreciated. For example, im looking at a
>> producer-consumer solution for simultaneous read/write using 2 threads.
>>
>> I intend to keep the framework structure intact, and reuse the existing
>> functional tests. I will extend unit tests to test the new features
>> regarding CTF trace generation.
>>
>> By the mid-term evaluation, auto generation of metadata and trace
>> wrappers that produce CTF traces will be complete. The mid term deliverable
>> will have all the capabilites of current trace framework, alebit the trace
>> generated will be in CTF format. That will also allow us to decode these
>> traces in Babeltrace too.
>> I will also pay attention to creating good examples, documentation and
>> video demonstration as you have suggested.
>>
>> Im occupied with my college exams but I will put these details in the
>> document as soon as possible.
>>
>> Regards,
>> Vivek
>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/devel/attachments/20160416/31996960/attachment-0002.html>