From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752561AbcF2AxH (ORCPT ); Tue, 28 Jun 2016 20:53:07 -0400 Received: from LGEAMRELO12.lge.com ([156.147.23.52]:39476 "EHLO lgeamrelo12.lge.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752423AbcF2AxF (ORCPT ); Tue, 28 Jun 2016 20:53:05 -0400 X-Original-SENDERIP: 156.147.1.125 X-Original-MAILFROM: namhyung@kernel.org X-Original-SENDERIP: 165.244.98.76 X-Original-MAILFROM: namhyung@kernel.org X-Original-SENDERIP: 10.177.227.17 X-Original-MAILFROM: namhyung@kernel.org Date: Wed, 29 Jun 2016 09:52:31 +0900 From: Namhyung Kim To: Steven Rostedt CC: , "linux-kernel@vger.kernel.org" , Minchan Kim Subject: Re: [QUESTION] Is there a better way to get ftrace dump on guest? Message-ID: <20160629005231.GA14525@sejong> References: <20160628062514.GA4674@danjae.aot.lge.com> <20160628095727.436925cb@gandalf.local.home> MIME-Version: 1.0 In-Reply-To: <20160628095727.436925cb@gandalf.local.home> User-Agent: Mutt/1.6.1 (2016-04-27) X-MIMETrack: Itemize by SMTP Server on LGEKRMHUB06/LGE/LG Group(Release 8.5.3FP6|November 21, 2013) at 2016/06/29 09:52:38, Serialize by Router on LGEKRMHUB06/LGE/LG Group(Release 8.5.3FP6|November 21, 2013) at 2016/06/29 09:52:38, Serialize complete at 2016/06/29 09:52:38 Content-Type: text/plain; charset="utf-8" Content-Disposition: inline Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Steve, On Tue, Jun 28, 2016 at 09:57:27AM -0400, Steven Rostedt wrote: > On Tue, 28 Jun 2016 15:33:18 +0900 > Namhyung Kim wrote: > > > Send again to correct addresses, sorry! > > > > On Tue, Jun 28, 2016 at 3:25 PM, Namhyung Kim wrote: > > > Hello, > > > > > > I'm running some guest machines for kernel development. For debugging > > > purpose, I use lots of trace_printk() since it's faster than normal > > > printk(). When kernel crash happens the trace buffer is printed on > > > console (I set ftrace_dump_on_oops) but it takes too much time. I > > > don't want to reduce the size of ring buffer as I want to collect the > > > debug info as much as possible. And I also want to see trace from all > > > cpu so 'ftrace_dump_on_oop = 2' is not an option. > > > > > > I know the kexec/kdump (and the crash tool) can dump and analyze the > > > trace buffer later. But it's cumbersome to do it everytime and more > > > importantly, I don't want to spend the memory for the crashkernel. > > > > > > So what is the best way to handle this? I'd like to know how others > > > setup the debugging environment.. > > Heh, I'd say something helpful but you basically already shot down all > of my advice, because what I do is... > > 1) Reduce the size of the ring buffer > > 2) Dump out just one CPU > > 3) use kexec/kdump and make a crash kernel to extract trace.dat from > > > That's my debugging environment, but it looks like you want something > else. Thanks for sharing. Yeah, I'd like to know other ways to overcome this if possible. Since I don't have enough knowledge about this area, I hope others would have better idea. :) Thanks, Namhyung