Received: by 2002:a25:824b:0:0:0:0:0 with SMTP id d11csp6960305ybn; Mon, 30 Sep 2019 06:35:04 -0700 (PDT) X-Google-Smtp-Source: APXvYqwqDZ38DHcJXwbSM0D4bRDm17USnVHFwD5m54QnP4wnd4dOtKhSPuyNoFs6DouHrGUXpHdB X-Received: by 2002:a50:f009:: with SMTP id r9mr20157862edl.195.1569850504054; Mon, 30 Sep 2019 06:35:04 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1569850504; cv=none; d=google.com; s=arc-20160816; b=UMf00GBM9cUgh4oooXEnYVI506UzcIuIK30yp5cFKXTwVHhoO5TIGaK5Gska+TbMCx EfU0RukHF/fKvhBXHsPgUPfkaOOYzEumPlDIE7GSjD6zk6Fy27ESUIkijAjt87qlBFNk pHRZEieXDV4WmaMTZ+P/qXo8yddAvDRVSIoNMWhu1iLPjpnHhpqraLkxg1w6ANgWL2Oq erVusVt9JDP9AY4mL0PvYYEF8UQXH3qm5BKdu9g+W6tDIslG+PGKUXMEjn8y24plt7JU GvPDUalm8DCn6gBSqrCQ83w9j+7YuJXP7VwPMuiA+068hGHcSrmqkoE+HDTZTeYvRK+z bkew== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:message-id:subject:cc:to:from :date:content-transfer-encoding:mime-version:dkim-signature :dkim-signature; bh=QfOghrbHC+uhBYJkZcpxQNmqOvJgCDeekFWXWjITdQk=; b=EJFf6b1Q7GKWTFUcOgY2RO0+Lvk6TcV5XAB6kI8/IXeE0rG/D7MLR7tLQge99y2dM7 yPsBQ6pKSMU5JWHPnhUIhgP0ruZjVT1OvRKWlnHiFszth3ock/DUZc1pawBq8HdOXjmB iu7llI7CUuqyFVNH9fqtuiSjeaMziNzWjm+b17ADcEdXNzcsw4c5pK+f2JSlnyFhdFDE 4HZxCo0otCz12EsTmanREc4t4RsKlEHsgLcACN9XoEHHAptXPEoP6vxHbEjFKOB4Advf HJpjWOUJswMdBGaob5krJilPIfx8pka46mW8BNV3lLGBcSJxwVP7WUpEXwKkALu1lfdR aVUA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@codeaurora.org header.s=default header.b=aMCNGRz4; dkim=pass header.i=@codeaurora.org header.s=default header.b=B9x321Jk; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id e22si7504638ejm.72.2019.09.30.06.34.39; Mon, 30 Sep 2019 06:35:04 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@codeaurora.org header.s=default header.b=aMCNGRz4; dkim=pass header.i=@codeaurora.org header.s=default header.b=B9x321Jk; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1731268AbfI3Ndp (ORCPT + 99 others); Mon, 30 Sep 2019 09:33:45 -0400 Received: from smtp.codeaurora.org ([198.145.29.96]:52804 "EHLO smtp.codeaurora.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729738AbfI3Ndp (ORCPT ); Mon, 30 Sep 2019 09:33:45 -0400 Received: by smtp.codeaurora.org (Postfix, from userid 1000) id 777CF6118C; Mon, 30 Sep 2019 13:33:43 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=codeaurora.org; s=default; t=1569850424; bh=Aane7lX/b8MbjQ7N/QXU+4I4h3uabatlKt7JDCZCBCc=; h=Date:From:To:Cc:Subject:From; b=aMCNGRz4KLejyWB8zNxhuPfOc1y9kFOnaD6aHKsJev6sWuFrCu/Kwo5RGPNIkj7Py 4bDbrUHl3QobQeeNK840WeIgZd4JjN6tmu827/ujJxH17umsh68XzjU2mbjkwHLX1j qNKSI6be8yOjiMyzwjUgBeSzriOeMAyyPbq+M5Dc= X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on pdx-caf-mail.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.7 required=2.0 tests=ALL_TRUSTED,BAYES_00, DKIM_INVALID,DKIM_SIGNED autolearn=no autolearn_force=no version=3.4.0 Received: from mail.codeaurora.org (localhost.localdomain [127.0.0.1]) by smtp.codeaurora.org (Postfix) with ESMTP id 53E35602CC; Mon, 30 Sep 2019 13:33:42 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=codeaurora.org; s=default; t=1569850422; bh=Aane7lX/b8MbjQ7N/QXU+4I4h3uabatlKt7JDCZCBCc=; h=Date:From:To:Cc:Subject:From; b=B9x321Jkh0mHK3l5DYh1NPooOL0E0ipngQgnbuOHPc1PDSOLBbAlRKIZEtsxRV/xJ lNM5pXRB3sl9PRHaH6pAReMCqufknidHJWnDMRxtTg7UDiGhs6/rE4ZlTjoTWpTTGY KhCViZIXESKd7a0Puh/YQ6hTq3sH8U3RxAgRU4xY= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Date: Mon, 30 Sep 2019 06:33:42 -0700 From: Sodagudi Prasad To: pmladek@suse.com, sergey.senozhatsky@gmail.com, rostedt@goodmis.org Cc: linux-kernel@vger.kernel.org Subject: Time stamp value in printk records Message-ID: <7d1aee8505b91c460fee347ed4204b9a@codeaurora.org> X-Sender: psodagud@codeaurora.org User-Agent: Roundcube Webmail/1.2.5 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi All, From Qualcomm side, we would like to check with upstream team about adding Raw time stamp value to printk records. On Qualcomm soc, there are various DSPs subsystems are there - for example audio, video and modem DSPs. Adding raw timer value(along with sched_clock()) in the printk record helps in the following use cases – 1) To find out which subsystem crashed first - Whether application processor crashed first or DSP subsystem? 2) If there are any system stability issues on the DSP side, what is the activity on the APPS processor side during that time? Initially during the device boot up, printk shed_clock value can be matched with timer raw value used on the dsp subsystem, but after APPS processor suspends several times, we don’t have way to correlate the time stamp value on the DSP and APPS processor. All timers(both apps processor timer and dsp timers) are derived from globally always on timer on Qualcomm soc, So keeping global timer raw values in printk records and dsp logs help to correlate the activity of all the processors in SoC. It would be great if upstream team adds common solution this problem if all soc vendors would get benefit by adding raw timer value to printk records. -Thanks, Prasad -- The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum, Linux Foundation Collaborative Project