Hello Himanshu,
I am interested in mentoring for Google Code-in 2019. Looking forward to be
a part of it.
Thanks
On Fri, 25 Oct, 2019, 1:32 am Vaibhav Gupta,
wrote:
> Hello everyone!
>
> I am interested in mentoring for Google Code-In 2019.
>
> -- Vaibhav Gupta
>
> On Fri, Oct 25, 2019, 1:28 A
> Hello Chris,
>
> I would like to check in the latest documentation patch from Ravindra as
> is and then work on top of it. Otherwise his work is not included in the
> project history
>
I have already sent the v5 of LTTng sched_switch documentation patch:
https://lists.rtems.org/pipermail/devel/
have removed the Trace Compass screen capture.
* I have REST numbering format.
* Removed the telent command. Telnet is not required for tracing.
* set the code block type to shell.
* Added few lines for raw-data.
Thanks
--
*Ravindra Kumar Meena*,
B. Tech. Computer Science and Engineering,
Indian
ated files are present. If othere files which
are not related to tracing are found then babeltrace will print error.
Here is the response from LTTng for the same:
https://lists.lttng.org/pipermail/lttng-dev/2019-June/029062.html
--
*Ravindra Kumar Meena*,
B. Tech. Computer Science and Engineeri
Hi,
Thanks for reviewing the draft:
https://docs.google.com/document/d/1Ucxb1HQTxMETDbqg432II1-pkGqqfymeZjZW2TVkUaI/edit
I have moved the report to permanent link:
https://rmeena840.github.io/final-report/
Thanks
--
*Ravindra Kumar Meena*,
B. Tech. Computer Science and Engineering,
Indian
;s patch, the user won't be able to receive the TCP
streams from the target.
>
> > If user has installed the tools then user can skip the step. I mentioned
> this
> > in step 1.
>
> Thanks. As stated I cannot review all that is happening without digging
> out the
> ot
t; tools?
>
'cd rtems-tools' means that the user has to run the command at
particular directory.
If user has installed the tools then user can skip the step. I mentioned
this
in step 1.
--
*Ravindra Kumar Meena*,
B. Tech. Computer Science and Engineering,
Indian Institute of Techno
ave access, ping me.
>
Please share the link of this doc. I don't have access to this file.
Please, grant me write access to this file.
--
*Ravindra Kumar Meena*,
B. Tech. Computer Science and Engineering,
Indian Institute of Technology (Indian School of Mines)
<https://www.iitism.ac
Hello all,
I have made the draft of my project report on google docs.
Please review the draft and let me know if any changes need to be made.
https://docs.google.com/document/d/1Ucxb1HQTxMETDbqg432II1-pkGqqfymeZjZW2TVkUaI/edit
Thank you
--
*Ravindra Kumar Meena*,
B. Tech. Computer Science
Hello Chris,
>
> sorry for the rush, but what do you think of this patch? I would like to
> integrate the tracing work of the GSoC project and this patch is a
> blocking point.
>
Please review the patches. This need to be integrated in master branch
before 19th August (GSoC ends). I have to prepar
Documentation patch review is pending:
https://lists.rtems.org/pipermail/devel/2019-August/027215.html
>
--
*Ravindra Kumar Meena*,
B. Tech. Computer Science and Engineering,
Indian Institute of Technology (Indian School of Mines)
<https://www.iitism.ac.in/>
027278.html
>
> Then you can rebase your work on top of it and send a single patch to
> devel@rtems.org for the normal patch review.
>
Okay. Thanks.
Let me know if any other coding optimization/style needed in code.
Thanks
--
*Ravindra Kumar Meena*,
B. Tech. Computer Science and Engi
/rmeena840/rtems-tools/commit/1ffbe7d5dcea741a3e7ceec8ded869d38c20081f
Have a look.
What's the procedure for getting code merged? Do I have to raise PR on
GitHub or simply send a patch on devel?
--
*Ravindra Kumar Meena*,
B. Tech. Computer Science and Engi
rtems-main.c coding style fix:
https://github.com/rmeena840/rtems-tools/commit/eeb2067783f7e375087bee913342ce3fecce7883
>
--
*Ravindra Kumar Meena*,
B. Tech. Computer Science and Engineering,
Indian Institute of Technology (Indian School of Mines)
<https://www.iitism.ac.in/>
i = get_api_of_id( cctx->thread_id_name[ item->cpu ].thread_id );
https://github.com/rmeena840/rtems-tools/commit/11cf7626e40a20c9bfaf889a94d51171519d6dc0
--
*Ravindra Kumar Meena*,
B. Tech. Computer Science and Engineering,
Indian Institute of Technology (Indian School of Mines)
<https://www.iitism.ac.in/>, Dhanbad
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
rtems-main.c cleanup:
https://github.com/rmeena840/rtems-tools/commit/61d5dc45e43f0998ad9305d565926090215a5bdc
Switch_event per CPU added:
https://github.com/rmeena840/rtems-tools/commit/8ffe8bd2adea27772a9ab0e578539dd99fa0174b
Have a look.
>
--
*Ravindra Kumar Meena*,
B. Tech. Compu
>
> > What to do for bound access for api_id? Should I use exit( EXIT_SUCCESS
> > ) for this?
>
> You ignore this item an continue.
>
Okay
https://github.com/rmeena840/rtems-tools/commit/24c7753238ab20fc8c002936657ee0f4c16a6e61
--
*Ravindra Kumar Meena*,
B. Te
--
*Ravindra Kumar Meena*,
B. Tech. Computer Science and Engineering,
Indian Institute of Technology (Indian School of Mines)
<https://www.iitism.ac.in/>, Dhanbad
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
rtems-main.c cleanup:
https://github.com/rmeena840/rtems-tools/commit/527fc0f2f3c971c21741b28b1f0ecde6efb6eb4a
Copyright added:
https://github.com/rmeena840/rtems-tools/commit/dc0cc02e805691bd0fd6a42abe4a0e068587c0ed
Have a look.
>
--
*Ravindra Kumar Meena*,
B. Tech. Computer Science
On Thu, Aug 8, 2019 at 1:06 PM Ravindra Kumar Meena
wrote:
> > Should I include whole metadata content in that char metadata[]?
>>
>> Yes, if everything is constant.
>>
> Okay
>
> https://github.com/rmeena840/rtems-tools/commit/13c81bfb3a72dd777507f3bf92a96ec
#x27;t
know why that is happening.
Because of this binary data at the end babeltrace is not able to read
events.
--
*Ravindra Kumar Meena*,
B. Tech. Computer Science and Engineering,
Indian Institute of Technology (Indian School of Mines)
<https://w
1.8 */\n\n");
> - fprintf(metadata, "typealias integer { size = 5; align = 1; signed =
> false; } := uint5_t;\
> + fwrite( metadata, sizeof( metadata ), 1, file );
>
Okay.
https://github.com/rmeena840/rtems-tools/commit/6ee5468224d70eda4147fb7739571ea91eac7b9c
Should
ing about typedef?
>
> >
> > Is there any coding style guideline mentioned somewhere to follow for
> > rtems-tools?
>
> This file should follow the RTEMS style:
>
> https://docs.rtems.org/branches/master/eng/coding.html
Thanks. I think first we should work on cod
somewhere to follow for
rtems-tools?
>
--
*Ravindra Kumar Meena*,
B. Tech. Computer Science and Engineering,
Indian Institute of Technology (Indian School of Mines)
<https://www.iitism.ac.in/>, Dhanbad
___
devel mailing list
devel@rtems
Code Cleanup:
https://github.com/rmeena840/rtems-tools/commit/f19ec63810347f6e532e13b1fb27002554344d3f
--
*Ravindra Kumar Meena*,
B. Tech. Computer Science and Engineering,
Indian Institute of Technology (Indian School of Mines)
<https://www.iitism.ac.in/>, D
serts in this path. Ignore items which have
> unexpected values.
>
Okay API is always returned in the range [ 1, 3 ]. Decrementing it by one
should be safe then.
https://github.com/rmeena840/rtems-tools/commit/8ff97b38970595f507e23f2a9a6e397ae1f70bb9
--
*Ravindra Kumar Meena*,
B. Tech. Co
om/rmeena840/rtems-tools/commit/6517c7b32f4dc063fd12dce02d5004741588ea28
The babeltrace and Trace Compass can now display event name :) :)
--
*Ravindra Kumar Meena*,
B. Tech. Computer Science and Engineering,
Indian Institute of Technology (Indian School of Mines)
<https://www.iitism.ac.in/>, Dhanbad
rom the line above.
>
I think this can be the right way to check bound access.
https://github.com/rmeena840/rtems-tools/commit/81bf2a9b9e57e7911d519c4719c5126e29a7adbe
--
*Ravindra Kumar Meena*,
B. Tech. Computer Science and Engineering,
Indian Institute of Technology (Indian Schoo
t_item() has done
its job?
And this table is not CPU specific so I am not sure in which CPU file
should I populate it?
--
*Ravindra Kumar Meena*,
B. Tech. Computer Science and Engineering,
Indian Institute of Technology (Indian School of Mines)
<ht
gt;
> +cctx->thread_id_name[ item->cpu ].name_index = 0;
>
> if the name_index was 1, is wrong. You have to increment it.
>
Done
https://github.com/rmeena840/rtems-tools/commit/8ceb3ccb97422044fb30b3c562fc736cf0686d48
--
*Ravindra Kumar Meena*,
B. Tech. Computer Science an
hm.
https://github.com/rmeena840/rtems-tools/commit/33c217642e36b91926dfd823e5b3b59974790084
--
*Ravindra Kumar Meena*,
B. Tech. Computer Science and Engineering,
Indian Institute of Technology (Indian School of Mines)
<https://www.iitism.ac.in/>, Dhanbad
_
;,item->data);
May be full information is not received in client-side.
--
*Ravindra Kumar Meena*,
B. Tech. Computer Science and Engineering,
Indian Institute of Technology (Indian School of Mines)
<https://www.iitism.ac.in/>, Dhanbad
___
devel mail
be:
{s,w,i,6,s,k, ,q,0,0,0,0,0,0,0,0}
For this decode, the value will be "swi6sk q". Right? This is exactly what
I am getting in Konsole.
--
*Ravindra Kumar Meena*,
B. Tech. Computer Science and Engineering,
Indian Institute of Technology (Indian School of Mines)
<h
bject Index: 70 Name: TNTc
Object Index: 71 Name: TNTd
Object Index: 72 Name: TNTe
Object Index: 73 Name: TNTD
Object Index: 74 Name: RCRD
Object Index: 75 Name: SHLL
Thread name is in the right order now.
--
*Ravindra Kumar Meena*,
B. Tech. Computer Science and Engineering,
Indian Institute of
s thing is taken care of by :
if( cctx->thread_names[ api_id ][ thread_id ][ i ] == 0x00 )
If thread_name is received for the same api_id and thread_id then it will
write only in empty char position.
I checked the value with the provided output. The value is the same but in
reverse order.
--
> eg.
> >
> >
> >
> >
> >
> >
> >
>
> This makes no sense to me. The thread id is fixed for a sequence of
> thread name events. From the thread id you get the API index and the
> object index.
>
Have made changes. Simplified the code.
es[api_id][thread_id][0..7], the second uses
> ctx->thread_names[api_id][thread_id][8..15]. The third and later are an
> error, just ignore it.
>
We can store the 16 char all at once then why are we doing this in two
parts.
My approach is like this:
Get the api_id from thread_id and f
ive the same thread_name. There is no need to
reverse. I checked the output. The values are the same.
snprintf( item_name_str, sizeof( item_name_str ), "%08"PRIx64, item->data
);
--
*Ravindra Kumar Meena*,
B. Tech. Computer Science and Engin
:
THREAD_ID:a01001e
THREAD_NAME:737769363a207461
THREAD_NAME:736b2071756575
Does this mean that the same thread_id have two thread_name? If so then
only one thread_name can be stored in
char thread_names[3][65536][THREAD_NAME_SIZE];
--
*Ravindra Kumar Meena*,
B. Tech. Computer Science and
ms-tools/commit/426c2d293f17e3d3150d50a7943a2d22ad382c47
I checked the output with/without it. The babeltrace and Trace Compass
displays the same output.
--
*Ravindra Kumar Meena*,
B. Tech. Computer Science and Engineering,
Indian Institute of Technology (Indian School of Mines)
<https://www.i
Now, I can get the [thread_id] and [thread_name] in print_item() but since
this information is not CPU specific so in which CPU should I store this
information?
>
--
*Ravindra Kumar Meena*,
B. Tech. Computer Science and Engineering,
Indian Institute of Technology (Indian School of Mines)
<
e for next_tid if the next thread is an idle thread.
>
Okay. I have added the idle thread condition in next_tid.
https://github.com/rmeena840/rtems-tools/commit/4e767dd71a7dc402edf7ac5e1ed78cdb49e09607
Have a look.
--
*Ravindra Kumar Meena*,
B. Tech. Computer Science and Engineering,
Indian
sponse, I shared with you previously.
https://lists.lttng.org/pipermail/lttng-dev/2019-July/029121.html
They had mentioned that
"My guess would be that prev_state is the previous state of the thread (TID)
"
So I think prev_state is for prev_tid only.
--
*Ravindra Kumar Meena*,
B. Tech.
>
> > I did following thing in print_item() but nothing is shown in the console
> > output:
> >
> > if(item->event == RTEMS_RECORD_THREAD_ID){
> >printf("this thing is present\n");
> > }
>
>
> I checked in a fix for this proble
{
printf("this thing is present\n");
}
--
*Ravindra Kumar Meena*,
B. Tech. Computer Science and Engineering,
Indian Institute of Technology (Indian School of Mines)
<https://www.iitism.ac.in/>, Dhanbad
___
devel mailing lis
D_ID:a010044
> *:0:THREAD_NAME:544e5461
> *:0:THREAD_ID:a010045
> *:0:THREAD_NAME:544e5462
> *:0:THREAD_ID:a010046
> *:0:THREAD_NAME:544e5463
> *:0:THREAD_ID:a010047
> *:0:THREAD_NAME:544e5464
> *:0:THREAD_ID:a010048
> *:0:THREAD_NAME:544e5465
> *:0:THREAD_ID:a010049
> *:0:
./build/misc/rtems-record -H 169.254.23.78 -p 1234 | head
or
./build/misc/rtems-record --input misc/record/qoriq_e6500_64.bin | head?
--
*Ravindra Kumar Meena*,
B. Tech. Computer Science and Engineering,
Indian Institute of Technology (Indian School of Mines)
<https://www.iitism.a
I have implemented the hash map for [thread_id]->[thread_name]. The hash
map stores the thread per cpu.
https://github.com/rmeena840/rtems-tools/commit/a8da9cc4aefc1cdb5d9634715601a96f69fa526a
Have a look.
--
*Ravindra Kumar Meena*,
B. Tech. Computer Science and Engineering,
Indian Instit
ent )
> >
> >
> > You can use C++ if this makes it easier for you.
> >
> > I will have to create separate c++ file for this.
>
> Please convert the entire record-main.c file to C++.
>
Okay. I will work on it after the previous task.
--
*Ravindra Kumar
vent_text( item->event )
> You can use C++ if this makes it easier for you.
>
I will have to create separate c++ file for this.
--
*Ravindra Kumar Meena*,
B. Tech. Computer Science and Engineering,
Indian Institute of Technology (Indian School of Mines)
<https://www.iitism.ac.in
gt; >
> > if so this can be done by calling:
> > rtems_record_event_text( item->event )
>
> Attached is a patch for RTEMS. The record server sends all thread names to
> the client after the header.
>
> For thread name changes and new threads we have to think about.
*Plan of the week:*
Last week I added the sched_switch in client-side. Trace compass can now
show more details of the trace now. I will continue to continue to work on
client-side.
--
*Ravindra Kumar Meena*,
B. Tech. Computer Science and Engineering,
Indian Institute of Technology (Indian School
n idea how
> we can do this?
>
With task name do you mean RTEMS_RECORD_THREAD_SWITCH_IN
and RTEMS_RECORD_THREAD_SWITCH_OUT?
if so this can be done by calling:
rtems_record_event_text( item->event )
--
*Ravindra Kumar Meena*,
B. Tech. Computer Science and Engineering,
Indian Institute of Techno
ot;, next_tid = 151060501, next_prio = 0
}
[19:16:31.180397048] (+0.34452) Record_Item sched_switch: { cpu_id = 5
}, { prev_comm = "09010015", prev_tid = 151060501, prev_prio = 0,
prev_state = 0, next_comm = "0a01002b", next_tid = 167837739, next_prio = 0
}
Both prev_* and next_* values are different.
--
*Ravindra Kumar Meena*,
B. Tech. Computer Science and Engineering,
Indian Institute of Technology (Indian School of Mines)
<https://www.iitism.ac.in/>, Dhanbad
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
ay. So this particular lttng sched_switch will have prev_* value
as RTEMS_RECORD_THREAD_SWITCH_OUT data and next_* value
as RTEMS_RECORD_THREAD_SWITCH_IN.
--
*Ravindra Kumar Meena*,
B. Tech. Computer Science and Engineering,
Indian Institute of Technology (Ind
--
*Ravindra Kumar Meena*,
B. Tech. Computer Science and Engineering,
Indian Institute of Technology (Indian School of Mines)
<https://www.iitism.ac.in/>, Dhanbad
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
ed_switch? Do you know what a software thread is?
>
I learned software thread in Java. I tried to implement thread in C. We
need '-lpthread' flag in gcc compiler to use the thread in C. Does this
flag needed to be included in wscript?
--
*Ravindra Kumar Meena*,
B. Tech. Computer Scie
.
* Added sched_switch in the metadata.
Next:
* Currently working on adding sched_switch in client-side.
Thanks
--
*Ravindra Kumar Meena*,
B. Tech. Computer Science and Engineering,
Indian Institute of Technology (Indian School of Mines)
<https://www.iitism.ac.in/>, D
}, { prev_comm = "09010014", prev_tid = 151060500, prev_prio = 0,
prev_state = 0, next_comm = "0a01002b", next_tid = 167837739, next_prio = 0
}
[19:16:31.180223920] (+0.49688) Record_Item sched_switch: { cpu_id = 5
}, { prev_comm = "09010015", prev_tid = 151060501,
value and second character is of next_comm value. Since we will
be writing just after receiving c(third row) we can't get d values.
For this, we should have d value so that we can write it in
RTEMS_RECORD_THREAD_SWITCH_IN event with next_comm value.
--
*Ravindra Kumar Meena*,
B. Tech. Com
es the
prev_* values and after this, it will enter in else part recursively
initializing prev_* and next_* values for the same CPU and write it in the
file.
--
*Ravindra Kumar Meena*,
B. Tech. Computer Science and Engineering,
Indian Institute of Technology (Indian School of
>
> All your state must be per-CPU otherwise you mix data from different CPUs.
>
Have made changes.
https://github.com/rmeena840/rtems-tools/commit/fac873672d5cd8fe3605ea7ac817ebaa4e8e4cdc
Have a look.
--
*Ravindra Kumar Meena*,
B. Tech. Computer Science and Engineering,
Indian Ins
223920] (+0.15326) Record_Item sched_switch: { cpu_id = 5
}, { prev_comm = "1ce0", prev_tid = 7392, prev_prio = 0, prev_state =
0, next_comm = "0a01002b", next_tid = 167837739, next_prio = 0 }
[19:16:31.180241405] (+0.17485) Record_Item sched_switch: { cpu_id = 5
}, { pr
37739", prev_tid = 167837739, prev_prio = 0,
prev_state = 0, next_comm = "5856", next_tid = 5856, next_prio = 0 }
[19:16:31.180241405] (+0.0) Record_Item sched_switch: { cpu_id = 5
}, { prev_comm = "151060501", prev_tid = 151060501, prev_prio = 0,
prev_state = 0
ary stream file.
--
*Ravindra Kumar Meena*,
B. Tech. Computer Science and Engineering,
Indian Institute of Technology (Indian School of Mines)
<https://www.iitism.ac.in/>, Dhanbad
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
>
Okay. Sure
>
> >
> > There is one problem here we need the next_comm and next_tid value
> > before actually next record item is generated in client-side.
>
> You need one sched_switch event per processor. The order of record
> events is fixed. You update the sched
the example.
There is one problem here we need the next_comm and next_tid value before
actually next record item is generated in client-side.
Thanks
--
*Ravindra Kumar Meena*,
B. Tech. Computer Science and Engineering,
Indian Institute of Technology (Indian School of Mines)
<ht
= 32; align = 8; signed = 1; encoding =
> none; base =
> 10; } _next_tid;
> integer { size = 32; align = 8; signed = 1; encoding =
> none; base =
> 10; } _next_prio;
> };
> };
>
Okay. We need to have the values of event fields in client-side. What
valu
s.
https://github.com/rmeena840/rtems-tools/commit/96b082a6a31a1ebf6ea05b475a7e6c8378e456e7
Have a look
Thanks
--
*Ravindra Kumar Meena*,
B. Tech. Computer Science and Engineering,
Indian Institute of Technology (Indian School of Mines)
<https://www.iitism.ac.in/>, Dhanbad
__
it
timestamp>
Now after this
<32-bit data> again <32-bit data> agina <
32-bit data>
I am not able to understand what this <32-bit data> is between every
>
> How is the id used? We are interested in the sched_switch events.
>
Okay
--
*Ravindra Kumar M
;
} align(8);
This is what I have tried.
https://github.com/rmeena840/rtems-tools/commit/b2ffc3d5b5ffd97075f1ed9028bcb8098e241e2b
Have a look. Please don't build it it's not working yet.
--
*Ravindra Kumar Meena*,
B. Tech. Computer Science and Engineering,
Indian Institute of Technolo
ide also. I think C does not have variant data type.
--
*Ravindra Kumar Meena*,
B. Tech. Computer Science and Engineering,
Indian Institute of Technology (Indian School of Mines)
<https://www.iitism.ac.in/>, Dhanbad
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
er =
216 ), data = 167837739 }
[19:16:31.180174232] (+0.0) Record_Item RTEMS_RECORDING_EVENT: {
cpu_id = 17 }, { events = ( "RTEMS_RECORD_THREAD_STACK_CURRENT" : container
= 209 ), data = 5856 }
--
*Ravindra Kumar Meena*,
B. Tech. Computer Science and Engineering,
Indi
NT" : container = 209 ), data = 7392 }
> 0 RTEMS_RECORDING_EVENT: { cpu_id = 17 }, { ns = 1044799, events = (
> "RTEMS_RECORD_THREAD_SWITCH_IN" : container = 215 ), data = 167837739 }
> 0 RTEMS_RECORDING_EVENT: { cpu_id = 17 }, { ns = 1064443, events = (
> "RTEMS_RECORD_THREAD_SWITC
t and metadata.
https://github.com/rmeena840/rtems-tools/commit/88a53f93865fb54f8bcf2afc323baba3feac98c3
https://github.com/rmeena840/rtems-tools/commit/2e4c130f42352df427ebafd7c36b1443f16c
Since our binary stream files do not have struct padding so both should be
equal in values.
Have a look.
T
lient_context.
>
Have made changes:
https://github.com/rmeena840/rtems-tools/commit/dcc4e814d5dd8ec2cbd6fc018a92c52e96f7851c
Have a look
--
*Ravindra Kumar Meena*,
B. Tech. Computer Science and Engineering,
Indian Institute of Technology (Indian School of Mines
https://github.com/rmeena840/rtems-tools/commit/9417aae5d19857489d93eba1c52bb94a7b2d67ec
https://github.com/rmeena840/rtems-tools/commit/6581dd57225ba3171886973b0182487c409f35d2
Have a look.
I added the dummy data at the starting of the file. So that only this part
of the file can be overwritten later after obtaining the relevan
ectory would look clean.
Isn't it needed?
>
> Please have a look at the fseek() function:
>
> http://man7.org/linux/man-pages/man3/fseek.3.html
Okay. I am not sure but won't this overwrite the old content in file? Since
we will be writing to the same file.
--
*Ravindr
.
--
*Ravindra Kumar Meena*,
B. Tech. Computer Science and Engineering,
Indian Institute of Technology (Indian School of Mines)
<https://www.iitism.ac.in/>, Dhanbad
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
seq_num;
unsigned long events_discarded;
uint32_t cpu_id;
};
timestamp values are needed in the client-side program. Where to obtain in
client side?
--
*Ravindra Kumar Meena*,
B. Tech. Computer Science and Engineering,
Indian Institute of Technology (Indian School of Mines)
<ht
--
*Ravindra Kumar Meena*,
B. Tech. Computer Science and Engineering,
Indian Institute of Technology (Indian School of Mines)
<https://www.iitism.ac.in/>, Dhanbad
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
;6a7715d0-b502-4c65-8678-6777ac7f755a";
byte_order = le;
packet.header := struct {
uint32_t magic;
uint8_t uuid[16];
uint32_t stream_id;
uint64_t stream_instance_id;
};
};
--
*Ravindra Kumar Meena*,
B. Tech
ficulty
> > in adding uuid in header. uuid is 128 a bit number which has 5 octets of
> > 8-4-4-4-12 bytes.
> [...]
>
--
*Ravindra Kumar Meena*,
B. Tech. Computer Science and Engineering,
Indian Institute of Technology (Indian School of Mines)
<https://www.iitism.ac.in/>, Dhan
> };
>
> Add a LTTNG compatible packet context:
>
> struct packet_context {
> uint64_clock_monotonic_t timestamp_begin;
> uint64_clock_monotonic_t timestamp_end;
> uint64_t content_size;
> uint64_t packet_size;
> uint64_t packet_seq_num;
> uns
ing to do with not properly closing the files in
> the record client.
>
With your, fix. This error is not occurring now. Thanks
--
*Ravindra Kumar Meena*,
B. Tech. Computer Science and Engineering,
Indian Institute of Technology (Indian School of Mines)
<
>
> I am pretty sure this is error is caused by something else. How many
> files do you open, how many do you close properly?
>
I did it in the end. Isn't it correct?
for( i = 0; i < RTEMS_RECORD_CLIENT_MAXIMUM_CPU_COUNT ; i++ ){
fclose( event_streams[ i ] );
}
--
*
acket. Either the trace data stream is corrupted
or metadata description does not match data layout.
[error] Reading event failed.
Error printing trace.
This might be happening because the last packet is not fully received in
the raw data file you pushed on my workplace.
--
*Ravindra Kumar Meena*
215 ), data =
648799898627506173 }
As you can see. It now includes cpu_id also.
--
*Ravindra Kumar Meena*,
B. Tech. Computer Science and Engineering,
Indian Institute of Technology (Indian School of Mines)
<https://www.iitism.ac.in/>, Dhanbad
___
part of the event header, so why then the duplication?
> And why was the cpu id in the event header, shouldn’t it be in the event
> context?
>
Okay. I have to work on the header part of the binary stream files.
>
>
> Sebastian mentioned a more complex format necessary for the Tra
truct packet_context {
uint64_clock_monotonic_t timestamp_begin;
uint64_clock_monotonic_t timestamp_end;
uint64_t content_size;
uint64_t packet_size;
uint64_t packet_seq_num;
uint32_t events_discarded;
uint32_t cpu_id;
};
--
*Ravindra Kumar Meena*,
B. Tech. Computer Science and Engineering,
Indian Ins
Okay. I have tried to fix the warnings.
https://github.com/rmeena840/rtems-tools/commit/a5bdb314ae74caf9dd3af96e1efedccbe8bdf364
Have a look.
Compiler didn't report a warning.
--
*Ravindra Kumar Meena*,
B. Tech. Computer Science and Engineering,
Indian Institute of Technology (Indian S
27;s running RHEL.
I can see the warnings now.
--
*Ravindra Kumar Meena*,
B. Tech. Computer Science and Engineering,
Indian Institute of Technology (Indian School of Mines)
<https://www.iitism.ac.in/>, Dhanbad
___
devel mailing list
devel@rtems
toolchain/libelf/gelf_checksum.c', 'elftoolchain/libelf/gelf_dyn.c',
'elftoolchain/libelf/gelf_ehdr.c', 'elftoolchain/libelf/gelf_getclass.c',
'elftoolchain/libelf/gelf_fsize.c', 'elftoolchain/libelf/gelf_move.c',
'elftoolchain/libelf/gelf_ph
I have upgraded my machine from Ubuntu 16.04 to Ubuntu 19. Still, I can't
see that warning.
I used GCC 8.3.0.
I have attached the configure and build process in txt file. Please find
them both below.
Thanks
--
*Ravindra Kumar Meena*,
B. Tech. Computer Science and Engineering,
I
RTEMS_RECORDING_EVENT: { ns = 2756272, events = (
"RTEMS_RECORD_THREAD_SWITCH_IN" : container = 215 ), data =
648799907217440765 }
0 RTEMS_RECORDING_EVENT: { ns = 954463440912, events = (
"RTEMS_RECORD_THREAD_SWITCH_OUT" : container = 216 ), data =
648799894332538877 }
--
*Ravi
>
> > I really didn't see these warnings in my build. Which gcc version are
> > you using?
> >
> > I am using gcc version 5.4.0.
>
> Ok, this explains a lot. This GCC version is quite old. Which Linux
> distribution do you use?
>
I am using Ubuntu 16.0
ng commands to configure and build:
./waf configure --prefix=$HOME/sandbox/rtems/5
./waf build install
--
*Ravindra Kumar Meena*,
B. Tech. Computer Science and Engineering,
Indian Institute of Technology (Indian School of Mines)
<https://www.iitism.ac.in/>, Dhanbad
that which
> > cpu_id is it reading.
>
> In your metadata you removed the cpu member from the event structure.
>
I removed it because the new binary stream file does not have CPU. It has
only three values ns, event, and data.
--
*Ravindra Kumar Meena*,
B. Tech. Computer Science and E
3rd July work summary:
Worked on metadata for multiple event stream file. Attended meeting on
freenode.
--
*Ravindra Kumar Meena*,
B. Tech. Computer Science and Engineering,
Indian Institute of Technology (Indian School of Mines)
<https://www.iitism.ac.in/>, D
.
--
*Ravindra Kumar Meena*,
B. Tech. Computer Science and Engineering,
Indian Institute of Technology (Indian School of Mines)
<https://www.iitism.ac.in/>, Dhanbad
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
1 - 100 of 214 matches
Mail list logo
