From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: trace_printk() support in trace-cmd Date: Mon, 13 Dec 2010 17:43:41 +0200 Message-ID: <4D063F2D.4020806@redhat.com> References: <4CE16941.3080008@redhat.com> <1289841107.12418.602.camel@gandalf.stny.rr.com> <4CE16E64.2040909@redhat.com> <1289846036.12418.604.camel@gandalf.stny.rr.com> <4CE24CA9.9030508@redhat.com> <1289913102.12418.622.camel@gandalf.stny.rr.com> <1289920353.30543.4.camel@gandalf.stny.rr.com> <4CEB9CD1.8050002@redhat.com> <4D04F3FB.7060708@redhat.com> <1292254011.5015.1545.camel@gandalf.stny.rr.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit Cc: linux-trace-users@vger.kernel.org, KVM list To: Steven Rostedt Return-path: In-Reply-To: <1292254011.5015.1545.camel@gandalf.stny.rr.com> Sender: linux-trace-users-owner@vger.kernel.org List-Id: kvm.vger.kernel.org On 12/13/2010 05:26 PM, Steven Rostedt wrote: > On Sun, 2010-12-12 at 18:10 +0200, Avi Kivity wrote: > > On 11/23/2010 12:52 PM, Avi Kivity wrote: > > > > I see a trace_printk() commit in trace-cmd.git. Is that related? If > > > not, I'll work on getting a small sample of the problem. > > > > > > > Sample: http://people.redhat.com/akivity/trace.dat.bz2 > > > > You said previously that /debug/tracing/printk_formats was empty? Still the case. > This > is the problem. It uses this file to map what the format of the printk > is to what is being printed. But if we don't have this mapping, > trace-cmd (nor perf) can not figure this out. > > You are using the latest kernel for this? 2.6.37-rc5 plus a bunch of kvm patches. > What's your work flow? Do you > load kvm modules after you start the trace, or are they always loaded? Loaded on boot. > Are the trace_printk's in the core kernel too, and not being printed? I don't have any trace_printk()s in the core kernel, only in modules. Perhaps module initialization does not communicate trace_printk formats? -- error compiling committee.c: too many arguments to function