Received: by 2002:ac0:a582:0:0:0:0:0 with SMTP id m2-v6csp236560imm; Fri, 19 Oct 2018 22:27:03 -0700 (PDT) X-Google-Smtp-Source: ACcGV63wuPd8ejkXjIyJ++qkGgMVwinjeRjm3qpR6sCuHhN/YQFrDgAsqJrd59fr3ev3tDBEMsGA X-Received: by 2002:a17:902:5981:: with SMTP id p1-v6mr4903020pli.260.1540013223222; Fri, 19 Oct 2018 22:27:03 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1540013223; cv=none; d=google.com; s=arc-20160816; b=yA0fwkmO52mNLsnFT7eNQGrMwIXc/FUrIBRh6klD0QOjCv3+hm+sswRlqbJRAqrPkV 06E9Yiyla+b7DkzUVDsuggxvW2JSs9gS8D8iRCdFOYZjqHzBqzkZdAoAFn12sNb5rVhS YHmjdbCsEdC9uxg5kYsSavj8m4n6JtgL6sW3f8O5TwnJ4zlrSPyQem629VOxywrb/UQW Is1rAAjhJh4A+SMd0JOk/GwdxZdE6HPJFvRf72JGgRPXEpBCRz7vx6f0QZSkS4af8bwp fLY2bp0aUjROYwPjUBWfk3xLyWT4Qb67c3D9I0Cinz/Sl3C6NdAOAwxdEZhzHYbCT1vw 1TMw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:dkim-signature; bh=95hQ0cElUXwFweOIF1T469SY81PeUDO4Y40jbpl1PbE=; b=u6zXw6Wst5AD9YfQARNMNT5qyFJxCz/09fvhku3RxSiD8rBpLDqxVnmK6bq3MzD6Uc VaBBXGZxo5ZeH8c51zycEueQP6qDdBxwcdetr8/nadbHqoRU3WLhF2LZ5QStnVG3ibiX 3a+1+E4pC+77fyrI+5A8ktAFx92tlrJPMrgqyBIUNbgwRrZ8n7MDghSXeTJQ9r0MInvp QVV6pW5bF+msA9xqRw98jUNL27exjvSuddVTOR7Y8HikGgb2FVxTGU4B4TcrN7T2Ny2H PCvrIBTaX0PmSWqBLQrENmG4W77jz0mnqxdyyH/qS05T49OXZiye1AA66+m3/SsK30B6 sGTQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@joelfernandes.org header.s=google header.b=Cn+tkxJ5; 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 p25-v6si7736372pli.239.2018.10.19.22.26.47; Fri, 19 Oct 2018 22:27:03 -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=@joelfernandes.org header.s=google header.b=Cn+tkxJ5; 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 S1727076AbeJTNet (ORCPT + 99 others); Sat, 20 Oct 2018 09:34:49 -0400 Received: from mail-pg1-f194.google.com ([209.85.215.194]:39190 "EHLO mail-pg1-f194.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726312AbeJTNet (ORCPT ); Sat, 20 Oct 2018 09:34:49 -0400 Received: by mail-pg1-f194.google.com with SMTP id r9-v6so16642513pgv.6 for ; Fri, 19 Oct 2018 22:25:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelfernandes.org; s=google; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=95hQ0cElUXwFweOIF1T469SY81PeUDO4Y40jbpl1PbE=; b=Cn+tkxJ5NdAQN/++5+8TCtU4mQWxu6USG5aIUFg3wUidOinctPa872ZuT8UYcwwZWw vrq4KqnGbdMg/+91j7vU88EZm3uU2q39WZgFBbPcZ9lVmSPSDuPCwGS2tIQRAOPhje5r SNWPe+Hgt5b+/vAJX8IN7wTiCmQnQ6hPSQj8k= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=95hQ0cElUXwFweOIF1T469SY81PeUDO4Y40jbpl1PbE=; b=st8J6lnEVBLh6uF+VZ67yjzwOffMfBzj3v330lZezaAyKdOcWX3rc9TDyEwafoCWBD fxEsLI7SRMldTRE5U79+7TZe8bk5tjGny7JCUbo5dfrxmAFYEEdGFS4Gvn9MnaA2kdNo aqAvtxCvsnj3ow49CDuleiyUsjkGMgiiDLOsQkVd1L1TqumO7S5lJCNLpj8uNFrG8k8z d7jz56Lq6pFEShI443L8o0ytOjOK1xlk3fiWogBCV9IVfY9UUAAB04lRJspB4NY2iNY+ G6hMmcwSBlILW240aIUxMbI5/6d7xay2uPtASkQF6pyKHaUB/Oh3c5mM08CnxItaQfnR o79A== X-Gm-Message-State: ABuFfoiI7I8VY8OccaCI19aZA33RoQQz/VdC64H/c0nAiPMZX6/A0NGB CbJ4Eq8ukeOF7XhPhLzkC0FgtA== X-Received: by 2002:a62:cd8a:: with SMTP id o132-v6mr4677308pfg.12.1540013137550; Fri, 19 Oct 2018 22:25:37 -0700 (PDT) Received: from localhost ([2620:0:1000:1601:3aef:314f:b9ea:889f]) by smtp.gmail.com with ESMTPSA id x15-v6sm38945452pfd.27.2018.10.19.22.25.35 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Fri, 19 Oct 2018 22:25:36 -0700 (PDT) Date: Fri, 19 Oct 2018 22:25:35 -0700 From: Joel Fernandes To: Sai Prakash Ranjan Cc: Steven Rostedt , Ingo Molnar , Laura Abbott , Kees Cook , Anton Vorontsov , Rob Herring , devicetree@vger.kernel.org, Colin Cross , Jason Baron , Tony Luck , Arnd Bergmann , Catalin Marinas , Will Deacon , Masami Hiramatsu , Joe Perches , Jim Cromie , Rajendra Nayak , Vivek Gautam , Sibi Sankar , linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org, Greg Kroah-Hartman , Ingo Molnar , Tom Zanussi , Prasad Sodagudi , tsoni@codeaurora.org, Bryan Huntsman , Tingwei Zhang , tkjos@google.com Subject: Re: [PATCH 0/6] Tracing register accesses with pstore and dynamic debug Message-ID: <20181020052535.GA155509@joelaf.mtv.corp.google.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sun, Sep 09, 2018 at 01:57:01AM +0530, Sai Prakash Ranjan wrote: > Hi, > > This patch series adds Event tracing support to pstore and is continuation > to the RFC patch introduced to add a new tracing facility for register > accesses called Register Trace Buffer(RTB). Since we decided to not introduce > a separate framework to trace register accesses and use existing framework > like tracepoints, I have moved from RFC. Details of the RFC in link below: > > Link: https://lore.kernel.org/lkml/cover.1535119710.git.saiprakash.ranjan@codeaurora.org/ > > MSR tracing example given by Steven was helpful in using tracepoints for > register accesses instead of using separate trace. But just having these > IO traces would not help much unless we could have them in some persistent > ram buffer for debugging unclocked access or some kind of bus hang or an > unexpected reset caused by some buggy driver which happens a lot during > initial development stages. By analyzing the last few entries of this buffer, > we could identify the register access which is causing the issue. Hi Sai, I wanted to see if I could make some time to get your patches working. We are hitting usecases that need something like this as well. Basically devices hanging and then the ramdump does not tell us much, so in this case pstore events can be really helpful. This usecase came up last year as well. Anyway while I was going through your patches, I cleaned up some pstore code as well and I have 3 more patches on top of yours for this clean up. I prefer we submit the patches together and sync our work together so that there is least conflict. Here's my latest tree: https://github.com/joelagnel/linux-kernel/commits/pstore-events (note that I have only build tested the patches since I just wrote them and its quite late in the night here ;-)) thanks, - Joel