On Tue, Mar 5, 2019 at 7:53 PM Jan Kiszka wrote:
>
> On 05.03.19 15:45, roman.stratiienko--- via Xenomai wrote:
> > From: Roman Stratiienko
> >
> > Signed-off-by: Roman Stratiienko
> > ---
> > .travis.yml | 73 +
> > 1 file changed, 73
On 06.03.19 14:10, Jan Kiszka wrote:
On 06.03.19 12:28, Lange Norbert via Xenomai wrote:
Hello,
I have a similar issue on real hardware (cc Philippe). Can you try booting
with notscdeadline?
I would be surprised if it's that: QEMU does not emulate this APIC feature, only
KVM does.
I
Hello,
I have a similar issue on real hardware (cc Philippe). Can you try booting with
notscdeadline?
Norbert
> -Original Message-
> From: Xenomai On Behalf Of Richard
> Weinberger via Xenomai
> Sent: Mittwoch, 6. März 2019 11:17
> To: xenomai@xenomai.org; henning.sch...@siemens.com
Hi!
When I try to run ipipe-core-4.14.89-x86-2.patch under qemu, the
kernel does not start.
I does always start when only one core is used.
It starts 9 out of 10 times when I enable KVM.
The kernel seems to wait forever for an IPI in ipipe_critical_enter().
Please find the gdb backtraces and
On 06.03.19 12:49, Roman Stratiienko via Xenomai wrote:
On Tue, Mar 5, 2019 at 7:53 PM Jan Kiszka wrote:
On 05.03.19 15:45, roman.stratiienko--- via Xenomai wrote:
From: Roman Stratiienko
Signed-off-by: Roman Stratiienko
---
.travis.yml | 73
On 06.03.19 12:28, Lange Norbert via Xenomai wrote:
Hello,
I have a similar issue on real hardware (cc Philippe). Can you try booting with
notscdeadline?
I would be surprised if it's that: QEMU does not emulate this APIC feature, only
KVM does.
I need to reproduce. Which QEMU version?
Hi!
I have a Xenomai 2.6 application which makes heavy usage of
rt_dev_ioctl() and shadow threads
with rt_task_shadow().
If I understand the new Xenomai 3 API correctly, rt_dev_ioctl() for
userspace is gone and the cobalt wrappers should be used such that
plain ioctl() calls will be routed
Hello,
1)
There is an inconsistency with the documentation [1], which claims that mutex
and condition variables
need to be explicitly initialized with the *_init functions.
The implementation however checks the state via a flag and calls *_init if
necessary, and the program below works
Am Mittwoch, 6. März 2019, 14:43:55 CET schrieb Jan Kiszka:
> On 06.03.19 14:10, Jan Kiszka wrote:
> > On 06.03.19 12:28, Lange Norbert via Xenomai wrote:
> >> Hello,
> >>
> >> I have a similar issue on real hardware (cc Philippe). Can you try booting
> >> with notscdeadline?
> >>
> >
> > I
On 3/6/19 2:43 PM, Jan Kiszka via Xenomai wrote:
> On 06.03.19 14:10, Jan Kiszka wrote:
>> On 06.03.19 12:28, Lange Norbert via Xenomai wrote:
>>> Hello,
>>>
>>> I have a similar issue on real hardware (cc Philippe). Can you try
>>> booting with notscdeadline?
>>>
>>
>> I would be surprised if
From: Roman Stratiienko
As do_gettimeofday is very old and deprecated, use ktime instead
Signed-off-by: Roman Stratiienko
---
kernel/cobalt/clock.c | 4 +---
kernel/drivers/analogy/rtdm_helpers.c | 5 +
2 files changed, 2 insertions(+), 7 deletions(-)
diff --git
On 06.03.19 10:59, Richard Weinberger via Xenomai wrote:
Hi!
I have a Xenomai 2.6 application which makes heavy usage of
rt_dev_ioctl() and shadow threads
with rt_task_shadow().
If I understand the new Xenomai 3 API correctly, rt_dev_ioctl() for
userspace is gone and the cobalt wrappers should
From: Roman Stratiienko
After kernel v4.18 commit 4a0772cf0674
("tracing: Prevent further users of zero size static arrays in trace events")
creating zero length arrays will force compile-time error
This will fix BUILD_BUG_ON error on v4.18 and later
Signed-off-by: Roman Stratiienko
---
Since
On 06.03.19 12:24, Philippe Gerum via Xenomai wrote:
On 3/2/19 1:25 PM, Jeff Webb via Xenomai wrote:
I could also avoid using the PCI command register entirely and just write to a
device-specific mask bit in my peripheral, but I would rather implement a
generic solution if there is not a
Hi,
On 3/5/19 3:45 PM, roman.stratiienko--- via Xenomai wrote:
> From: Roman Stratiienko
>
> Signed-off-by: Roman Stratiienko
> ---
> .travis.yml | 5 +
> 1 file changed, 5 insertions(+)
>
> diff --git a/.travis.yml b/.travis.yml
> index 0807760f4..ab23b745d 100644
> --- a/.travis.yml
On 06.03.19 16:33, Richard Weinberger wrote:
Am Mittwoch, 6. März 2019, 14:43:55 CET schrieb Jan Kiszka:
On 06.03.19 14:10, Jan Kiszka wrote:
On 06.03.19 12:28, Lange Norbert via Xenomai wrote:
Hello,
I have a similar issue on real hardware (cc Philippe). Can you try booting
with
From: Roman Stratiienko
Signed-off-by: Roman Stratiienko
---
Since v1: v4.20 removed and added to last commit
.travis.yml | 68 +
1 file changed, 68 insertions(+)
create mode 100644 .travis.yml
diff --git a/.travis.yml b/.travis.yml
new
From: Roman Stratiienko
Since kernel v5.0 upstream commit 96d4f267e40f
("Remove 'type' argument from access_ok() function")
access_ok() function takes only 2 parameters
Change access_rok and access_wok wrappers for kernels
starting from v5.0, and preserve them for earlier versions
This will
From: Roman Stratiienko
Starting from kernel v5.0 commit f5451582c4e2
("kconfig: stop supporting '.' and '/' in unquoted words")
quotes are mandatory for usage
Signed-off-by: Roman Stratiienko
---
kernel/drivers/analogy/Kconfig | 8
kernel/drivers/can/Kconfig | 4 ++--
From: Roman Stratiienko
$SRCARCH removed since v4.18-rc1, upstream commit 104daea149c4
("kconfig: reference environment variables directly and remove 'option env='")
This will fix build with v4.18
Signed-off-by: Roman Stratiienko
---
scripts/Kconfig.frag | 2 +-
From: Roman Stratiienko
Signed-off-by: Roman Stratiienko
---
.travis.yml | 10 ++
1 file changed, 10 insertions(+)
diff --git a/.travis.yml b/.travis.yml
index 24889ca5f..ab23b745d 100644
--- a/.travis.yml
+++ b/.travis.yml
@@ -46,6 +46,16 @@ script:
matrix:
include:
+- env:
From: Roman Stratiienko
print_symbol() removed since v4.16-rc1 commit d2279c9d7f7d
("kallsyms: remove print_symbol() function")
use print_symbol for version less than v4.16 and printk starting from v4.16
Signed-off-by: Roman Stratiienko
---
Since v1: add cast to (void *) to fix build warning
From: Roman Stratiienko
siginfo_t can't be used in kernel-space starting from v4.20-rc1 commit
ae7795bc6187 ("signal: Distinguish between kernel_siginfo and siginfo")
replace all siginfo_t to kernel_siginfo_t and create wrapper for kernel < v4.20
Signed-off-by: Roman Stratiienko
---
From: Roman Stratiienko
READ_ONCE() introduced from v3.19 commit 230fa253df63
("kernel: Provide READ_ONCE and ASSIGN_ONCE")
and ACCESS_ONCE() removed startibg from v4.15-rc4 commit
b899a850431e ("compiler.h: Remove ACCESS_ONCE()")
Replace ACCESS_ONCE with READ_ONCE and make READ_ONCE wrapper
for
On 06.03.19 10:39, Lange Norbert via Xenomai wrote:
Hello,
1)
There is an inconsistency with the documentation [1], which claims that mutex
and condition variables
need to be explicitly initialized with the *_init functions.
The implementation however checks the state via a flag and calls
Am Mittwoch, 6. März 2019, 18:25:56 CET schrieb Jan Kiszka:
> On 06.03.19 10:59, Richard Weinberger via Xenomai wrote:
> > Hi!
> >
> > I have a Xenomai 2.6 application which makes heavy usage of
> > rt_dev_ioctl() and shadow threads
> > with rt_task_shadow().
> >
> > If I understand the new
26 matches
Mail list logo
