According to POSIX message queues have kernel persistence, which means
they are not cleaned up until the next reboot.
The test has a mq_unlink() as "precondition", so it will clean up
failed test runs silently but /proc/xenomai/registry/usage will still
report a "leak" once the test has
From: Song Chen
Add a syscall specific for mq_timedreceive64 with 64bit time_t.
Signed-off-by: Song Chen
[Florian:
- Reformat commit msg
- relocate code
- tracing
- fix syscall declarations
]
Signed-off-by: Florian Bezdeka
---
@Jan: This should replace 76607e1a7237 in next. Other
On 12.08.21 16:39, Bezdeka, Florian (T RDA IOT SES-DE) wrote:
> On Thu, 2021-08-12 at 14:45 +0200, Jan Kiszka wrote:
>> On 12.08.21 14:39, Bezdeka, Florian (T RDA IOT SES-DE) wrote:
>>> Hi all,
>>>
>>> I just noticed that the posix_select test of smokey is leaking one
>>> registry element:
>>>
>>>
On Thu, 2021-08-12 at 14:45 +0200, Jan Kiszka wrote:
> On 12.08.21 14:39, Bezdeka, Florian (T RDA IOT SES-DE) wrote:
> > Hi all,
> >
> > I just noticed that the posix_select test of smokey is leaking one
> > registry element:
> >
> > $ cat /proc/xenomai/registry/usage
> > 8/512
> >
> > $
On 12.08.21 14:39, Bezdeka, Florian (T RDA IOT SES-DE) wrote:
> Hi all,
>
> I just noticed that the posix_select test of smokey is leaking one
> registry element:
>
> $ cat /proc/xenomai/registry/usage
> 8/512
>
> $ /smokey --run=posix_select
> posix_select OK
>
> $ cat
Hi all,
I just noticed that the posix_select test of smokey is leaking one
registry element:
$ cat /proc/xenomai/registry/usage
8/512
$ /smokey --run=posix_select
posix_select OK
$ cat /proc/xenomai/registry/usage
9/512
The following diff would fix that, but I assume the resource cleanup
OK, yeah I had mistakenly put --ldflags in the xeno-config line for CFLAGS
=
This was also problem:
LDLIBS= $(shell $(XENOCONFIG) --skin=native --ldflags) \
$(shell $(XENOCONFIG) --skin=rtdm --ldflags) \
$(shell $(XENOCONFIG) --skin=posix --ldflags)
That used to work in Xenomai 2.6 but not in
Based on the tests provided by Song with the following adjustments:
- #includes cleaned up
- making sure all resources used during tests have are cleaned up
- Switched to CLOCK_MONOTONIC for time measurement
__cobalt_event_wait sets the time mode to XN_ABSOLUTE, so we have to
use
From: Song Chen
If sizeof time_t bigger than 4, which means glibc supports
64bit timespec, go to event_wait64.
otherwise, go to original event_wait.
Signed-off-by: Song Chen
Signed-off-by: Florian Bezdeka
---
lib/cobalt/internal.c | 5 +
1 file changed, 5 insertions(+)
diff --git
From: Song Chen
Add a syscall specific for event_wait with 64bit time_t.
Signed-off-by: Song Chen
[Florian: Tracing, reformatting/rebasing]
Signed-off-by: Florian Bezdeka
---
include/cobalt/uapi/syscall.h | 1 +
kernel/cobalt/posix/event.c| 34 +++---
Hi!
Just another y2038 related syscall, once again based on v1 sent out by
Song and rebased to current next with some code- and test-cleanups applied.
@Song:
This one was the last one in my inbox. Please make sure that all
following patches are based on next. IIRC there are 3 or 4 syscalls
在 2021/8/11 下午9:36, Florian Bezdeka 写道:
Hi!
Just another y2038 related syscall, once again based on v1 sent out by
Song and rebased to current next with some code- and test-cleanups applied.
@Song:
This one was the last one in my inbox. Please make sure that all
following patches are based
在 2021/8/10 下午6:24, Florian Bezdeka 写道:
Hi all,
this is kind of a re-send of the patch series originall published by
Song. There were some things that had to be addressed:
- Code formattings
- Copy paste errors in the test suite
- Failing / incomplete tests, missing test cleanups
-
On 12.08.21 07:50, C Smith wrote:
> Hi Jan,Thanks for your prompt reply. I reduced my very large app to
> about 200 lines, it only starts one periodic process. but I still get
> this error during linkage:
>
> /usr/xenomai/lib/xenomai/bootstrap.o: In function `xenomai_main':
>
14 matches
Mail list logo
