RE: [Cobalt Xenoami3.1 PATCH 1/2] process: update clockfreq when receive corresponding event.

>-Original Message- >From: Xenomai On Behalf Of Chen, Hongzhan via >Xenomai >Sent: Wednesday, June 15, 2022 9:29 AM >To: Kiszka, Jan ; xenomai@xenomai.org >Subject: RE: [Cobalt Xenoami3.1 PATCH 1/2] process: update clockfreq when >receive corresponding event. > > > >>-Original

Reminder: Xenomai community call on Wednesday, Jun 15, 2022, UTC 7:00 AM

We have the Xenomai community call today. Topics may include but are not limited to upstream/downstream project plans, status updates, and technical discussions. It's an open online meeting that anyone can join and ask questions. Time: Wednesday, Jun 15, 2022, UTC 7:00 AM Paris, France CEST

RE: [I-PIPE Xenoami3.1 PATCH 2/2] x86/tsc: I-PIPE : notify I-PIPE about updated clockfreq

> >Xenomai is conceptually not known to I-pipe. This patch is about calling >the well-defined kevent hook when the TSC frequency changes after a >recalibration. ARM does something similar on frequency changes. > >> Linux may schedule a delayed work to refine tsc clock and update >> tsc_khz which

RE: [Cobalt Xenoami3.1 PATCH 1/2] process: update clockfreq when receive corresponding event.

>-Original Message- >From: Jan Kiszka >Sent: Wednesday, June 15, 2022 5:28 AM >To: Chen, Hongzhan ; xenomai@xenomai.org >Subject: Re: [Cobalt Xenoami3.1 PATCH 1/2] process: update clockfreq when >receive corresponding event. > >On 27.05.22 08:22, Hongzhan Chen via Xenomai wrote: >> 1.

EVL Heap Clarification

4 of these functions were being called from an EVL attached thread. -- next part -- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 6759 bytes Desc: not available URL: <http://xenomai.org/pipermail/xenomai/attachments/20220

Re: [I-PIPE Xenoami3.1 PATCH 2/2] x86/tsc: I-PIPE : notify I-PIPE about updated clockfreq

On 27.05.22 08:22, Hongzhan Chen via Xenomai wrote: > When there is refined tsc clock, notify Xenomai to apply it. Xenomai is conceptually not known to I-pipe. This patch is about calling the well-defined kevent hook when the TSC frequency changes after a recalibration. ARM does something similar

Re: [Cobalt Xenoami3.1 PATCH 1/2] process: update clockfreq when receive corresponding event.

On 27.05.22 08:22, Hongzhan Chen via Xenomai wrote: > 1. When there is clockfreq param passed down via command line, we >do not update clockfreq even if we receive event of updating clockfreq. >Or else, we update the clockfreq with notified value. > 2. At the same time, we would like to

Re: [PATCH 2/2] x86: ipipe: Enable FPU tests unconditionally

On 08.06.22 18:59, Bezdeka, Florian (T CED SES-DE) wrote: > On Wed, 2022-06-08 at 17:02 +0200, Jan Kiszka wrote: >> On 25.05.22 11:56, Florian Bezdeka wrote: >>> Parts of the FPU tests were skipped when one of the following config >>> options was enabled, shadowing a real test issue that was

Re: [PATCH] rtdm/drvlib: Prevent pagefaults on arm on io mapping

On 23.05.22 16:04, Gunter Grau via Xenomai wrote: > From: Gunter Grau > > When mapping io memory into userspace an extra simulated pagefault for all > pages is added to prevent later pagefaults because of copy on write > mechanisms. This happens only on architectures that have defined the >

RE: [External] - Re: compile conflict with Boost

tachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 6759 bytes Desc: not available URL: <http://xenomai.org/pipermail/xenomai/attachments/20220614/ccefc832/attachment.bin>

Re: compile conflict with Boost

Jan Kiszka writes: > On 14.06.22 16:18, Russell Johnson via Xenomai wrote: >> From 452e8b2ca8ecd53571a6b1f5d8b9ab23cd67f99d Mon Sep 17 00:00:00 2001 >> From: Russell Johnson >> Date: Tue, 14 Jun 2022 08:10:14 -0600 >> Subject: [PATCH] fixing conflict with C++ [[fallthough]], and maybe at some

Re: compile conflict with Boost

On 14.06.22 16:18, Russell Johnson via Xenomai wrote: > From 452e8b2ca8ecd53571a6b1f5d8b9ab23cd67f99d Mon Sep 17 00:00:00 2001 > From: Russell Johnson > Date: Tue, 14 Jun 2022 08:10:14 -0600 > Subject: [PATCH] fixing conflict with C++ [[fallthough]], and maybe at some > point in the future with

Re: compile conflict with Boost

Russell Johnson writes: > [[S/MIME Signed Part:Undecided]] > From 452e8b2ca8ecd53571a6b1f5d8b9ab23cd67f99d Mon Sep 17 00:00:00 2001 > From: Russell Johnson > Date: Tue, 14 Jun 2022 08:10:14 -0600 > Subject: [PATCH] fixing conflict with C++ [[fallthough]], and maybe at some > point in the

Re: compile conflict with Boost

-signature Size: 6759 bytes Desc: not available URL: <http://xenomai.org/pipermail/xenomai/attachments/20220614/376ef8cc/attachment.bin>

Re: [External] - Re: compile conflict with Boost

Russell Johnson writes: > [[S/MIME Signed Part:Undecided]] > This is what I have been using. I have tested it and it seems to work fine. > > Thanks, > > Russell > > diff --git a/benchmarks/hectic.c b/benchmarks/hectic.c > index 6b6b3b5..886f7d2 100644 > --- a/benchmarks/hectic.c > +++

RE: [External] - Re: compile conflict with Boost

<http://xenomai.org/pipermail/xenomai/attachments/20220614/b4791815/attachment.bin>

Re: compile conflict with Boost

Julien Blanc writes: > Le mardi 14 juin 2022 à 09:44 +, Bezdeka, Florian a écrit : >> >> Based on the kernel's fallthrough, introducing evl_fallthrough would >> avoid all kinds of conflicts (IMHO): >> >> #ifndev evl_fallthrough >> #if __has_attribute(__fallthrough__) >> # define

Re: compile conflict with Boost

Le mardi 14 juin 2022 à 09:44 +, Bezdeka, Florian a écrit : > > Based on the kernel's fallthrough, introducing evl_fallthrough would > avoid all kinds of conflicts (IMHO): > > #ifndev evl_fallthrough > #if __has_attribute(__fallthrough__) > # define evl_fallthrough

Re: compile conflict with Boost

On Tue, 2022-06-14 at 11:01 +0200, Philippe Gerum via Xenomai wrote: > Julien Blanc writes: > > > Le mardi 14 juin 2022 à 10:04 +0200, Philippe Gerum a écrit : > > > Julien Blanc < > > > julien.bl...@sprinte.eu > > > > writes: > > > > > > > Le mardi 14 juin 2022 à 08:54 +0200, Philippe Gerum a

Re: compile conflict with Boost

Julien Blanc writes: > Le mardi 14 juin 2022 à 10:04 +0200, Philippe Gerum a écrit : >> Julien Blanc < >> julien.bl...@sprinte.eu >> > writes: >> >> > Le mardi 14 juin 2022 à 08:54 +0200, Philippe Gerum a écrit : >> > > Julien Blanc via Xenomai >> > > > #define __fallthrough

Re: compile conflict with Boost

On Tue, 2022-06-14 at 08:29 +, Julien Blanc via Xenomai wrote: > Le mardi 14 juin 2022 à 10:04 +0200, Philippe Gerum a écrit : > > Julien Blanc < > > julien.bl...@sprinte.eu > > > writes: > > > > > Le mardi 14 juin 2022 à 08:54 +0200, Philippe Gerum a écrit : > > > > Julien Blanc via Xenomai

Re: compile conflict with Boost

Le mardi 14 juin 2022 à 10:04 +0200, Philippe Gerum a écrit : > Julien Blanc < > julien.bl...@sprinte.eu > > writes: > > > Le mardi 14 juin 2022 à 08:54 +0200, Philippe Gerum a écrit : > > > Julien Blanc via Xenomai > > > > #define __fallthrough __attribute__((fallthrough)) > > > > > > > > >

Re: compile conflict with Boost

Julien Blanc writes: > Le mardi 14 juin 2022 à 08:54 +0200, Philippe Gerum a écrit : >> Julien Blanc via Xenomai >> > >> > #define __fallthrough __attribute__((fallthrough)) >> > >> >> 6.39. attribute syntax >> https://gcc.gnu.org/onlinedocs/gcc/Attribute-Syntax.html#Attribute-Syntax

Re: compile conflict with Boost

Le mardi 14 juin 2022 à 08:54 +0200, Philippe Gerum a écrit : > Julien Blanc via Xenomai > > > > #define __fallthrough __attribute__((fallthrough)) > > > > 6.39. attribute syntax > https://gcc.gnu.org/onlinedocs/gcc/Attribute-Syntax.html#Attribute-Syntax > Not sure what you mean with

Re: compile conflict with Boost

Julien Blanc via Xenomai writes: > Le lundi 13 juin 2022 à 14:39 +, Russell Johnson via Xenomai a > écrit : >> I use boost throughout my entire app, so I need >> to figure how to get both of these libraries to play nice with each >> other. Any ideas? ( I am using gcc 8.3 and boost 1.70.0)