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=-4.3 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,NICE_REPLY_A,SPF_HELO_NONE, SPF_PASS,USER_AGENT_SANE_1 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 7BCC4C433E6 for ; Fri, 19 Mar 2021 10:09:29 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 4B09764E45 for ; Fri, 19 Mar 2021 10:09:29 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229864AbhCSKI5 (ORCPT ); Fri, 19 Mar 2021 06:08:57 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:55566 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229900AbhCSKIs (ORCPT ); Fri, 19 Mar 2021 06:08:48 -0400 Received: from mail-ej1-x62f.google.com (mail-ej1-x62f.google.com [IPv6:2a00:1450:4864:20::62f]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 246AFC06174A for ; Fri, 19 Mar 2021 03:08:48 -0700 (PDT) Received: by mail-ej1-x62f.google.com with SMTP id u9so8746587ejj.7 for ; Fri, 19 Mar 2021 03:08:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding:content-language; bh=FWbhmHtako5sDuRjsgS7KvChBXOqx1yzV8NUPhnS59Q=; b=gMF1Nm+IIM1eEQ2dOk123w2FfHqB9QFQuEJTa1Lns9sUJIzNN7/qodfBj84aeqfnAO omgAnuZP02okhZfgBPiVGb3Ws7WleFH5DViqT2LSe4rSkqnjav846mkzW9VqBOtiWlWL R7FqhOp0gALZSOSsi9C2gfgNqHbq6YXffCKHljzrA67BZxlL0cB7u07+GQ1/SGQbT5Ym Cb0tAQ71w2Ch0cfP1ygFkGAsWv3NEPLjBWde5sz6RffktwClMOrEDOO/qrC6LoR9iW57 680EGBiu4NEINOTfyTF/E5uQWxisAEIREA98+BA+sgTf7WRVLMRVkrhie96d0fEwrOW5 h1TQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=FWbhmHtako5sDuRjsgS7KvChBXOqx1yzV8NUPhnS59Q=; b=K7hxV2WmDJ88pgHKeXE34bKu2x8GCIb6xf+8swP3WV3f3MgObzK0bi1aPbuvPqhDIh 20vV9A211JS9HM03KcifZbT2t/hn13IKG35O0H3hTxJRcYJIe2peUaqzIGi/6ua5I2d6 PdVUxhJJZ44hDLpn8P8KKiDenTeEazwibWHJ2uWaZ48hH7ydLGENWhXIwd5Sq65rZz6C 3FlrQxS3Y1fuDXsHAPICVzFjDJkJhzDfvbPi/cgtE7+R00H9IKv3jm+umMIJWLL3W2sM ZaYXl2WgCnDGZaQDM7iyucRKVNycCAuEeeL1mw0z3PIWSkbuyrp3itDZSeUM+ffc+q/O b7Zg== X-Gm-Message-State: AOAM5315F1ymFB+DC1ZWst214MeFmMZomG50PIQQZN/ep6AwZklK8pjR 4W0+22rEYx9mFO8Jilhujrc= X-Google-Smtp-Source: ABdhPJwdXrfDKoZtd3bjedEWF/V3574NazWXQPbX+tuOZW0kHKpHUYyclHQmMCruh1fnYpamrFnE7g== X-Received: by 2002:a17:906:cb0a:: with SMTP id lk10mr3335613ejb.479.1616148526889; Fri, 19 Mar 2021 03:08:46 -0700 (PDT) Received: from [192.168.1.9] ([151.32.218.153]) by smtp.gmail.com with ESMTPSA id g26sm3375285ejz.70.2021.03.19.03.08.45 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 19 Mar 2021 03:08:46 -0700 (PDT) Subject: Re: [PATCH v32 0/5]Timestamp synchronization of host - guest tracing session To: "Tzvetomir Stoyanov (VMware)" , rostedt@goodmis.org Cc: linux-trace-devel@vger.kernel.org, Dario Faggioli References: <20210315061857.168570-1-tz.stoyanov@gmail.com> From: Stefano De Venuto Message-ID: <6796a75b-6a59-767f-08ec-ee0cbfd8c825@gmail.com> Date: Fri, 19 Mar 2021 11:08:45 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.8.1 MIME-Version: 1.0 In-Reply-To: <20210315061857.168570-1-tz.stoyanov@gmail.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Content-Language: en-US Precedence: bulk List-ID: X-Mailing-List: linux-trace-devel@vger.kernel.org Hello, On 3/15/21 7:18 AM, Tzvetomir Stoyanov (VMware) wrote: > Basic infrastructure for host - guest timestamp synchronization and a > PoC implementation of PTP-like and KVM algorithms. I'm trying to make some analysis on traces generated by host and guest, so I applied this series and the related dependencies. However, when the KVM algorithm is used, the merging process of the two traces doesn't seem to happen properly. The output of `trace-cmd report -i trace.dat -i trace-tumbleweed.dat` is:            trace.dat: cpus=4 trace-tumbleweed.dat: cpus=1            trace.dat:            sleep-23948 [002]61124758463654: write_msr:            c0000100, value 7f35092875c0            trace.dat:           -0     [000]61124760841508: write_msr:            c0000100, value 7f6136b75640            trace.dat:        CPU 0/KVM-1640  [000]61124760851620: write_msr:            c0011020, value 40000000000000            trace.dat:        CPU 0/KVM-1640  [000]61124760861778: read_msr:             c0000101, value ffff9b1b76c00000            trace.dat:        CPU 0/KVM-1640  [000]61124760862832: read_msr:             c0000081, value 23001000000000            trace.dat:        CPU 0/KVM-1640  [000]61124760864347: read_msr:             c0000082, value ffffffffb5400010            trace.dat:        CPU 0/KVM-1640  [000]61124760865225: read_msr:             c0000083, value ffffffffb5401670            .            .            . trace-tumbleweed.dat:   IPC I/O Parent-4313 [000]8446232460209009653: write_msr:            c0000100, value 7f94535c7640 trace-tumbleweed.dat:    IPC I/O Child-4503 [000]8446348845232796661: write_msr:            c001011f, value 4 trace-tumbleweed.dat:    IPC I/O Child-4503 [000]8447532508154803189: write_msr:            c0000100, value 7f945e8d5780 trace-tumbleweed.dat:           -0    [000]8452336523564659701: write_msr:            c001011f, value 0 trace-tumbleweed.dat:           -0    [000]8452515224268944373: write_msr:            6e0, value 731478a3bf62 trace-tumbleweed.dat:           -0    [000]8452610851715789813: write_msr:            6e0, value 731478968f37 trace-tumbleweed.dat:           -0    [000]8555757214338495477: write_msr:            6e0, value 731478853ec1 trace-tumbleweed.dat:           -0    [000]8555904475882173429: write_msr:            6e0, value 7314778a60e8 trace-tumbleweed.dat:      kworker/0:1-7351 [000]8556355589182174197: write_msr:            c0000100, value 7f8373573740 The TimeShift information is inside the guest trace file, so I think this is not a transfer problem. I also tried to remove the last patch, the one related to the KVM clock, in order to use PTP and the two traces are merged correctly. The commands used to record are: Host: # trace-cmd record -C x86-tsc -e kvm:* -e msr:* -A tumbleweed:823 -e msr:* -C x86-tsc sleep 1 Guest: # echo x86-tsc > /sys/kernel/tracing/trace_clock # trace-cmd agent Am I doing something wrong? If necessary, I can provide more info about my setup, or do more tests. Thanks and Regards, Stefano