On 02.12.19 08:12, Jan Kiszka via Xenomai wrote:
From: Jan Kiszka
Now that this path goes via an own syscall, better test it.
At this chance, make sure that the test runs the scheduler changes from
primary mode.
Signed-off-by: Jan Kiszka
---
testsuite/smokey/setsched/setsched.c | 19 ++
Le Vendredi, Novembre 29, 2019 17:45 CET, Jan Kiszka a
écrit:
> On 29.11.19 17:19, François Legal wrote:
> > Le Vendredi, Novembre 29, 2019 17:05 CET, Jan Kiszka
> > a écrit:
> >
> >> On 29.11.19 16:05, François Legal wrote:
> >>> Le Vendredi, Novembre 29, 2019 15:45 CET, Jan Kiszka
> >>> a
Hello.
I am developing in the following environment.
* Raspberry Pi 3b
* Linux 4.14. 52 (arm)
* Xenomai 3.0. 7
I want to build a 64 bit (arm 64) kernel for use with a Raspberry Pi 3 b (or
Raspberry Pi 4b).
The Raspberry Pi 3b (arm 64) was mentioned on the wiki as a Xenomai evaluation
board.
Co
On 02.12.19 12:41, smpd support via Xenomai wrote:
> Hello.
>
> I am developing in the following environment.
> * Raspberry Pi 3b
> * Linux 4.14. 52 (arm)
> * Xenomai 3.0. 7
>
> I want to build a 64 bit (arm 64) kernel for use with a Raspberry Pi 3 b (or
> Raspberry Pi 4b).
>
> The Raspberry Pi
Thank you for your reply.
* Linux 4.19.81 (Raspberry pi github repos)
* ipipe-core-4.19.55-arm64-4.patch
* Xenomai-3.1-rc3
When I build with arm64 and run it on a Raspberry Pi 3,
mmap fails when I run userland tools.
(The situation is the same for all tools such as corectl.)
I think
On 12/2/19 7:46 AM, Jan Kiszka wrote:
> On 30.11.19 19:39, Philippe Gerum via Xenomai wrote:
>> From: Philippe Gerum
>>
>> rtdm_nrtsig_pend() is based on ipipe_post_root_work(), which keeps a
>> copy of every request descriptor internally until it is consumed by
>> the secondary mode handler. Trig
From: Philippe Gerum
rtdm_nrtsig_pend() is based on ipipe_post_root_work(), which keeps a
copy of every request descriptor internally until it is consumed by
the secondary mode handler. Triggering rtdm_nrtsig_pend() every time a
packet is relayed from the stack to the tap device may cause such
re
On 12/2/19 7:42 AM, Jan Kiszka wrote:
> On 29.11.19 19:37, Philippe Gerum wrote:
>> On 11/29/19 7:04 PM, Jan Kiszka wrote:
>>> On 28.11.19 11:02, Philippe Gerum via Xenomai wrote:
From: Philippe Gerum
static inline int rtdm_task_set_period(rtdm_task_t *task,
@@ -1062,9 +10
From: Philippe Gerum
Kicking the rescheduling procedure (xnsched_run()) from call sites
running over the root thread with hard irqs enabled may lead to
missing a rescheduling opportunity as a consequence of a CPU
migration, e.g.:
CPU0CPU1
It has been two years since I stepped down as Xenomai's lead maintainer.
In the meantime, Jan took over and did a very good job in this role as
expected.
Since this transition period is now taking an end, I'm switching focus
to the EVL project [1] I have been nurturing for some time, with the
go
- Den 2 dec 2019, på kl 17:05, xenomai xenomai@xenomai.org skrev:
> It has been two years since I stepped down as Xenomai's lead maintainer.
> In the meantime, Jan took over and did a very good job in this role as
> expected.
> Since this transition period is now taking an end, I'm switching
On Mon, Dec 2, 2019 at 11:22 AM Per Oberg via Xenomai
wrote:
>
> - Den 2 dec 2019, på kl 17:05, xenomai xenomai@xenomai.org skrev:
>
> > It has been two years since I stepped down as Xenomai's lead maintainer.
> > In the meantime, Jan took over and did a very good job in this role as
> > expec
On 02.12.19 16:18, Philippe Gerum via Xenomai wrote:
> From: Philippe Gerum
>
> rtdm_nrtsig_pend() is based on ipipe_post_root_work(), which keeps a
> copy of every request descriptor internally until it is consumed by
> the secondary mode handler. Triggering rtdm_nrtsig_pend() every time a
> pac
On 02.12.19 16:35, Philippe Gerum via Xenomai wrote:
> From: Philippe Gerum
>
> Kicking the rescheduling procedure (xnsched_run()) from call sites
> running over the root thread with hard irqs enabled may lead to
> missing a rescheduling opportunity as a consequence of a CPU
> migration, e.g.:
>
14 matches
Mail list logo
