mtl.ca> wrote:
> On Tue, 2018-07-03 at 07:50 +0530, Vidushi Vashishth wrote:
> > > 3. Clearly document your modifications in separate commit messages.
> >
> > > 4. Add a Makefile to build it automatically.
> >
> > I will push commits to a fork of the rtems
Hi!
I am sorry for the late update. I might not be able to make it due to a
prescheduled doctor's appointment. I will try to get in on the go.
I will update the progress on the wiki page as well. I will send a separate
progress mail on the mailing list if need be.
Thanks
On Mon, Jul 2, 2018 at 1
> On Mon, Jul 2, 2018 at 1:27 AM, Sebastian Huber
> wrote:
> > Hello Vidushi,
> >
> > On 29/06/18 09:44, Vidushi Vashishth wrote:
> >>
> >>
> >> >Could you please create a self-contained repository which
> >> contains
> &
should do?
References:
https://github.com/efficios/barectf/wiki/Using-barectf
Thanks
On Sun, Jul 1, 2018 at 7:12 AM, Chris Johns wrote:
>
> On 29 Jun 2018, at 5:44 pm, Vidushi Vashishth wrote:
>
> >Could you please create a self-contained repository which contains
>
components. CTF is a flexible
tracing format with a range of configurable datatypes. This allows CTF to
describe any binary structure. Also since CTF is a binary trace format it
is faster to write. The post processing (eg Trace Compass) and real time
monitoring tools available with it are valuabl
u, Jun 28, 2018 at 11:43 AM, Sebastian Huber <
sebastian.hu...@embedded-brains.de> wrote:
> On 28/06/18 07:42, Vidushi Vashishth wrote:
>
>> >which use case does this address? What is the connection to an RTEMS
>> application?
>> This converts the trace buffering of the f
These can be transported to the host and then viewed using Trace Compass.
I lost some time trying to figure things out on my own. I will be more
frequent in communicating places where I am stuck. Apologies for the same.
On Thu, Jun 28, 2018 at 10:42 AM, Vidushi Vashishth
wrote:
> >Run on
rtems/cpukit/libmisc/shell/main_rtrace.c*. It saves the raw trace buffer
to a file and then uses the logic of `program.c`
to convert it into CTF traces.
On Thu, Jun 28, 2018 at 10:07 AM, Chris Johns wrote:
> On 28/06/2018 13:48, Vidushi Vashishth wrote:
> >
> > Sorry for the delay
some errors that I am working on. I will push the
changes to the main_rtrace.c file in a couple of hours.
Thanks
On Wed, Jun 27, 2018 at 10:31 AM, Sebastian Huber <
sebastian.hu...@embedded-brains.de> wrote:
> Hello Vidushi,
>
> On 22/06/18 03:16, Vidushi Vashishth wrote:
>
Hi!
I have updated the weekly status of my work on the GSoC tracking page. Here
is a summary of it:
Progress so far:
- Still working on adding rtrace shell capability to convert RTEMS traces
into CTF. There has been progress which I will push to (
https://github.com/VidushiVashishth/rtems) by en
The latest trace documentation images patch is version 5.
Thanks
On Thu, Jun 14, 2018 at 7:47 PM, Vidushi Vashishth
wrote:
> - Updates #3454
> - This commit adds Tracing Framework Chapter in the RTEMS User Manual
> - It comprises of subchapters on RTEMS Trace Linker, Capture Engi
/tracing/captureengine.rst b/user/tracing/captureengine.rst
new file mode 100644
index 000..8eaed3b
--- /dev/null
+++ b/user/tracing/captureengine.rst
@@ -0,0 +1,169 @@
+.. comment SPDX-License-Identifier: CC-BY-SA-4.0
+
+.. comment: Copyright (c) 2018 Vidushi Vashishth
+.. comment: All rights
still apply. I suspect v7 will
> be mergeable.
>
> On Wed, Jun 13, 2018 at 9:18 AM, Gedare Bloom wrote:
> > I think we're almost there. ;) A bit more below:
> >
> > On Wed, Jun 13, 2018 at 5:22 AM, Vidushi Vashishth
> wrote:
> >> - Completed Trace Link
>Do we have PDF versions of the PNG images? PNG images are not really good
for PDF generation.
I downloaded the images from the RTEMS website :
https://devel.rtems.org/wiki/Developer/Tracing
Should I convert them to pdf and send?
On Wed, Jun 13, 2018 at 3:06 PM, Sebastian Huber <
sebastian.hu...
Removed white spaces
---
user/index.rst | 2 +
user/tracing/captureengine.rst | 169 ++
user/tracing/examples.rst | 183 +++
user/tracing/index.rst | 29 +++
user/tracing/introduction.rst | 104 +
user/tracing/tracelinker.rst | 498
review and let me know.
Thanks
On Wed, Jun 13, 2018 at 8:50 AM, Chris Johns wrote:
> On 13/06/2018 13:04, Vidushi Vashishth wrote:
> >
> > I have made the changes you suggested.
>
> Thanks.
>
> > I am still working on CTF support.
> >
> >>> +
- Completed Trace Linker Section
- Added Trace Examples section
- Removed CTF section
- Removed Use cases section
- Incorporated changes asked by Chris
---
user/index.rst | 2 +
user/tracing/captureengine.rst | 182 +++
user/tracing/examples.rst | 185 +++
d, Jun 13, 2018 at 7:26 AM, Chris Johns wrote:
> Hi,
>
> This documentation looks good and I welcome this being done and added to
> the
> RTEMS project.
>
> I have some comments below I hope are easy to resolve.
>
> Thanks
> Chris
>
> On 13/06/2018 11:23, V
I was using Sublime text. It appeared okay on the editor. I have changed my
editor and sent another patch.
Thanks.
On Tue, Jun 12, 2018 at 9:46 PM, Gedare Bloom wrote:
> On Tue, Jun 12, 2018 at 11:15 AM, Vidushi Vashishth
> wrote:
> >
> > Adjusted line length to 79-80
---
user/index.rst | 2 +
user/tracing/captureengine.rst | 184 ++
user/tracing/examples.rst | 12 ++
user/tracing/index.rst | 29 +
user/tracing/introduction.rst | 182 ++
user/tracing/tracelinker.rst | 287 ++
Adjusted line length to 79-80
---
user/index.rst | 2 +
user/tracing/captureengine.rst | 188 ++
user/tracing/examples.rst | 12 ++
user/tracing/index.rst | 33 +
user/tracing/introduction.rst | 184 ++
user/tra
Hi!
>in case you receive comments for your patches the highest priority should
be to fix the problems with the patches and send the next revision of the
patch to the list, e.g. fixing trivial things like the line ?>length should
be done in a couple of minutes. If you think a comment is invalid or
Hi!
Updating the status on the tracing project. I am working on a ctftrace
function in the main_rtrace.c file in rtems source code which will use the
libbabeltrace C API to convert the trace buffers and print the final CTF
onto the console. I am using a static metadata specific to the fileio
sampl
>The formatting is the Emacs default for ReST. It would be nice to maintain
that format.
Oh yes I will fix that.
On Sun, Jun 10, 2018 at 5:56 PM, Chris Johns wrote:
>
> > On 10 Jun 2018, at 8:32 pm, Gedare Bloom wrote:
> >
> > I can't give a detailed review, but one possible problem I notice
- Incorporated suggested changes (except making use case example as close to
the actual output)
- Added trace linker section (to be completed)
- Added capture engine section
- Added trace buffering and printk trace generation in introduction
- Added trace examples section (to be completed)
The on
t;a");
fprintf (fp, ">>> %s (0x%08x)\n", func_name, func_addr);
fclose(fp);
}
Is there something wrong with this approach?
On Thu, Jun 7, 2018 at 2:00 PM, Vidushi Vashishth
wrote:
> Hi Sebastian.
>
>
>> I still have problems to see the big picture. W
Hi Sebastian.
> I still have problems to see the big picture. Would it be possible to
> implement both approaches using a simple example?
I am working on the babeltrace approach and using the fileio test case to
track entry and exit of malloc, calloc, realloc and free functions. I will
have som
ectly in RTEMS if modification to babeltrace source
> code would be required. I think it would be simpler to upstream your
> changes that way.
>
> [1] http://tracecompass.org/
>
> Guillaume
>
> Vidushi Vashishth a écrit :
>
>
> Hi!
>>
>> I have written
Hi!
I have written a blog post (https://vidushivashishth.github.io/sixthpost/)
summarizing two approaches to CTF generation that I can employ at this
point. I prefer on working with the barectf approach. The only blocker that
exists with this approach is deciding on a YAML configuration [1] for
d
I am just sending a revised version with incorporations of your
>> suggestions. I will create a fresh version 2 patch after everyone has
>> reviewed.
>>
>
> If you send revised version, then please send them as a separate patch
> with a new version. You can mention in the commit message what you ch
5, 2018 at 9:10 PM, Vidushi Vashishth
wrote:
> ---
> user/index.rst| 2 +
> user/tracing/development.rst | 12 ++
> user/tracing/index.rst| 25
> user/tracing/introduction.rst | 90 ++
> +
---
user/index.rst| 2 +
user/tracing/development.rst | 12 ++
user/tracing/index.rst| 25
user/tracing/introduction.rst | 90 +++
user/tracing/usecases.rst | 77
5 files cha
---
linkers/rtld-trace-buffer.ini | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/linkers/rtld-trace-buffer.ini b/linkers/rtld-trace-buffer.ini
index af9fc31..c17f2f1 100644
--- a/linkers/rtld-trace-buffer.ini
+++ b/linkers/rtld-trace-buffer.ini
@@ -26,6 +26,8 @@ buffer-l
---
linkers/rtld-trace-buffer.ini | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/linkers/rtld-trace-buffer.ini b/linkers/rtld-trace-buffer.ini
index ee68d55..c17f2f1 100644
--- a/linkers/rtld-trace-buffer.ini
+++ b/linkers/rtld-trace-buffer.ini
@@ -27,6 +27,7 @@ header = "#i
= "#include "
header = "#include "
header = "#include "
header = "#include "
+header = "#include "
[trace-buffer-tracers]
code = <<Real_priority.priority;
}
--
2.7.4
On Wed, May 30, 2018 at 7:24 PM, Vidushi Vashishth
wrote:
> &
d in it. I don't know if the convention has changed but I
stuck with how it was done in the configuration files of the trace linker.
On Wed, May 30, 2018 at 7:05 PM, Amaan Cheval
wrote:
> On Wed, May 30, 2018 at 6:33 PM, Vidushi Vashishth
> wrote:
> > Could you please change
7;t work.
On Wed, May 30, 2018 at 10:59 AM, Sebastian Huber <
sebastian.hu...@embedded-brains.de> wrote:
>
>
> On 29/05/18 17:36, Vidushi Vashishth wrote:
>
>> ---
>> linkers/rtld-trace-buffer.ini | 5 +++--
>> 1 file changed, 3 insertions(+), 2 deletions(-
Thats alright no problem! I will begin work on the documentation.
On Wed, May 30, 2018 at 4:59 PM, Sebastian Huber <
sebastian.hu...@embedded-brains.de> wrote:
> On 30/05/18 13:27, Vidushi Vashishth wrote:
>
>> Hi Sebastian!
>>
>> Yes I have been working on the
Hi Sebastian!
Yes I have been working on the documentation. I wrote a blog about the the
tracing framework use cases a while ago. It can be seen here
https://vidushivashishth.github.io/Third-post-copy/
I will write a blog about trace buffer generation which would explain all
the questions you have
Hello!
I am in the process of writing a CTF generator configuration file. This
will be used in converting trace data into Common Trace Format. I am
following the flow of events as described in [1] for the conversion
process. Have there been previous attempts to create CTF generator
configuration?
Hi!
Just updating that I have sent a patch which fixes the trace buffer
generation. I am now able to generate trace buffers for the fileio sample
testcase. I will begin work on CTF conversion now.
Thanks,
Vidushi
On Tue, May 29, 2018 at 1:00 PM, Vidushi Vashishth
wrote:
> Hey Sebast
---
linkers/rtld-trace-buffer.ini | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/linkers/rtld-trace-buffer.ini b/linkers/rtld-trace-buffer.ini
index af9fc31..ee68d55 100644
--- a/linkers/rtld-trace-buffer.ini
+++ b/linkers/rtld-trace-buffer.ini
@@ -26,6 +26,7 @@ buffer-lo
Hey Sebastian!
Yes I have been working on the trace linker the past week. It is outdated
and needs improvements. A lot of my work depends on me fixing the trace
linker. I had informed about this last week during the meeting. I thought I
would update you as soon as I make progress. Nevertheless the
Hey!
I did take note of some. I think it should not take too much time to
document these. I will surely do this after I am done with running my CTF
conversion formula on the linux system.
Best,
Vidushi
On Tue, May 22, 2018 at 3:23 PM, Chris Johns wrote:
> On 22/5/18 1:48 am, Vidushi Vashis
w.
On Mon, May 21, 2018 at 4:04 PM, Sebastian Huber <
sebastian.hu...@embedded-brains.de> wrote:
> Hello Vidushi,
>
> do you already have something that we can try out?
>
> - Vidushi Vashishth schrieb:
> > Hi!
> >
> > As asked by my mentor, I am going to
ts start to do this. Thanks for the update!
>
> On Mon, May 14, 2018 at 9:12 PM, Vidushi Vashishth
> wrote:
> > Hi!
> >
> > As asked by my mentor, I am going to post my weekly project target on the
> > mailing list every Monday. For this week I have the fol
Hi!
As asked by my mentor, I am going to post my weekly project target on the
mailing list every Monday. For this week I have the following planned:
1) Develop use cases (common development problems catered to, etc) for the
rtems tracing support and identify what all needs to be implemented aroun
of my current goals (integration of barectf, transport mechanism to
host, live tracing) in place of it?
Regards,
Vidushi Vashishth
On Mon, Mar 26, 2018 at 12:17 PM, Sebastian Huber <
sebastian.hu...@embedded-brains.de> wrote:
> On 23/03/18 16:28, Gedare Bloom wrote:
>
>> Hel
Hi!
I have uploaded my final proposal pdf for GSOC'18. I have tried to
incorporate all the comments made. PFA the final draft of the proposal.
Thanks for being such a wonderful community! I enjoyed every bit of the
application process.
Warm regards,
Vidushi Vash
Hello!
>>We should focus on basic functionality and this is interrupt entry/exit
and thread switching. This should work out of the box without having to
compile RTEMS with specialized configuration options. It should work via a
serial line and network (UDP I guess). It should also support SMP mach
Hi!
I apologise for the delay in submission. Was caught up with college project
submission.
PFA my proposal application for GSOC'18. I would appreciate insight and
suggestions.
Best,
Vidushi Vashishth
GSOC_proposal_Vidushi_runtime_tracing
<https://docs.google.com/do
Mon, Mar 19, 2018 at 11:20 AM, Chris Johns wrote:
> On 19/03/2018 03:44, Joel Sherrill wrote:
> > On Mar 18, 2018 6:48 AM, "Vidushi Vashishth" > <mailto:reachv...@gmail.com>> wrote:
> >
> > Hello!
> >
> > I am hoping to apply to Gsoc'
Hello!
I am hoping to apply to Gsoc'18 for the runtime tracing project. I am
following the RTEMS tracing documentation [1] and have been trying to run
the fileio trace sample to familiarise with how traces are generated. I
have set the rtems-path to the installed BSP erc32 in the fileio-trace.ini.
3/18 2:31 pm, Vidushi Vashishth wrote:
> >>I have been testing on a range of MacOS versions over the years and I
> have not
> > seen any issues report. If you have seen issues or you know of reports
> please
> > let me know.
> >
> > I was able to setup the envi
>I have been testing on a range of MacOS versions over the years and I have
not
seen any issues report. If you have seen issues or you know of reports
please
let me know.
I was able to setup the environment successfully yesterday. Though in the
process I had another error which I managed to deal w
em (at least on the surface). macOS does come
>> with
>> Python built-in, but I don't believe that's good enough for development
>> (vague memories only of issues) - have you installed Python separately
>> too?
>>
>> If so, could you confirm that you hav
Hello!
I was trying to set up the sparc/erc32 bsp on a new system and was
following the quickstart on the user manual. Though I have successfully
done this before, this time its throwing an error. PFA the rsb log file
with the error report. I was doing this to run the trace buffering
examples.
Wh
Hello!
I am Vidushi Vashishth from Netaji Subhas Institute of Technology, Delhi
and I intend to participate in the selection procedure for GSOC'18. I have
already submitted the Hello world patch. The past couple of days I have
been going through the open projects and I am interested in the
n, Jan 15, 2018 at 2:20 PM, Christian Mauderer <
> christian.maude...@embedded-brains.de> wrote:
>
>> - Ursprüngliche Mail -
>> > Von: "Vidushi Vashishth"
>> > An: "RTEMS Devel"
>> > Gesendet: Montag, 15. Januar 2018 06:17:53
&g
Hi!
I have the hello world patch and screenshot. Whom should I send it to?
Best,
Vidushi
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
60 matches
Mail list logo
