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.

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 ha

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.

RE: [Cobalt Xenoami3.1 PATCH 0/2] notify Xenomai udpated clockfreq.

>-Original Message- >From: Jan Kiszka >Sent: Thursday, June 9, 2022 1:48 PM >To: Chen, Hongzhan ; xenomai@xenomai.org >Subject: Re: [Cobalt Xenoami3.1 PATCH 0/2] notify Xenomai udpated clockfreq. > >On 09.06.22 04:06, Chen, Hongzhan wrote: >>> -Original Message- >>> From: Jan Kis

RE: [Cobalt Xenoami3.1 PATCH 0/2] notify Xenomai udpated clockfreq.

>-Original Message- >From: Jan Kiszka >Sent: Wednesday, June 8, 2022 11:21 PM >To: Chen, Hongzhan ; xenomai@xenomai.org >Subject: Re: [Cobalt Xenoami3.1 PATCH 0/2] notify Xenomai udpated clockfreq. > >On 02.06.22 14:56, Chen, Hongzhan wrote: >> >> >>> -Original Message- >>> From

RE: [Cobalt Xenoami3.1 PATCH 0/2] notify Xenomai udpated clockfreq.

>-Original Message- >From: Jan Kiszka >Sent: Thursday, June 2, 2022 5:54 PM >To: Chen, Hongzhan ; xenomai@xenomai.org >Subject: Re: [Cobalt Xenoami3.1 PATCH 0/2] notify Xenomai udpated clockfreq. > >On 27.05.22 08:22, Hongzhan Chen via Xenomai wrote: >> When there is refined tsc clock,

Reminder: Xenomai community call on Wednesday, Jun 1, 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 1, 2022, UTC 7:00 AM Paris, France CEST 9:

RE: Difference between Xenomai timer and Linux clock

>-Original Message- >From: Prasanna Kannan >Sent: Monday, May 30, 2022 3:33 PM >To: Chen, Hongzhan ; xenomai@xenomai.org >Subject: AW: Difference between Xenomai timer and Linux clock > >> -Ursprüngliche Nachricht- >> Von: Chen, Hongzhan [mailto:hongzhan.c...@intel.com] >> Gese

RE: Difference between Xenomai timer and Linux clock

>-Original Message- >From: Xenomai On Behalf Of Prasanna Kannan via >Xenomai >Sent: Friday, May 27, 2022 9:39 PM >To: xenomai@xenomai.org >Subject: Difference between Xenomai timer and Linux clock > >Hello Everybody, > >I am comparing the Xenomai Timer(rt_timer_read()) and clock_gettim

Reminder: Xenomai community call on Wednesday, May 18, 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, May 18, 2022, UTC 7:00 AM Paris, France CEST 9

Xenomai Community Call Minutes - May 04, 2022

Attendees: Jan Kiszka, Rick Wang, Richard Weinberger, Johannes Kirchmair, Florian Bezdeka, Hongzhan Chen *Community update: Register (or stack) corruption issue discussion: Need to check if related to kconfig /sched switch/ memory alloc and further debug Meetu

Reminder: Xenomai community call on Wednesday, May 04, 2022, UTC 7:00 AM

Correction: Wednesday, May 04, 2022, UTC 7:00 AM Sorry for the mistake. Regards Hongzhan Chen -Original Message- From: Chen, Hongzhan Sent: Tuesday, May 3, 2022 9:35 AM To: xenomai@xenomai.org Subject: Reminder: Xenomai community call on Wednesday, May 03, 2022, UTC 7:00 AM Topics m

Reminder: Xenomai community call on Wednesday, May 03, 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, May 03, 2022, UTC 7:00 AM Paris, France CEST 9:0

Xenomai Community Call Minutes - Apr 20, 2022

Attendees: Jan Kiszka, Rick Wang, Richard Weinberger, Fanjun Kong, Florian Bezdeka, Jianbo Cao, Qiang Zhang, Hongzhan Chen *Community update: Reviving Analog driver required by new user & contributor. Realtime clocksource regression issue on Xenomai 3.2 -- work-around by modifyi

Reminder: Xenomai community call on Wednesday, Apr 20, 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, Apr 20, 2022, UTC 7:00 AM Paris, France CEST 9:0

Xenomai Community Call Minutes - Apr 06, 2022

Attendees: Jan Kiszka, Rick Wang, Richard Weinberger, Jianbo Cao, Qiang Zhang, Hongzhan Chen *Community update: Xenomai Meetup CFP discussion - Jan will announce CFP soon. Comprehensive discussion on issues raised by Richard Weinberger recently * I/O test broken on dovetai

RE: Reminder: Xenomai community call on Wednesday, Apr 06, 2022, UTC 7:00 AM

, 2022, UTC 7:00 AM On Wed, 2022-04-06 at 04:54 +, Chen, Hongzhan via Xenomai wrote: > 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 >

Reminder: Xenomai community call on Wednesday, Apr 06, 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, Apr 06, 2022, UTC 7:00 AM Paris, France CEST 8:0

RE: [linux-dovetail PATCH 2/2] clocksource: GENERIC_CLOCKSOURCE_VDSO only supported on ARM

>-Original Message- >From: Philippe Gerum >Sent: Saturday, April 2, 2022 5:11 PM >To: Chen, Hongzhan >Cc: xenomai@xenomai.org >Subject: Re: [linux-dovetail PATCH 2/2] clocksource: GENERIC_CLOCKSOURCE_VDSO >only supported on ARM > > >Hongzhan Chen via Xenomai writes: > >> Currently, GEN

RE: Understanding output of /proc/xenomai/sched/rt/threads

>-Original Message- >From: Xenomai On Behalf Of Sam Daniel via Xenomai >Sent: Friday, April 1, 2022 12:07 AM >To: xenomai@xenomai.org >Subject: Understanding output of /proc/xenomai/sched/rt/threads > >What does the PERIOD column mean? > >Some of my processes show a period of 1s, others s

Xenomai Community Call Minutes - Mar 23, 2022

Attendees: Jan Kiszka, Rick Wang, Peter Steub, Jianbo Cao, Qiang Zhang, Hongzhan Chen *Community update: Three bugs fixed on ipipe/pcie and xenomai 3.2.x Xenomai Meetup agenda discussion and live streaming function test. Xenomai 4 discussion - migration is tough cur

Reminder: Xenomai community call on Wednesday, Mar 23, 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, Mar 23, 2022, UTC 7:00 AM Paris, France CEST 8:0

RE: CONFIG_NO_HZ_FULL = y but still have arch-timer on isolation CPUs

Hi Ivan The description I posted follows " Got it to work. My final set of kernel parameters was isolcpus=nohz,domain,8-15 nohz_full=8-15. Moreover, I realized that I was running my program with FIFO scheduling via chrt -f but forgot to set /proc/sys/kernel/sched_rt_runtime_us to -1, which intr

RE: CONFIG_NO_HZ_FULL = y but still have arch-timer on isolation CPUs

Hi Ivan According to the description "@sevko I found that I didn't need the nohz_full= (I think it's redundant given the isolcpus=nohz) but I had to add tsc=reliable, on CentOS 8 with kernel 4.18. – Joshua Chia" , it seems that there is solution with 4.18 , which should work with 4.19? Regard

RE: CONFIG_NO_HZ_FULL = y but still have arch-timer on isolation CPUs

Hi Ivan Hope that what discussed in https://stackoverflow.com/questions/60322119/completely-eliminating-the-timer-tick-in-modern-linux-5-0 may help you. Seems that there need do more settings for kernel parameters per your requirement but I have not tried myself. When you remove Xenomai, th

RE: [PATCH v8 0/4] Kernel-Shark and libtraceevent plugins

Looks good to me. Thanks for your help. Regards Hongzhan Chen -Original Message- From: Jan Kiszka Sent: Monday, March 14, 2022 6:01 PM To: xenomai@xenomai.org Cc: Chen, Hongzhan Subject: [PATCH v8 0/4] Kernel-Shark and libtraceevent plugins Changes in v8: - drop explicit deps again

RE: [PATCH v7 1/3] build: add options to build plugins of kernelshark and libtraceevent

>On 14.03.22 07:48, Chen, Hongzhan wrote: >> -Original Message- >> From: Jan Kiszka >>> Sent: Monday, March 14, 2022 2:41 PM >>> To: Chen, Hongzhan ; xenomai@xenomai.org >>> Subject: Re: [PATCH v7 1/3] build: add options to build plugins of >>> kernelshark and libtraceevent >>> >>> On 14

RE: [PATCH v7 1/3] build: add options to build plugins of kernelshark and libtraceevent

-Original Message- From: Jan Kiszka >Sent: Monday, March 14, 2022 2:41 PM >To: Chen, Hongzhan ; xenomai@xenomai.org >Subject: Re: [PATCH v7 1/3] build: add options to build plugins of kernelshark >and libtraceevent > >On 14.03.22 02:27, Chen, Hongzhan wrote: >>> >>> >>> -Original Mes

RE: [PATCH v7 1/3] build: add options to build plugins of kernelshark and libtraceevent

> Message- >From: Chen, Hongzhan >Sent: Monday, March 14, 2022 9:40 AM >To: 'Jan Kiszka' ; 'xenomai@xenomai.org' > >Subject: RE: [PATCH v7 1/3] build: add options to build plugins of kernelshark >and libtraceevent > >>>-Original Message- >>>From: Jan Kiszka >>>Sent: Saturday, Ma

RE: [PATCH v7 1/3] build: add options to build plugins of kernelshark and libtraceevent

>>-Original Message- >>From: Jan Kiszka >>Sent: Saturday, March 12, 2022 9:00 PM >>To: xenomai@xenomai.org >>Cc: Chen, Hongzhan >>Subject: [PATCH v7 1/3] build: add options to build plugins of kernelshark >>and libtraceevent >> >>From: Hongzhan Chen >> >>To build plugins of kernelshark

RE: [PATCH v7 1/3] build: add options to build plugins of kernelshark and libtraceevent

> > >-Original Message- >From: Jan Kiszka >Sent: Saturday, March 12, 2022 9:00 PM >To: xenomai@xenomai.org >Cc: Chen, Hongzhan >Subject: [PATCH v7 1/3] build: add options to build plugins of kernelshark and >libtraceevent > >From: Hongzhan Chen > >To build plugins of kernelshark and li

RE: [PATCH 2/4] build: add options to build plugins of kernelshark and libtraceevent

>>> Jan >>> >> >> CFLAGS and LDFLAGS are not set for both plugins, so the build fails. >> I'll fix this up as well. >> > >It was rather related to missing dependencies (libtraceevent and >libtracefs). > >Also, *_INSTALLDIR does not work properly. It ignores --prefix and >DESTDIR. Will try to res

RE: [PATCH 2/4] build: add options to build plugins of kernelshark and libtraceevent

>>> + >>> +if test x$kernelshark_plugin = xy -o x$libtraceevent_plugin = xy; then >>> + PKG_CHECK_MODULES(LIBTRACEEVENT, libtraceevent) >>> + PKG_CHECK_VAR(XENO_LIBTRACEEVENT_INSTALLDIR, libtraceevent, libdir) >>> +fi >>> + >>> +if test x$kernelshark_plugin = xy; then >>> + PKG_CHECK_MODULES(

RE: [PATCH v5 2/3] KernelShark: Add xenomai_cobalt_switch_events plugin for KernelShark

... >> +libplugin_xenomai_cobalt_switch_events_la_CPPFLAGS = \ >> +$(KS_INCLUDS) >> + >> +install-libLTLIBRARIES: $(lib_LTLIBRARIES) >> +echo "$(LIBTOOL) $(AM_LIBTOOLFLAGS) $(LIBTOOLFLAGS) --mode=install \ >> +$(INSTALL_DATA) $(lib_LTLIBRARIES) >> '$(KS_INSTALLDIR)/kern

reminder: Xenomai community call on Wednesday, Mar 09, 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, Mar 09, 2022, UTC 7:00 AM Paris, France CEST 8:0

RE: [PATCH v4 3/3] libtraceevent: Add xenomai_schedparams plugin for libtraceevent

>> + >> + Please copy built libplugin_xenomai_schedparams.so to >> + /usr/local/lib/traceevent/plugins/ or >> + /usr/local/lib64/traceevent/plugins/ depending on your system. >> + While libtracevent and its plugins is installed correctly, the plugins >> + would be loaded automatically by other

RE: [PATCH v3] libtraceevent: Add xenomai_schedparams plugin for libtraceevent

>>-Original Message- >>From: Jan Kiszka >>Sent: Thursday, March 3, 2022 3:01 PM >>To: Chen, Hongzhan ; xenomai@xenomai.org; >>florian.bezd...@siemens.com >>Subject: Re: [PATCH v3] libtraceevent: Add xenomai_schedparams plugin for >>libtraceevent >> > + libtraceevent +els

RE: [PATCH v3] libtraceevent: Add xenomai_schedparams plugin for libtraceevent

>-Original Message- >From: Jan Kiszka >Sent: Thursday, March 3, 2022 3:01 PM >To: Chen, Hongzhan ; xenomai@xenomai.org; >florian.bezd...@siemens.com >Subject: Re: [PATCH v3] libtraceevent: Add xenomai_schedparams plugin for >libtraceevent > >On 03.03.22 07:57, Jan Kiszka via Xenomai w

RE: [PATCH v2 2/3] Add --with-kernelshark option

>-Original Message- >From: Jan Kiszka >Sent: Thursday, March 3, 2022 2:39 PM >To: Chen, Hongzhan ; xenomai@xenomai.org >Subject: Re: [PATCH v2 2/3] Add --with-kernelshark option > >On 03.03.22 07:30, Chen, Hongzhan wrote: >> >> >> + tracing/Makefile \ + tracing/kernelshar

RE: [PATCH v2 2/3] Add --with-kernelshark option

>> +tracing/Makefile \ >> +tracing/kernelshark/Makefile \ >> lib/Makefile \ >> lib/boilerplate/Makefile \ >> lib/boilerplate/init/Makefile \ >> diff --git a/tracing/Makefile.am b/tracing/Makefile.am >> index 8bdf1f906..7925ae9c6 100644 >> --- a/tracing/Makefile.am >> +++ b

RE: [PATCH 1/4] build: Add c++ build support

>-Original Message- >From: Jan Kiszka >Sent: Tuesday, March 1, 2022 3:31 PM >To: Chen, Hongzhan ; xenomai@xenomai.org >Subject: Re: [PATCH 1/4] build: Add c++ build support > >On 28.02.22 06:40, Hongzhan Chen wrote: >> Add c++ build support or use specific c++ compiler >> >> Signed-off-b

RE: [PATCH 4/4] libtraceevent: Add Add xenomai_schedparams plugin for libtraceevent

> >-Original Message- >From: Jan Kiszka >Sent: Tuesday, March 1, 2022 3:41 PM >To: Chen, Hongzhan ; xenomai@xenomai.org >Subject: Re: [PATCH 4/4] libtraceevent: Add Add xenomai_schedparams plugin for >libtraceevent > >On 28.02.22 06:40, Hongzhan Chen wrote: >> For cobalt thread, there i

RE: [PATCH 2/4] Kernel-shark: Add xenomai_cobalt_switch_events plugin for kernel-shark

>-Original Message- >From: Jan Kiszka >Sent: Tuesday, March 1, 2022 3:40 PM >To: Chen, Hongzhan ; xenomai@xenomai.org >Subject: Re: [PATCH 2/4] Kernel-shark: Add xenomai_cobalt_switch_events plugin >for kernel-shark > >On 28.02.22 06:40, Hongzhan Chen wrote: >> For Xenomai-cobalt enabl

Xenomai Community Call Minutes - Feb 23, 2022

Attendees: Jan Kiszka, Rick Wang, Florian Bezdeka, Jianbo Cao, Qiang Zhang, Li Hao, Hongzhan Chen *Community update: Xenomai 3.3 - ongoing with bug fixing. Xenomai meetup in Q2 - preparing. Regards Hongzhan Chen

RE: [PATCH 0/2] kernel-shark related patches

>-Original Message- >From: Jan Kiszka >Sent: Wednesday, February 23, 2022 2:51 PM >To: Chen, Hongzhan ; xenomai@xenomai.org >Cc: y.kar...@gmail.com >Subject: Re: [PATCH 0/2] kernel-shark related patches > >On 22.02.22 03:30, Hongzhan Chen wrote: >> 1. Add kernel-shark plugin to visualize

RE: Realtime interrupt handling in driver

>-Original Message- >From: Xenomai On Behalf Of Russell Johnson via >Xenomai >Sent: Wednesday, February 23, 2022 8:10 AM >To: xenomai@xenomai.org >Subject: Realtime interrupt handling in driver > >Hello, > >In my driver that I have been converting to support OOB functionality with the >E

reminder: Xenomai community call on Wednesday, Feb 23, 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, Feb 23, 2022, UTC 7:00 AM Paris, France CEST 8

RE: Compiling xenomai-linux 5.10.83

>-Original Message- >From: Xenomai On Behalf Of Andrew via Xenomai >Sent: Wednesday, February 23, 2022 3:56 AM >To: xenomai@xenomai.org >Subject: Compiling xenomai-linux 5.10.83 > >Hi, > >I am trying to work on a project that is easiest to accomplish if I base my >changes on a product tha

Xenomai Community Call Minutes - Jan 26, 2022

Attendees: Jan Kiszka, Rick Wang, Florian Bezdeka, Jianbo Cao, Qiang Zhang, Li Hao, Steve, Hongzhan Chen *Community update: Bug related: Huge Page issue fixed in 5.15 and would be backported to 5.10. Kernel-shark & libtraceevent patches for upstream repo is ready but need to

eminder: Xenomai community call on Wednesday, Jan 26, 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, Jan 26, 2022, UTC 7:00 AM Paris, France CEST 8:0

RE: [PATCH] kernel-shark: Add plugin for handling Xenomai cobalt_context_switch

-Original Message- >From: Jan Kiszka >Sent: Wednesday, January 26, 2022 12:37 AM >To: Chen, Hongzhan ; xenomai@xenomai.org >Subject: Re: [PATCH] kernel-shark: Add plugin for handling Xenomai >cobalt_context_switch > >On 18.01.22 04:45, Hongzhan Chen wrote: >> For Xenomai-cobalt enable

RE: About the kernel configuration(CONFIG_CPU_FREQ and CONFIG_CPU_IDLE.)

>From: ??? sunshilong >Sent: Thursday, January 20, 2022 4:26 PM >To: Chen, Hongzhan >Cc: xenomai@xenomai.org >Subject: Re: About the kernel configuration(CONFIG_CPU_FREQ and >CONFIG_CPU_IDLE.) > >> Please try if can enter into advanced->power & performance -> CPU - Power >> Management Contr

RE: About the kernel configuration(CONFIG_CPU_FREQ and CONFIG_CPU_IDLE.)

>From: ??? sunshilong >Sent: Thursday, January 20, 2022 3:12 PM >To: Chen, Hongzhan >Cc: xenomai@xenomai.org >Subject: Re: About the kernel configuration(CONFIG_CPU_FREQ and >CONFIG_CPU_IDLE.) > >>>Let us go back to what you found with disabling CPU_IDLE and CPU_FREQ. I do >>>not know if you a

RE: About the kernel configuration(CONFIG_CPU_FREQ and CONFIG_CPU_IDLE.)

>From: ??? sunshilong >Sent: Thursday, January 20, 2022 2:25 PM >To: Chen, Hongzhan >Cc: xenomai@xenomai.org >Subject: Re: About the kernel configuration(CONFIG_CPU_FREQ and >CONFIG_CPU_IDLE.) > >>Let us go back to what you found with disabling CPU_IDLE and CPU_FREQ. I do >>not know if you alr

RE: About the kernel configuration(CONFIG_CPU_FREQ and CONFIG_CPU_IDLE.)

> >From: ??? sunshilong sunshilong...@gmail.com >>Sent: Wednesday, January 19, 2022 5:01 PM >>To: Chen, Hongzhan hongzhan.c...@intel.com >>Subject: Re: About the kernel configuration(CONFIG_CPU_FREQ and >>CONFIG_CPU_IDLE.) >> >>> Did

RE: About the kernel configuration(CONFIG_CPU_FREQ and CONFIG_CPU_IDLE.)

From: ??? sunshilong sunshilong...@gmail.com >Sent: Wednesday, January 19, 2022 5:01 PM >To: Chen, Hongzhan hongzhan.c...@intel.com >Subject: Re: About the kernel configuration(CONFIG_CPU_FREQ and >CONFIG_CPU_IDLE.) > >> Did you use

RE: About the kernel configuration(CONFIG_CPU_FREQ and CONFIG_CPU_IDLE.)

>>-Original Message- >>From: Xenomai On Behalf Of ??? sunshilong via >>Xenomai >>Sent: Tuesday, January 18, 2022 3:18 PM >>To: xenomai >>Subject: Re: About the kernel configuration(CONFIG_CPU_FREQ and >>CONFIG_CPU_IDLE.) >> >>Sorry, there is a clerical error in the last mail. >> >

RE: About the kernel configuration(CONFIG_CPU_FREQ and CONFIG_CPU_IDLE.)

>-Original Message- >From: Xenomai On Behalf Of ??? sunshilong via >Xenomai >Sent: Tuesday, January 18, 2022 3:18 PM >To: xenomai >Subject: Re: About the kernel configuration(CONFIG_CPU_FREQ and >CONFIG_CPU_IDLE.) > >Sorry, there is a clerical error in the last mail. > >>It should be

RE: [PATCH] libtraceevent: Add new xenomai plugin to print param_ex correctly

> >> +/* >> + * Copyright (C) 2021 Intel Inc, Hongzhan Chen >> + */ >> +#include >> +#include >> +#include >> +#include >> + >> +#include "event-parse.h" >> +#include "trace-seq.h" >> + >> + >> +#define SCHED_SPORADIC 10 >> +#define SCHED_TP11 >> +#define SCHED_QUOTA

Xenomai Community Call Minutes - Jan 12, 2022

Attendees: Jan Kiszka, Rick Wang, Florian Bezdeka, Jianbo Cao, Qiang Zhang, Hongzhan Chen *Community update: 1. 5.15 Linux related bug fixing 2. xenomai 3.3 ongoing - drop and adjust some APIs and remove IPIPE. 3. kernel-shark bug fixing - ongoing. 4. Can driver and corre

reminder: Xenomai community call on Wednesday, Jan 12, 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, Jan 12, 2022, UTC 7:00 AM Paris, France CEST 8:0

Xenomai Community Call Minutes - Dec 15, 2021

Attendees: Jan Kiszka, Rick Wang, Hao,Li, cwb, Hongzhan Chen *Community update: 1. three stable branch maintained currently(3.0 , 3. 1, 3.2). 2. kernel-shark improvement patchset for Xenomai visualizaion: Function basically meet our requirement to visualize OOB state e

reminder: Xenomai community call on Wednesday, Dec 15, 2021, 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, Dec 15, 2021, UTC 7:00 AM Paris, France CEST 8:0

RE: [RFC PATCH 1/2] kernel-shark: add plugin for handling xenomai cobalt context switch event

>-Original Message- >From: Jan Kiszka >Sent: Tuesday, December 14, 2021 3:51 PM >To: Chen, Hongzhan ; xenomai@xenomai.org >Subject: Re: [RFC PATCH 1/2] kernel-shark: add plugin for handling xenomai >cobalt context switch event > >On 14.12.21 08:46, Chen, Hongzhan wrote: >> >>

RE: [RFC PATCH 1/2] kernel-shark: add plugin for handling xenomai cobalt context switch event

BTW, is that blue hollow box exclusive for our plugin? Or can this be customized? Is it explained somewhere in Kernelshark what hollow boxes mean? >>> >>> Some visualization issue: >>> >>>pthelper-912 [000] 753.948271: cobalt_schedule: >>> status=0x1

RE: [RFC PATCH 1/2] kernel-shark: add plugin for handling xenomai cobalt context switch event

>-Original Message- >From: Jan Kiszka >Sent: Tuesday, December 14, 2021 3:02 PM >To: Chen, Hongzhan ; xenomai@xenomai.org >Subject: Re: [RFC PATCH 1/2] kernel-shark: add plugin for handling xenomai >cobalt context switch event > >On 14.12.21 07:49, Jan Kiszka via Xenomai wrote: >> On

RE: [RFC PATCH 2/2] kernelshark: shape blue hollow box to show OOB state of task

>-Original Message- >From: Jan Kiszka >Sent: Tuesday, December 14, 2021 2:49 PM >To: Chen, Hongzhan ; xenomai@xenomai.org >Subject: Re: [RFC PATCH 1/2] kernel-shark: add plugin for handling xenomai >cobalt context switch event > >On 14.12.21 07:44, Chen, Hongzhan wrote: >>> >>> >>>

RE: [RFC PATCH 1/2] kernel-shark: add plugin for handling xenomai cobalt context switch event

> > >-Original Message- >From: Jan Kiszka >Sent: Tuesday, December 14, 2021 2:38 PM >To: Chen, Hongzhan ; xenomai@xenomai.org >Subject: Re: [RFC PATCH 1/2] kernel-shark: add plugin for handling xenomai >cobalt context switch event > >On 14.12.21 04:15, Hongzhan Chen wrote: >> For Xenomai

RE: [RFC PATCH V2] kernel-shark: add plugin for handling xenomai cobalt context switch event

>-Original Message- >From: Jan Kiszka >Sent: Monday, December 13, 2021 3:50 PM >To: Chen, Hongzhan ; xenomai@xenomai.org >Subject: Re: [RFC PATCH V2] kernel-shark: add plugin for handling xenomai >cobalt context switch event > >On 13.12.21 02:55, Hongzhan Chen wrote: >> For Xenomai-cob

RE: questions about comments on https://gitlab.com/Xenomai/xenomai-hacker-space/-/issues/33

>>-Original Message- >>From: Jan Kiszka >>Sent: Thursday, December 9, 2021 5:35 PM >>To: Chen, Hongzhan ; xenomai@xenomai.org >>Subject: Re: questions about comments on >>https://gitlab.com/Xenomai/xenomai-hacker-space/-/issues/33 >> >>On 07.12.21 04:11, Chen, Hongzhan wrote: >>> Hi

RE: questions about comments on https://gitlab.com/Xenomai/xenomai-hacker-space/-/issues/33

>-Original Message- >From: Jan Kiszka >Sent: Thursday, December 9, 2021 5:35 PM >To: Chen, Hongzhan ; xenomai@xenomai.org >Subject: Re: questions about comments on >https://gitlab.com/Xenomai/xenomai-hacker-space/-/issues/33 > >On 07.12.21 04:11, Chen, Hongzhan wrote: >> Hi Jan >> >>

RE: questions about comments on https://gitlab.com/Xenomai/xenomai-hacker-space/-/issues/33

> >-Original Message- >From: Chen, Hongzhan >Sent: Tuesday, December 7, 2021 11:11 AM >To: xenomai@xenomai.org; Jan Kiszka >jan.kis...@siemens.com >Subject: questions about comments on >https://gitlab.com/Xenomai/xenomai-hacker-

questions about comments on https://gitlab.com/Xenomai/xenomai-hacker-space/-/issues/33

Hi Jan I have some questions about comments on https://gitlab.com/Xenomai/xenomai-hacker-space/-/issues/33 and need your help to comment more. 1. I do not quite understand the requirement "visualize task switches correctly in Kernelshark (color in CPU bar is not updating on cobalt_switch_cont

Xenomai Community Call Minutes - Dec 1,2021

Of Chen, Hongzhan via Xenomai Sent: Wednesday, December 1, 2021 11:15 AM To: xenomai@xenomai.org Subject: reminder: Xenomai community call on Wednesday, Dec 1, 2021, UTC 7:00 AM We have the Xenomai community call today. Topics may include but are not limited to upstream/downstream project plans

reminder: Xenomai community call on Wednesday, Dec 1, 2021, 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, Dec 1, 2021, UTC 7:00 AM Paris, France CEST 8:00

RE: [PATCH v2 2/2] cobalt/trace: dovetail: remove TODO and return -ENOSYS for unportable features

>-Original Message- >From: Jan Kiszka >Sent: Tuesday, November 30, 2021 2:41 PM >To: Chen, Hongzhan ; xenomai@xenomai.org >Subject: Re: [PATCH v2 2/2] cobalt/trace: dovetail: remove TODO and return >-ENOSYS for unportable features > >On 30.11.21 02:07, Chen, Hongzhan wrote: >> >> >>>

RE: [PATCH v2 2/2] cobalt/trace: dovetail: remove TODO and return -ENOSYS for unportable features

>-Original Message- >From: Jan Kiszka >Sent: Monday, November 29, 2021 3:58 PM >To: Chen, Hongzhan ; xenomai@xenomai.org >Subject: Re: [PATCH v2 2/2] cobalt/trace: dovetail: remove TODO and return >-ENOSYS for unportable features > >On 29.11.21 02:03, Hongzhan Chen via Xenomai wrote: >

RE: [PATCH] cobalt/dovetail: Resolve pipeline_clock_name TODO

Hi Jan What about following patch? Try to get clocksource name via sys fs. From aa6fdc59a22f9b1ddca145c72a75f2aa1f776e85 Mon Sep 17 00:00:00 2001 From: Hongzhan Chen Date: Wed, 24 Nov 2021 02:08:27 -0500 Subject: [PATCH] cobalt/clock: dovetail: get current clocksource name via sys fs Dovetail

compile error about TODO after make

Hi Jan Internally , we try to do some basic validation for linux_dovetail branch. One of test is to pass build after make allyesconfig. But it would fail because of enabled CONFIG_XENO_TODO. There is still something NTD in include/cobalt/kernel/dovetail/pipeline/trace.h and include/cobalt/ke

reminder: Xenomai community call on Wednesday, Nov 17, 2021, 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, Nov 17, 2021, UTC 7:00 AM Paris, France CEST 8:0

reminder: Xenomai community call on Wednesday, Nov. 3, 2021, UTC 7:00 AM

Hi all, 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, Nov. 3, 2021, UTC 7:00 AM Paris, Franc

RE: [PATCH v3] utils: add kernel config check utility

> >-Original Message- >From: Jan Kiszka >Sent: Friday, October 22, 2021 12:37 AM >To: Chen, Hongzhan ; xenomai@xenomai.org >Subject: Re: [PATCH v3] utils: add kernel config check utility > >On 20.10.21 10:06, Hongzhan Chen wrote: >> diff --git a/utils/chkkconf/Makefile.am b/utils/chkkcon

RE: [PATCH] utils: add kernel config check utility

>[Next][PATCH] utils: add kernel .config check utility >Jan Kiszka jan.kiszka at siemens.com >Tue Oct 5 16:27:22 CEST 2021 >Previous message (by thread): RTnet failed setup >Next message (by thread): "switchtest" problem with recent 5.10 dovetail and >distro-like kernel config >Messages sorted by:

RE: [PATCH] utils: add kernel config check utility

Hi Jan I resent the first version because I had not received your remark email in my outlook so I thought that it may be flooded somehow. I already find that you remarks https://xenomai.org/pipermail/xenomai/2021-October/046559.html now. Regards Hongzhan Chen -Original Message- From: J

reminder: Xenomai community call on Wednesday, Sept 22, 2021, UTC 7:00 AM

Hi all, 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, Sept 22, 2021, UTC 7:00 AM Paris, Fran

reminder: Xenomai community call on Wednesday, Sept 8, 2021, UTC 7:00 AM

Hi all, 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, Sept 8, 2021, UTC 7:00 AM Paris, Fra

RE: [PATCH] testsuite/gpiobench: Provide choice to switch clock for getting timestamp

> > > > >-Original Message- > >From: Jan

RE: [PATCH 0/3] add support for cherryview gpio controller driver

>-Original Message- >From: Jan Kiszka >Sent: Thursday, September 2, 2021 2:11 PM >To: Chen, Hongzhan ; xenomai@xenomai.org >Subject: Re: [PATCH 0/3] add support for cherryview gpio controller driver > >On 02.09.21 02:42, Chen, Hongzhan wrote: >> >> >>> -Original Message- >>> F

RE: [PATCH 0/3] add support for cherryview gpio controller driver

>-Original Message- >From: Jan Kiszka >Sent: Wednesday, September 1, 2021 10:27 PM >To: Chen, Hongzhan ; xenomai@xenomai.org >Subject: Re: [PATCH 0/3] add support for cherryview gpio controller driver > >On 31.08.21 08:36, Chen, Hongzhan wrote: -Original Message- > From

RE: [PATCH 1/3] drivers/gpio: core: Move out of OF config conditional compilation

>-Original Message- > >From: Jan Kiszka

RE: [PATCH 2/3] drivers/gpio: core: Introduce helper to find gpiochip

-Original Message- >From: Jan Kiszka >Sent: Tuesday, August 31, 2021 2:48 PM >To: Chen, Hongzhan ; xenomai@xenomai.org >Subject: Re: [PATCH 2/3] drivers/gpio: core: Introduce helper to find gpiochip > >On 31.08.21 07:07, Hongzhan Chen via Xenomai wrote: >> To find gpiochip for non-OF p

RE: [PATCH 0/3] add support for cherryview gpio controller driver

>> -Original Message- >>> From: Jan Kiszka >>> Sent: Tuesday, August 31, 2021 1:59 PM >>> To: Chen, Hongzhan ; xenomai@xenomai.org >>> Subject: Re: [PATCH 0/3] add support for cherryview gpio controller driver >>> >>> On 31.08.21 03:35, Chen, Hongzhan wrote: > > > -Origina

RE: [PATCH 0/3] add support for cherryview gpio controller driver

>-Original Message- >From: Jan Kiszka >Sent: Tuesday, August 31, 2021 1:59 PM >To: Chen, Hongzhan ; xenomai@xenomai.org >Subject: Re: [PATCH 0/3] add support for cherryview gpio controller driver > >On 31.08.21 03:35, Chen, Hongzhan wrote: >>> >>> >>> -Original Message- >>> From

RE: [PATCH 0/3] add support for cherryview gpio controller driver

> > >-Original Message- >From: Jan Kiszka >Sent: Monday, August 30, 2021 3:37 PM >To: Chen, Hongzhan ; xenomai@xenomai.org >Subject: Re: [PATCH 0/3] add support for cherryview gpio controller driver > >On 30.08.21 08:45, Hongzhan Chen via Xenomai wrote: >> 1. move out of OF config conditi

reminder: Xenomai community call on Wednesday, Aug 25, 2021, UTC 7:00 AM

Hi all, 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, Aug 25, 2021, UTC 7:00 AM Paris, Franc

reminder: Xenomai community call on Wednesday, Aug 11, 2021, UTC 7:00 AM

Hi all, 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, Aug 11, 2021, UTC 7:00 AM Paris

RE: [PATCH] testsuite/smokey: net: Load rtnet module if missing

-Original Message- >From: Jan Kiszka >Sent: Friday, August 6, 2021 4:12 PM >To: Chen, Hongzhan ; Xenomai >Subject: Re: [PATCH] testsuite/smokey: net: Load rtnet module if missing > >On 06.08.21 09:48, Chen, Hongzhan wrote: >> >> >>> -Original Message- >>> From: Jan Kiszka

RE: [PATCH] testsuite/smokey: net: Load rtnet module if missing

>-Original Message- >From: Jan Kiszka >Sent: Friday, August 6, 2021 3:38 PM >To: Xenomai >Cc: Chen, Hongzhan >Subject: [PATCH] testsuite/smokey: net: Load rtnet module if missing > >From: Jan Kiszka > >This allows to run RTnet tests if the core is built as module but not >yet loaded

RE: [PATCH V2] testsuite/smokey: net: load rtnet module if it has not been loaded

>

  1   2   >