From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca by simark.ca with LMTP id JPmfOnm5rGC5dAAAWB0awg (envelope-from ) for ; Tue, 25 May 2021 04:46:49 -0400 Received: by simark.ca (Postfix, from userid 112) id E2EBF1F11C; Tue, 25 May 2021 04:46:49 -0400 (EDT) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on simark.ca X-Spam-Level: X-Spam-Status: No, score=-0.8 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,FREEMAIL_REPLYTO_END_DIGIT,MAILING_LIST_MULTI, URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.2 Received: from lists.lttng.org (lists.lttng.org [167.114.26.123]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by simark.ca (Postfix) with ESMTPS id 0ED541E54D for ; Tue, 25 May 2021 04:46:49 -0400 (EDT) Received: from lists-lttng01.efficios.com (localhost [IPv6:::1]) by lists.lttng.org (Postfix) with ESMTP id 4Fq73r2WfJz1wJ0; Tue, 25 May 2021 04:46:48 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=lists.lttng.org; s=default; t=1621932408; bh=gxGGuGvnwbtv7RmiXaZvmVqlDRxZwLpfkco5C9EUfi0=; h=References:In-Reply-To:Date:To:Subject:List-Id:List-Unsubscribe: List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:Cc: From; b=P/zkQwXBpGJcjm6m/k23y2ZYstYJts70Qmrhee3cMdpzIdIlcuWbxXfvmFVNBBj9F /t4qWB+s/M+5sAiI+59hG3PisfVL4gS30ACQ+s6cbvCDrBSdrCf0Gs26CF1EK57iaS sXoXfhNnP2pGjo30GAM+sEOgVkO+rclfL3iOFg87fdIqZEM5SqUG4q53NjYD89KBB3 hdsjvpFhpJmtHb1tXvcJolwMeDcdPK7NkhZFGNL7G5F9pgfSfbEnqGfkplaoqjkw6I WSkGnlH1INYRdU4HnP+vRUms9k9feFW8tRWbB+Qz23qMWmX7odYAOyl6JsgEAKMjIY ZxElhEHp5Foag== Received: from mail-ot1-x333.google.com (mail-ot1-x333.google.com [IPv6:2607:f8b0:4864:20::333]) by lists.lttng.org (Postfix) with ESMTPS id 4Fq73p6cZpz1wHy for ; Tue, 25 May 2021 04:46:46 -0400 (EDT) Received: by mail-ot1-x333.google.com with SMTP id i23-20020a9d68d70000b02902dc19ed4c15so27962589oto.0 for ; Tue, 25 May 2021 01:46:46 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=Y2jOcofkOyVSili3ONXaLeX9USNp2YBBtn07TYWh+vg=; b=oicC0fOunSm8lz4rtPol9mXdPJyoRfPtx9cnlMiq2QM6eyOl4P8fPDvMiw1GUUWtAv /sUwkOHqGKFvYTTMvFiiPm3r4ubtO3gVlf7QQNCDV06t5EVVL7U1OZMdWzT2DqmJq4Lq utmi9+cNlx9WF5lrvC1Rwv+q5AmlrqfDznSLnu5Iie4/d1NGb7m/ZgrkMNvKFnH1HiIK 7U7wsJ2tcz4WZYQykfSSVyE/KyVvJw1RyNwFr0qlbjcIv5oIbvMaT+VJsVFSvec/IHUa 0Rr21LK5KQMQz82yC1fiXs3GFFT0PPL/Iies3ngWAy96VKtjsjHcM9VYMOZ4V+f/QKaW wl1g== X-Gm-Message-State: AOAM533He+yDIz5Xw6D3g8Mi9nJG4As1NEs5JuBTdSuDlyQlO8UQhg8S VjnmH6PiMkkIa/ukPhzuygERCHASO5/TiY2KK7o= X-Google-Smtp-Source: ABdhPJyebvkniAvjJH1pZb9Vb92qkfosIGoD34MCj8r2wM4F38wGZg6/iWYL1UHSMkM6282P4BuTK+CCPUH8f230EO0= X-Received: by 2002:a9d:5c14:: with SMTP id o20mr7834109otk.328.1621932406149; Tue, 25 May 2021 01:46:46 -0700 (PDT) MIME-Version: 1.0 References: <851697925.52293.1621518874455.JavaMail.zimbra@efficios.com> <201689209.52304.1621519010729.JavaMail.zimbra@efficios.com> <186729016.52398.1621523346736.JavaMail.zimbra@efficios.com> In-Reply-To: Date: Tue, 25 May 2021 10:46:35 +0200 Message-ID: To: MONTET Julien Subject: Re: [lttng-dev] LTTng - Xenomai : different results between timestamp-lttng and rt_time_read() X-BeenThere: lttng-dev@lists.lttng.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: LTTng development list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Norbert Lange via lttng-dev Reply-To: Norbert Lange Cc: Jan Kiszka , lttng-dev , Xenomai Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: lttng-dev-bounces@lists.lttng.org Sender: "lttng-dev" Am Fr., 21. Mai 2021 um 12:13 Uhr schrieb MONTET Julien : > > Hello Mathieu, Norbert and Jan, > > Thank you for all of your explainations and the overview of the system. > No I didn't change the ipipe patch for the vDSO, I may try this. > If I have correctly understood, this patch prevents Cobalt from entering in a deadlock when the kernel is using the vDSO and the program interrupts the kernel at the same time. On which kernel does it word (aroubd 4.19) ? > I currently try to avoid kernel 5.4 because I remember I faced some boot issues (but it is on another topic). That patch was for 4.19 AFAIR, but its specific to x86. The Linux kernel cleaned up the vdso handling to have a common base with some 5.x version, but back then its been separate for each arch > > Here the issues i faced (drawn on TraceCompass). Are these the deadlocks we are talking about ? > https://postimg.cc/BP4G3bF0 (on 11:02:56:380) > https://postimg.cc/q6wHvrcC Nope, if you get such a deadlock, then your only hope is Xenomai's Watchdog killing the process. It should happen very rarely (but thats not an argument if your software should run for years). Norbert _______________________________________________ lttng-dev mailing list lttng-dev@lists.lttng.org https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev