date:20160303

Re: [PATCH 8/8] score: Replace watchdog handler implementation

2016-03-03 Thread Sebastian Huber

On 03/03/16 23:44, Joel Sherrill wrote:

>
> "be placed on Red-Black Trees for set management." copy-pasted
comment
> should be Chains?

Thanks, for spotting this.

>
> "watchdog is scheduled and a black node". ditto, black should be red
> for the second one.

Oh, yes.

>
> _Watchdog_Ticks_from_seconds(): why is ticks = seconds<<30 the right
> thing to do? Same for _Watchdog_Ticks_from_timespec(). I am missing
> some assumption here, I guess. It might improve readability to
provide
> a helper function for this.

Ok, sorry for the magic numbers.  2**30 == 1073741824 enough to
cope with 1e9 nanoseconds.  So, we have 2**34 seconds available,
leading to a year 2514 problem.

That's pretty close to the 2^64 nanosecond limit as I recall. So 
reasonable but

I suppose that should be very explicit somewhere in a comment.

Funny, before there was a wiki, we had a FAQ document which had a 
section on
date/time overflow issues. We probably need a section in the users 
manual with

the current truth on this:

https://docs.rtems.org/releases/rtemsdocs-4.6.4/share/rtems/html/FAQ/FAQ00100.html

We have multiple date/time and interval representations in the score, 
classic and

POSIX APIs. It would be good to capture them again.

Yes, this is on my TODO list along with the year 2038 problem.

--
Sebastian Huber, embedded brains GmbH

Address : Dornierstr. 4, D-82178 Puchheim, Germany
Phone   : +49 89 189 47 41-16
Fax : +49 89 189 47 41-09
E-Mail  : sebastian.hu...@embedded-brains.de
PGP : Public key available on request.

Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.

___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

error in building RTEMS Source Builder

2016-03-03 Thread Abhinav Jain

So I am trying to build the RTEMS Source Builder on my Ubuntu machine
and this is the report file that gets generated!
RTEMS Tools Project - Source Builder Error Report
 Build: error: building rtems-tools-HEAD-1
 Command Line: ../source-builder/sb-set-builder --log=l-i386.txt 
--prefix=/home/abhinav/development/rtems/4.12 4.12/rtems-i386
 Python: 2.7.6 (default, Jun 22 2015, 17:58:13) [GCC 4.8.2]
 
git://git.rtems.org/rtems-source-builder.git/origin/b537e5536459e207fc8e56a1df3774c1700606d5-modified
 Linux cr33p 3.19.0-49-generic #55~14.04.1-Ubuntu SMP Fri Jan 22 11:24:31 UTC 
2016 x86_64
Tail of the build log:
script: 69: 
script: 70: 
script: 71: export PATH
script: 72: # Default environment set up.
script: 73: LANG=C
script: 74: export LANG
script: 75: unset DISPLAY || :
script: 76: umask 022
script: 77: cd 
"/home/abhinav/development/rtems/src/rtems-source-builder/rtems/build/rtems-tools-HEAD-1"
script: 78: echo "=> rtems-tools-HEAD-1:"
script: 79: echo "==> %prep:"
script: 80: build_top=$(pwd)
script: 81: rtems_tools_source="rtems-tools.git"
script: 82: source_dir_rtems_tools=${rtems_tools_source}
source setup: rtems-tools-HEAD-1: source rtems-tools -q -n ${rtems_tools_source}
Creating source directory: sources/git
making dir: 
/home/abhinav/development/rtems/src/rtems-source-builder/rtems/sources/git
git: clone: git://git.rtems.org/rtems-tools.git -> sources/git/rtems-tools.git
git: reset: git://git.rtems.org/rtems-tools.git
git: fetch: git://git.rtems.org/rtems-tools.git -> sources/git/rtems-tools.git
git: checkout: git://git.rtems.org/rtems-tools.git => HEAD
git: pull: git://git.rtems.org/rtems-tools.git
script: 83: cd 
/home/abhinav/development/rtems/src/rtems-source-builder/rtems/build/rtems-tools-HEAD-1
script: 84: /bin/rm -rf ${rtems_tools_source}
script: 85: ln -s 
/home/abhinav/development/rtems/src/rtems-source-builder/rtems/sources/git/rtems-tools.git
 ${source_dir_rtems_tools}
script: 86: cd ${rtems_tools_source}
script: 87: /bin/chmod -R a+rX,g-w,o-w .
script: 88: cd ${build_top}
script: 89: SB_CXC="no"
script: 90: echo "==> clean %{buildroot}: ${SB_BUILD_ROOT}"
script: 91: /bin/rm -rf ${SB_BUILD_ROOT}
script: 92: /bin/mkdir -p ${SB_BUILD_ROOT}
script: 93: echo "==> %build:"
script: 94: build_top=$(pwd)
script: 95: if test "x86_64-linux-gnu" != "x86_64-linux-gnu" ; then
script: 96: RT_HOST="-host=x86_64-linux-gnu"
script: 97: else
script: 98: RT_HOST=
script: 99: fi
script:100: cd ${source_dir_rtems_tools}
script:101: ./waf configure ${RT_HOST} 
--prefix=/home/abhinav/development/rtems/4.12
script:102: ./waf
script:103: cd ${build_top}
script:104: echo "==> %install:"
script:105: build_top=$(pwd)
script:106: /bin/rm -rf $SB_BUILD_ROOT
script:107: SB_BUILD_ROOT_WAF=$SB_BUILD_ROOT
script:108: cd ${source_dir_rtems_tools}
script:109: ./waf --destdir=$SB_BUILD_ROOT_WAF install
script:110: cd ${build_top}
script:111: echo "==> %clean:"
removing: 
/home/abhinav/development/rtems/src/rtems-source-builder/rtems/build/rtems-tools-HEAD-1
making dir: 
/home/abhinav/development/rtems/src/rtems-source-builder/rtems/build/rtems-tools-HEAD-1
write script: 
/home/abhinav/development/rtems/src/rtems-source-builder/rtems/build/rtems-tools-HEAD-1/doit
building: rtems-tools-HEAD-1
run: /bin/sh -ex  
/home/abhinav/development/rtems/src/rtems-source-builder/rtems/build/rtems-tools-HEAD-1/doit
+ export 
SB_ORIG_PATH=/home/abhinav/development/rtems/4.12/bin:/home/abhinav/development/rtems/4.11/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games
+ SB_PREFIX=/home/abhinav/development/rtems/4.12
+ echo /home/abhinav/development/rtems/4.12
+ /usr/bin/sed -e s/^\///
+ SB_PREFIX_CLEAN=home/abhinav/development/rtems/4.12
+ 
SB_SOURCE_DIR=/home/abhinav/development/rtems/src/rtems-source-builder/rtems/sources
+ 
SB_BUILD_DIR=/home/abhinav/development/rtems/src/rtems-source-builder/rtems/build/rtems-tools-HEAD-1
+ SB_HOST_CFLAGS=-O2 -pipe 
+ SB_HOST_CXXFLAGS=-O2 -pipe 
+ 
SB_HOST_LDFLAGS=-L/home/abhinav/development/rtems/src/rtems-source-builder/rtems/build/tmp/sb-abhinav/4.12/rtems-i386/home/abhinav/development/rtems/4.12/lib
+ SB_BUILD_CFLAGS=-O2 -pipe 
-I/home/abhinav/development/rtems/src/rtems-source-builder/rtems/build/tmp/sb-abhinav/4.12/rtems-i386/home/abhinav/development/rtems/4.12/include
=> rtems-tools-HEAD-1:
==> %prep:
+ SB_BUILD_CXXFLAGS=-O2 -pipe 
-I/home/abhinav/development/rtems/src/rtems-source-builder/rtems/build/tmp/sb-abhinav/4.12/rtems-i386/home/abhinav/development/rtems/4.12/include
+ 
SB_BUILD_LDFLAGS=-L/home/abhinav/development/rtems/src/rtems-source-builder/rtems/build/tmp/sb-abhinav/4.12/rtems-i386/home/abhinav/development/rtems/4.12/lib
+ SB_CFLAGS=-O2 -pipe 
-I/home/abhinav/development/rtems/src/rtems-source-builder/rtems/build/tmp/sb-abhinav/4.12/rtems-i386/home/abhinav/development/rtems/4.12/include
 
+ SB_CXXFLAGS=-O2 -pipe

Building RTEMS hello world image using CMake

2016-03-03 Thread Sambeet Panigrahi

I wanted to build a hello world image of RTEMS using cmake. Can someone
provide me steps for doing so or point me to the right resources ?
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: [PATCH 8/8] score: Replace watchdog handler implementation

2016-03-03 Thread Sebastian Huber

Thanks a lot for your review.

- Gedare Bloom  schrieb:
> I scanned through most of it. I just have a few minor issues/questions:
>
> There is an _Assert(0) followed by a TODO. This _Assert() is likely
> dead/untested code block. It may be worth fabricating a fatal test for
> it, if possible?

This one:

> +  if ( pthread_kill ( ptimer->thread_id, ptimer->inf.sigev_signo ) ) {
> +_Assert( FALSE );
> +/*
> + * TODO: What if an error happens at run-time? This should never
> + *   occur because the timer should be canceled if the thread
> + *   is deleted. This method is being invoked from the Clock
> + *   Tick ISR so even if we decide to take action on an error,
> + *   we don't have many options. We shouldn't shut the system
> down.
> + */

Its a code move from one file to another, so nothing new.

>
> "be placed on Red-Black Trees for set management." copy-pasted comment
> should be Chains?

Thanks, for spotting this.

>
> "watchdog is scheduled and a black node". ditto, black should be red
> for the second one.

Oh, yes.

>
> _Watchdog_Ticks_from_seconds(): why is ticks = seconds<<30 the right
> thing to do? Same for _Watchdog_Ticks_from_timespec(). I am missing
> some assumption here, I guess. It might improve readability to provide
> a helper function for this.

Ok, sorry for the magic numbers.  2**30 == 1073741824 enough to cope with 1e9 
nanoseconds.  So, we have 2**34 seconds available, leading to a year 2514 
problem.
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: GSoC 2016 Interested in Tracing was Re:

2016-03-03 Thread Isaac Gutekunst

Hi Vivek,

Chris is definitely the person most knowledgeable in this area.

On 03/03/2016 11:45 AM, Joel Sherrill wrote:

On Thu, Mar 3, 2016 at 10:25 AM, Vivek Kukreja > wrote:

Hi everyone

I am Vivek Kukreja, currently pursuing Masters from India. I'm
interested in applying for GSOC this year. I am a skilled C
Programmer and have strong understanding of OS concepts. I'm
interested in system programming and kernel development.

I am interested to work on topics under Tracing. I am intrigued by
the topic. I think this will be a good place to start for me.

That's a good area that needs work. Chris Johns is the core person in
this area. He is in
Sydney and will likely comment once he is awake. :)

I gave a presentation at the Flight Software Workshop in 2014 on the
RTEMS ecosystem.
Tracing was included in that presentation and Chris helped with the
slides. The slides are
here:

http://flightsoftware.jhuapl.edu/files/2014/Presentations/Day-2/Session-3/2-RTEMSProjectEcosystem.pdf

There is a video of my presentation if you want to see it. But this
presentation covers the
background and status.

I have gone through Getting Started documentation and setup RTEMS on
my machine. I have tried running the provided examples. I tried to
run the tracing example, but am facing some problem during
compilation (wrapper compilation error). I will continue looking
into it, and report if I can't solve the problem on my own.

Focus first on doing the GSoC Hello World and adding yourself to the
list of students.
Then ask specific questions about those examples.

Please tell me about the open projects under the Tracing Tool. I
request you to please give me some pointers to get started.

Chris is the person to make sure the task list is current and in priority.

But I know there is work to be done on generation of method trace wrappers,
getting trace data off target (tcp/ip, etc), and producing Common Trace
Format
and integrating with the Linux Trace Toolkit.

My understanding is that the Linux Trace Toolkit can also dynamically
interact (bidirectionally) with the target system. I don't know what that
entails but it is desirable. But it requires having basic integration solved
first.

I have done some work on the side trying to understand the lttng-live
trace protocol

The Linux Trace Toolkit has one component that runs on a potentially
remote system, and captures trace information.

A different system can connect to the system being traced using the
lttng-live protocol.

See
https://github.com/lttng/lttng-tools/blob/master/doc/live-reading-protocol.txt

It is a fairly straightforward binary protocol with a handshake, and a
few interactions before raw CTF is sent back in a request/response manner.

The lttng-live relay daemon is what provides this service.

The code for that can be seen here:

https://github.com/lttng/lttng-tools/tree/master/src/common/relayd

I've done some work to implement the lttng-live protocol as a proof of
concept as part of some development here.

I'd be interested in providing some help to make RTEMS Trace Capture
Engine support storing logs in CTF format, and making them available via
lttng-live.

Hope this helps as well,

Isaac

I hope that helps.

--joel

Regards,

Vivek

___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

34 matches

Mail list logo