Hello, Following are the system informations: - OS: Centos 7 64 bit with Gnome 3.14.2 Version - Processor: Intel® Xeon(R) CPU E5-2630 v3 @ 2.40GHz × 32 - Graphics: Gallium 0.4 on llvmpipe (LLVM 3.8, 256 bits) I patched 3.18.20 kernel with Xenomai 3.0.6... For more details I attach the kernel configuration file...
I built Xenomai with the following configure option: configure --enable-smp --enable-dlopen-libs --enable-pshared I disabled the following system services: upower.service - Daemon for power management tuned.service - Dynamic System Tuning Daemon smartd.service - Self Monitoring and Reporting Technology (SMART) Daemon firewalld.service - firewalld - dynamic firewall daemon As Simone Zucchi wrote before... I disabled the gnome power management dconf-editor => gnome.settings-daemon.plugins.power => active false in grub2 I configured the following kernel parameters: apm=off xenomai.msi=disabled xenomai.sysheap_size=2048 Latency grows when I launch applications like kdevelop or similar, or when the I return from the lock screen... I simply launch the [XENOMAI FOLDER]/bin/latency application... can I trace this built in application? Thanks in advance Maurizio Fazio Chief Technical Office / Aircraft Systems Software Engineer Leonardo S.p.A. C.so Francia, 426 - Torino - 10146 - Italy Tel. +39 011 756 3308 / 3761 maurizio.fa...@leonardocompany.com www.leonardocompany.com ————————————————————————————————–—————— HELICOPTERS/AERONAUTICS/ELECTRONICS, DEFENCE & SECURITY SYSTEMS/SPACE ————————————————————————————————–—————— Company General Use Il presente messaggio e-mail e ogni suo allegato devono intendersi indirizzati esclusivamente al destinatario indicato e considerarsi dal contenuto strettamente riservato e confidenziale. Se non siete l'effettivo destinatario o avete ricevuto il messaggio e-mail per errore, siete pregati di avvertire immediatamente il mittente e di cancellare il suddetto messaggio e ogni suo allegato dal vostro sistema informatico. Qualsiasi utilizzo, diffusione, copia o archiviazione del presente messaggio da parte di chi non ne è il destinatario è strettamente proibito e può dar luogo a responsabilità di carattere civile e penale punibili ai sensi di legge. Questa e-mail ha valore legale solo se firmata digitalmente ai sensi della normativa vigente. The contents of this email message and any attachments are intended solely for the addressee(s) and contain confidential and/or privileged information. If you are not the intended recipient of this message, or if this message has been addressed to you in error, please immediately notify the sender and then delete this message and any attachments from your system. If you are not the intended recipient, you are hereby notified that any use, dissemination, copying, or storage of this message or its attachments is strictly prohibited. Unauthorized disclosure and/or use of information contained in this email message may result in civil and criminal liability. “ This e-mail has legal value according to the applicable laws only if it is digitally signed by the sender -----Messaggio originale----- Da: Jan Kiszka [mailto:jan.kis...@siemens.com] Inviato: venerdì 12 gennaio 2018 14:37 A: Fazio Maurizio; Simone M. Zucchi; xenomai@xenomai.org Oggetto: Re: R: Xenomai 3.0.6 high latency On 2018-01-12 10:51, Fazio Maurizio wrote: > Hello, > I applied your solution. I launched again the latency test but again worst > case was 164us... > I monitored the test for a while and I noticed these behaviors: > - When I launched the console application the worst latency grew over 100 > us... > - After a while the monitor has gone to black screen and then I moved > the mouse... even in this case the worst latency grew over 100us > > Have you any idea? > You didn't specify enough details of your hardware platform and configuration yet. Maybe the latencies are related to hw effects, thus not much that software can contribute to. Typical sources: - system management mode (BIOS) -> disable SMI, if possible, via the related Xenomai logic - contentions on graphic operations, specifically with built-in GPUs -> head-less operation, possibly also a different graphic mode (framebuffer instead of DRM) - aggressive power management -> disable in the kernel, watch out for suspicious BIOS settings Software-related latencies can be identified by using tracing, ftrace with event tracing (trace-cmd, kernelshark) or the ipipe function tracer. Specifically, use the latency benchmark to stop the latter when a new maximum arrives. If you share the trace, the community may help with analyzing. Jan -- Siemens AG, Corporate Technology, CT RDA IOT SES-DE Corporate Competence Center Embedded Linux -------------- next part -------------- A non-text attachment was scrubbed... Name: config-3.18.20 Type: application/octet-stream Size: 138948 bytes Desc: config-3.18.20 URL: <http://xenomai.org/pipermail/xenomai/attachments/20180112/7773eff7/attachment.obj> _______________________________________________ Xenomai mailing list Xenomai@xenomai.org https://xenomai.org/mailman/listinfo/xenomai
