On 20.04.21 03:02, Chen, Hongzhan wrote: > > >> -----Original Message----- >> From: Jan Kiszka <jan.kis...@siemens.com> >> Sent: Friday, April 16, 2021 8:05 PM >> To: Chen, Hongzhan <hongzhan.c...@intel.com>; xenomai@xenomai.org >> Subject: Re: [PATCH V2 3/3] testsuite/latmus: introduce latmus benchmark >> >> On 16.04.21 07:31, hongzha1 via Xenomai wrote: >>> Measure response time to GPIO events sent by a remote Zephyr-based >>> latency monitor (latmon). This monitor collects then sends the latency >>> data over a network connection to the latmus front-end which displays >>> the results received: >>> >>> [Linux device under test running latmus] <--+ >>> | >>> ^ | (GPIO ack) | >>> | | | TCP/IP network connection >>> | | | (control & data samples) >>> | (GPIO pulse) v | >>> | >>> [Zephyr-based device running latmon] <--+ >>> >>> The generic latency monitor code running the measurement loop is >>> available from the zephyr/ directory. This support comes with a Zephyr >>> device tree patch for enabling this monitor on NXP's FRDM-K64F >>> development board. >> >> Where is all this? > > Actually , this zephyr directory is located in libevl project at > https://git.evlproject.org/libevl.git/tree/benchmarks/zephyr. > at this time. Do you think it is suitable to make a copy for this folder in > xenomai code base? Or I just described in comments > that it is from https://git.evlproject.org/libevl.git/tree/benchmarks/zephyr . >
It's fine to link that. But, again, this needs to go into proper in-tree documentation. Jan -- Siemens AG, T RDA IOT Corporate Competence Center Embedded Linux
