Seb,
I tried your approach with this test program:
http://static.mah.priv.at/public/perfct.c
this freezes both 3.8.13-bone41 (vanilla) and 3.8.13xenomai-bone27 kernels
after the second call.
I had synced up the g.l.o/unified-build-candidate-3 and
On 03/03/2014 04:44 AM, Michael Haberler wrote:
Seb,
I tried your approach with this test program:
http://static.mah.priv.at/public/perfct.c
this freezes both 3.8.13-bone41 (vanilla) and 3.8.13xenomai-bone27 kernels
after the second call.
I had synced up the
On 3/3/2014 9:17 AM, Sebastian Kuzminsky wrote:
On 03/03/2014 04:44 AM, Michael Haberler wrote:
Seb,
I tried your approach with this test program:
http://static.mah.priv.at/public/perfct.c
this freezes both 3.8.13-bone41 (vanilla) and 3.8.13xenomai-bone27 kernels
after the second call.
Hi EBo,
On 03/02/2014 09:19 AM, EBo wrote:
Sławek and I have started a project over on SourceForge called
GentooCNC. We are still in the planning stages, but I thought I would
invite the other Gentoo users out there to join in the fun.
Another distro port means more potential users, devs,
Reading between the lines in the bug report below,
I see mention of Xenomai on the 3.8.13 kernel for
the BeagleBoneBlack.
I have also seen mention that TI has the SGX accelerated
graphics drivers running on the 3.8.13 kernel.
There are probably still some missing pieces to the
goal of having
On 3/3/2014 10:08 AM, Steve Stallings wrote:
Reading between the lines in the bug report below,
I see mention of Xenomai on the 3.8.13 kernel for
the BeagleBoneBlack.
I have also seen mention that TI has the SGX accelerated
graphics drivers running on the 3.8.13 kernel.
There are
On 03/02/2014 10:52 AM, Michael Haberler wrote:
5. The RT-PREEMPT RTAPI code which I imported from Michael Büsch uses
normal Posix threads. It uses the sched_setscheduler(..SCHED_FIFO..)
call to set the desired scheduling policiy. See man 2
sched_setscheduler. This system call requires
On Mon, Mar 3, 2014, at 12:26 PM, John Morris wrote:
If it were possible to set SCHED_FIFO with the fast thread prio 0 (no
special privs needed), and other thread prio relatively lower, it might
achieve the same effect. This could be implemented by changing the
definition of the
On Mar 3 2014 10:26 AM, John Morris wrote:
On 03/02/2014 10:52 AM, Michael Haberler wrote:
- do we use elevated privileges for the posix flavor binary, and
obtain the desired behavior
I'm in favor of this.
What sort of person might want to run LinuxCNC in 'sim' mode, and
requires no
On Sun, Mar 2, 2014, at 02:29 PM, Michael Haberler wrote:
Am 02.03.2014 um 15:21 schrieb John Kasunich jmkasun...@fastmail.fm:
There are several variables that are used to communicate
between the two parts. The faster part was written assuming
that those variables would not change
On Mar 3 2014 1:12 PM, John Kasunich wrote:
On Sun, Mar 2, 2014, at 02:29 PM, Michael Haberler wrote:
The required operations are:
record_write_begin() - allocate space for a message in the rb but do
not commit the write yet
record_write_end() - commit the write operation
On Mon, Mar 3, 2014, at 05:12 PM, EBo wrote:
Euuu... is there any log or indication that a non zero even occurred?
EAGAIN is a drop dead error. That implies, if I understand the
conversation correctly, that you ran out of memory on the machine. That
should be a fatal error on this
Hi All,
I just created a release candidate branch for circular arc blending:
http://git.linuxcnc.org/gitweb?p=linuxcnc.git;a=shortlog;h=refs/heads/circular-blend-arc-rc1
It's identical to my github branch that Sam and others have been testing.
There was one small hiccup in pushing the new
On Mon, Mar 3, 2014, at 05:32 PM, Michael Haberler wrote:
moreover this aspect is completely irrelevant to the discussion topic at
hand, which is about using scheduling behaviour used to assert certain
properties of parallel programs
can we focus on the actual problem please, which is
Am 03.03.2014 um 23:12 schrieb EBo e...@sandien.com:
On Mar 3 2014 1:12 PM, John Kasunich wrote:
On Sun, Mar 2, 2014, at 02:29 PM, Michael Haberler wrote:
The required operations are:
record_write_begin() - allocate space for a message in the rb but do
not commit the write yet
On 3/3/14 16:12 , Robert Ellenberg wrote:
Hi All,
I just created a release candidate branch for circular arc blending:
http://git.linuxcnc.org/gitweb?p=linuxcnc.git;a=shortlog;h=refs/heads/circular-blend-arc-rc1
Sweet!
It's identical to my github branch that Sam and others have been
On Mar 3 2014 3:21 PM, John Kasunich wrote:
On Mon, Mar 3, 2014, at 05:12 PM, EBo wrote:
Euuu... is there any log or indication that a non zero even
occurred?
EAGAIN is a drop dead error. That implies, if I understand the
conversation correctly, that you ran out of memory on the machine.
Sure will thanks!
EBo --
On Mar 3 2014 9:03 AM, John Morris wrote:
Hi EBo,
On 03/02/2014 09:19 AM, EBo wrote:
Sławek and I have started a project over on SourceForge called
GentooCNC. We are still in the planning stages, but I thought I
would
invite the other Gentoo users out there
On 3/3/14 16:18 , Sebastian Kuzminsky wrote:
On 3/3/14 16:12 , Robert Ellenberg wrote:
As a possible solution, I've been able to rebase the RC branch onto the
lastest master with minimal changes. If there is a recent build that we
know is solid, I can rebase my branch onto that and push it.
Robert, are you on IRC? If so, what's your nickname?
There was a failure in a sim build that looks like an actual bug, rather
than yet another problem with the buildbot. Check this out:
http://buildbot.linuxcnc.org/buildbot/builders/1306.rip-precise-amd64/builds/1847/steps/runtests/logs/stdio
On 03/02/2014 11:02 AM, Michael Haberler wrote:
Am 02.03.2014 um 15:21 schrieb John Kasunich jmkasun...@fastmail.fm:
the problem is about passing _several scalar values between threads
in an atomic fashion_ (transactional, meaning - all of them updated,
or none of them updated as seen by
to establish better common understanding, here are some diagrams:
1. the two threads, and the state they share:
http://static.mah.priv.at/public/stepgen-sharedstate.png . The dashed box
contains the state which is critical with respect to atomic update and
consumption.
2. the intended
On 03/01/2014 12:04 PM, Sebastian Kuzminsky wrote:
Taking this discussion from IRC to email, as requested by Michael...
In the master branch, and in 2.5 and all earlier releases of LinuxCNC,
all HAL threads obey this invariant: short-period threads (ie, the base
thread) are never interrupted
On 03/04/2014 12:26 AM, John Morris wrote:
In summary: Re-enable the 'make setuid' step on the buildbot, and I bet
the threads.0 test will pass again.
The sim builders never ran 'sudo make setuid', in 2.5 and master only
the realtime builders need it.
So this is a new behavior in ub, which is
24 matches
Mail list logo
