From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-5.3 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, USER_AGENT_SANE_2 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 70509C433DB for ; Wed, 24 Mar 2021 01:53:24 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 3C231619EB for ; Wed, 24 Mar 2021 01:53:24 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234526AbhCXBws (ORCPT ); Tue, 23 Mar 2021 21:52:48 -0400 Received: from mail.kernel.org ([198.145.29.99]:34666 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231835AbhCXBwf (ORCPT ); Tue, 23 Mar 2021 21:52:35 -0400 Received: from oasis.local.home (cpe-66-24-58-225.stny.res.rr.com [66.24.58.225]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 797D4619EA; Wed, 24 Mar 2021 01:52:34 +0000 (UTC) Date: Tue, 23 Mar 2021 21:52:32 -0400 From: Steven Rostedt To: "Tzvetomir Stoyanov (VMware)" Cc: linux-trace-devel@vger.kernel.org Subject: Re: [PATCH v2 18/18] trace-cmd: Get current clock for host-guest tracing session Message-ID: <20210323215232.32a80daa@oasis.local.home> In-Reply-To: <20210322095945.259300-19-tz.stoyanov@gmail.com> References: <20210322095945.259300-1-tz.stoyanov@gmail.com> <20210322095945.259300-19-tz.stoyanov@gmail.com> X-Mailer: Claws Mail 3.17.3 (GTK+ 2.24.33; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-trace-devel@vger.kernel.org On Mon, 22 Mar 2021 11:59:45 +0200 "Tzvetomir Stoyanov (VMware)" wrote: > In host-guest tracing session, all peers should use the same tracing > clock. If there is no user configured trace clock, the current logic > assumes "local" clock for the session. This could be wrong, as other > clock than "local" could be already configured on the host, before > running trace-cmd. The default clock for host-guest tracing session > should be rertieved from the host's "trace_clock" file. I need more time to review the last two patches, but feel free to send a new version of this patch series before I do so. Thanks! -- Steve