Re: GSOC'18 project description

On 13/05/18 15:20, Vidushi Vashishth wrote: Hi! >There is this as well .. >https://devel.rtems.org/ticket/3028 >It would be nice to have this updated. I think I would need the TICKET_EDIT_DESCRIPTION permission to make changes to an existing ticket. Or I

Re: GSOC'18 project description

Hi! >There is this as well .. >https://devel.rtems.org/ticket/3028 >It would be nice to have this updated. I think I would need the TICKET_EDIT_DESCRIPTION permission to make changes to an existing ticket. Or I could write about the changes in the comments section. On Thu, May 10, 2018 at 1:06

Re: GSOC'18 project description

On 9/5/18 6:23 pm, Sebastian Huber wrote: > On 09/05/18 07:56, Vidushi Vashishth wrote: >> Hi! >> >> Updating the progress. I have updated my wiki page, created two tickets and >> completed an introductory blog post. The next blog post containing an >> analysis >> of live tracing vs kernel level t

Re: GSOC'18 project description

>Ok, good. I would create a master ticket for this project based on the contents of the wiki page and your proposal. You can use the "Blocked By" and "Blocking" fields of the ticket to create >dependencies. >We should work on the documentation for the tracing right from the start. The tracing is f

Re: GSOC'18 project description

On 09/05/18 07:56, Vidushi Vashishth wrote: Hi! Updating the progress. I have updated my wiki page, created two tickets and completed an introductory blog post. The next blog post containing an analysis of live tracing vs kernel level tracing design considerations might take about two days. L

Re: GSOC'18 project description

Hello Vidushi, please notify us when you cannot work on your GSoC project for a couple of days.  From the GSoC Students FAQ: https://developers.google.com/open-source/gsoc/faq "How much time does GSoC participation take? You are expected to spend around 30+ hours a week working on your proj

Re: GSOC'18 project description

Hi! Updating the progress. I have updated my wiki page, created two tickets and completed an introductory blog post. The next blog post containing an analysis of live tracing vs kernel level tracing design considerations might take about two days. Let me know if you have any changes to suggest for

Re: GSOC'18 project description

Hello Sebastian! I apologise for the apparent inactivity. I have been caught up with preponed exams in college. I have a day off until my next exam so I will update update both my blogs, wiki documentation and create relevant tickets. Meanwhile I have been reading up barectf documentation and hav

Re: GSOC'18 project description

Hello Vidushi, I hope you are doing well. The wiki page and your blog are still empty. I didn't see any new tickets for this tracing GSoC project. I didn't see much activity from your side in the last couple of days. From the GSoC FAQ: https://developers.google.com/open-source/gsoc/2018/mento

Re: GSOC'18 project description

On 1/5/18 7:34 pm, Sebastian Huber wrote: > - Am 1. Mai 2018 um 5:38 schrieb Chris Johns chr...@rtems.org: > >> On 30/04/2018 20:05, Sebastian Huber wrote: 3) Investigate the importance of live tracing functionality and addition of kernel level tracing. I will design both possibiliti

Re: GSOC'18 project description

- Am 1. Mai 2018 um 5:38 schrieb Chris Johns chr...@rtems.org: > On 30/04/2018 20:05, Sebastian Huber wrote: >>> 3) Investigate the importance of live tracing functionality and addition of >>> kernel level tracing. I will design both possibilities and decide which one >>> to >>> work on by th

Re: GSOC'18 project description

On Mon, Apr 30, 2018 at 8:54 PM, Chris Johns wrote: > On 01/05/2018 08:35, Russell Haley wrote: > > > > Hi! I wanted to add that DTrace is an unmatched tool for kernel level > tracing. > > It provides "zero" overhead tracing by actually re-writing the in-memory > process > > images with instrumen

Re: GSOC'18 project description

On 01/05/2018 08:35, Russell Haley wrote: > > Hi! I wanted to add that DTrace is an unmatched tool for kernel level tracing. > It provides "zero" overhead tracing by actually re-writing the in-memory > process > images with instrumented instructions. In FreeBSD, it can be used to count > individu

Re: GSOC'18 project description

On 01/05/2018 02:09, Gedare Bloom wrote: > This is a good and important question. I think there should be a > section in this User Manual under Host Tools for the Babeltrace/Debug > tools that use the CTF output. There will also likely need to be > additions to the Classic API guide for "Configurin

Re: GSOC'18 project description

On 30/04/2018 20:05, Sebastian Huber wrote: >> 3) Investigate the importance of live tracing functionality and addition of >> kernel level tracing. I will design both possibilities and decide which one >> to >> work on by the end of phase 1 of my evaluation. > > I work currently on a new low leve

Fwd: GSOC'18 project description

-- Forwarded message -- From: Vidushi Vashishth Date: Mon, Apr 30, 2018 at 11:42 PM Subject: Re: GSOC'18 project description To: Gedare Bloom >Vidushi can add a task of creating a babeltrace formula for conversion from your custom format to CTF to facilitate unified

Re: GSOC'18 project description

On Mon, Apr 30, 2018 at 5:38 PM, Russell Haley wrote: > > > On Mon, Apr 30, 2018 at 3:05 AM, Sebastian Huber < > sebastian.hu...@embedded-brains.de> wrote: > >> Hello Vidushi, >> >> On 30/04/18 09:15, Vidushi Vashishth wrote: >> >>> Hello! >>> >>> I am Vidushi Vashishth, and I have been selected

Re: GSOC'18 project description

On Mon, Apr 30, 2018 at 3:05 AM, Sebastian Huber < sebastian.hu...@embedded-brains.de> wrote: > Hello Vidushi, > > On 30/04/18 09:15, Vidushi Vashishth wrote: > >> Hello! >> >> I am Vidushi Vashishth, and I have been selected for the Google Summer of >> Code'18 program. I look forward to a product

Re: GSOC'18 project description

On Mon, Apr 30, 2018 at 12:15 AM, Vidushi Vashishth wrote: > Hello! > > I am Vidushi Vashishth, and I have been selected for the Google Summer of > Code'18 program. I look forward to a productive and enriching summer with > the RTEMS community. > > I will be working on enhancement of the tracing

Re: GSOC'18 project description

On Mon, Apr 30, 2018 at 6:05 AM, Sebastian Huber wrote: > Hello Vidushi, > > On 30/04/18 09:15, Vidushi Vashishth wrote: >> >> Hello! >> >> I am Vidushi Vashishth, and I have been selected for the Google Summer of >> Code'18 program. I look forward to a productive and enriching summer with >> the

Re: GSOC'18 project description

Hello Vidushi, On 30/04/18 09:15, Vidushi Vashishth wrote: Hello! I am Vidushi Vashishth, and I have been selected for the Google Summer of Code'18 program. I look forward to a productive and enriching summer with the RTEMS community. I am looking forward to get some new insights into a net

GSOC'18 project description

Hello! I am Vidushi Vashishth, and I have been selected for the Google Summer of Code'18 program. I look forward to a productive and enriching summer with the RTEMS community. I will be working on enhancement of the tracing system of RTEMS, under the guidance of mentors: Gedare Bloom, Chris Johns