It's a dual core 8th Gen Intel atom.
In the future I will use a quad core atom and probably I will isolate a
core.
I will investigate on ipipe traces. I will let you know, but for me it's OK
anyway.
Il mer 10 apr 2019, 21:36 Jan Kiszka ha scritto:
> On 10.04.19 21:26, cagnulein via Xenomai
On 10.04.19 21:26, cagnulein via Xenomai wrote:
After 3 days of test (latency + windows 10 with cpu-z and stress test) I
reached rare peaks of 130 us.
For me it's OK but I think there is a small "regression" against the 4.9
Do you need any other test?
What is the CPU / SoC here? Are we talking
After 3 days of test (latency + windows 10 with cpu-z and stress test) I
reached rare peaks of 130 us.
For me it's OK but I think there is a small "regression" against the 4.9
Do you need any other test?
R.
Il lun 8 apr 2019, 12:13 Jan Kiszka ha scritto:
> On 08.04.19 11:56, cagnulein wrote:
>
On 10.04.19 17:02, Lange Norbert wrote:
-Original Message-
From: Jan Kiszka
Sent: Mittwoch, 10. April 2019 16:48
To: Lange Norbert ; Xenomai
Subject: Re: (unknown)
E-MAIL FROM A NON-ANDRITZ SOURCE: AS A SECURITY MEASURE, PLEASE
EXERCISE CAUTION WITH E-MAIL CONTENT AND ANY LINKS OR
nabbed verbatim from the Linux kernel.
Signed-off-by: Norbert Lange
---
.clang-format | 469 ++
1 file changed, 469 insertions(+)
create mode 100755 .clang-format
diff --git a/.clang-format b/.clang-format
new file mode 100755
index
> -Original Message-
> From: Jan Kiszka
> Sent: Mittwoch, 10. April 2019 16:48
> To: Lange Norbert ; Xenomai
>
> Subject: Re: (unknown)
>
> E-MAIL FROM A NON-ANDRITZ SOURCE: AS A SECURITY MEASURE, PLEASE
> EXERCISE CAUTION WITH E-MAIL CONTENT AND ANY LINKS OR ATTACHMENTS.
>
>
>
[re-adding the list]
On 10.04.19 16:44, Lange Norbert wrote:
-Original Message-
From: Xenomai On Behalf Of Jan Kiszka via
Xenomai
Sent: Mittwoch, 10. April 2019 16:36
To: Norbert Lange ; xenomai@xenomai.org
Subject: Re: (unknown)
E-MAIL FROM A NON-ANDRITZ SOURCE: AS A SECURITY
On 10.04.19 13:14, Norbert Lange via Xenomai wrote:
V3 of the patchset, corrected many checkstyle issues,
simplified condvar autoinit.
I did not use ARRAY_SIZE, as that would need another include.
All applied now. Patch 1 was not cleanly based on next, though. I think some
local style
On 10.04.19 16:25, Norbert Lange via Xenomai wrote:
The optional mode argument (open is a vararg function),
was only be read and forwarded if the O_CREAT flag is set.
That is not complete, as O_TMPFILE will require this
argument aswell. Fixed in this commit, and a fallback definition
of
V2 now also fixes the wrappers.
Btw. wouldnt it be possible to just do away with the ugly vaargs?
I tested a few architectures (x86, arm mips, both 32 and 64 bit)
and the function call singature stays the same whether a
function has varagrs or a fixed amount of arguments.
The wrappers could then
The optional mode argument (open is a vararg function),
was only be read and forwarded if the O_CREAT flag is set.
That is not complete, as O_TMPFILE will require this
argument aswell. Fixed in this commit, and a fallback definition
of O_TMPFILE is added, incase libcobalt is built against an
On 10.04.19 13:18, Norbert Lange via Xenomai wrote:
The optional mode argument (open is a vararg function),
was only be read and forwarded if the O_CREAT flag is set.
That is not complete, as O_TMPFILE will require this
argument aswell. Fixed in this commit, and a fallback definition
of
On 10.04.19 13:17, Norbert Lange via Xenomai wrote:
V2 of the patchset. Fixed checkstyle issues, better identation,
and aded casts to silence (false) pedantic warnings.
Both applied to next, thanks.
You probably want to edit your cover letter subject as well - or use git
format-patch.
Jan
On 10.04.19 10:42, Roman Stratiienko wrote:
I did measurements after clearing cache 'ccache -C'
I assume that 600mb in current statistic is due to multiple build of different
source dependencies due to enabled DEBUG INFO config. Old cache should be
invalidated and cleaned automatically as
On 10.04.19 13:14, Norbert Lange via Xenomai wrote:
V3 of the patchset, corrected many checkstyle issues,
simplified condvar autoinit.
Thanks for the update!
I did not use ARRAY_SIZE, as that would need another include.
Ah, we do not have this construct in lib/ so far.
There are private
V2 of the patchset. Fixed checkstyle issues, better identation,
and aded casts to silence (false) pedantic warnings.
The optional mode argument (open is a vararg function),
was only be read and forwarded if the O_CREAT flag is set.
That is not complete, as O_TMPFILE will require this
argument aswell. Fixed in this commit, and a fallback definition
of O_TMPFILE is added, incase libcobalt is built against an
Covers now all standard integer types,
no need for corner cases.
Signed-off-by: Norbert Lange
---
include/boilerplate/compiler.h | 28
1 file changed, 8 insertions(+), 20 deletions(-)
diff --git a/include/boilerplate/compiler.h b/include/boilerplate/compiler.h
Because of conflicts with libc++ (v1/bit include file).
Simplify the macro as there shouldn't be any bad cornercases
Signed-off-by: Norbert Lange
---
include/boilerplate/compiler.h| 31 ++-
lib/boilerplate/heapmem.c | 2 +-
add a few testcases where destroy is called as first function,
and test failure if the state is a non-standard initializer.
Signed-off-by: Norbert Lange
---
testsuite/smokey/posix-cond/posix-cond.c | 15 +++
testsuite/smokey/posix-mutex/posix-mutex.c | 52 ++
2 files
Signed-off-by: Norbert Lange
---
lib/cobalt/mutex.c | 8 ++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff --git a/lib/cobalt/mutex.c b/lib/cobalt/mutex.c
index 2748850e2..2f7595b50 100644
--- a/lib/cobalt/mutex.c
+++ b/lib/cobalt/mutex.c
@@ -49,8 +49,12 @@
* By default, Cobalt
contrary to some comments, mutexes are automatically
initialised on lock/unlock.
Correct the destroy method to not report an
error on such mutexes.
{get,set}prioceiling requires mutexes that were explicitly
initialised, so no change needed there
Signed-off-by: Norbert Lange
---
V3 of the patchset, corrected many checkstyle issues,
simplified condvar autoinit.
I did not use ARRAY_SIZE, as that would need another include.
Signed-off-by: Norbert Lange
---
lib/cobalt/cond.c | 10 +++---
1 file changed, 7 insertions(+), 3 deletions(-)
diff --git a/lib/cobalt/cond.c b/lib/cobalt/cond.c
index 9553824c2..e66b20922 100644
--- a/lib/cobalt/cond.c
+++ b/lib/cobalt/cond.c
@@ -47,9 +47,13 @@
* several processes (it
contrary to some comments, condvars are automatically
initialised on signal/wait.
Correct the destroy method to not report an
error on such condvars.
Check whether the condition variable has the
static initializer is now more strict.
Signed-off-by: Norbert Lange
---
lib/cobalt/cond.c | 86
I did measurements after clearing cache 'ccache -C'
I assume that 600mb in current statistic is due to multiple build of
different source dependencies due to enabled DEBUG INFO config. Old cache
should be invalidated and cleaned automatically as size goes up to the
limit.
ср, 10 апр. 2019 г.,
26 matches
Mail list logo
