From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: trace_printk() support in trace-cmd Date: Sun, 12 Dec 2010 18:35:24 +0200 Message-ID: <4D04F9CC.3060908@redhat.com> References: <4CE16941.3080008@redhat.com> <1289920433.30543.5.camel@gandalf.stny.rr.com> <4CEB9FCE.9020108@redhat.com> <1290522640.30543.306.camel@gandalf.stny.rr.com> <4CEBD1AE.7000203@redhat.com> <1290527132.30543.372.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: <1290527132.30543.372.camel@gandalf.stny.rr.com> Sender: linux-trace-users-owner@vger.kernel.org List-Id: kvm.vger.kernel.org On 11/23/2010 05:45 PM, Steven Rostedt wrote: > Again, the work around is to replace your trace_printks() with > __trace_printk(_THIS_IP_, ...) or just modify the trace_printk() macro > in include/linux/kernel.h to always use the __trace_printk() version. This works; I'm using it for now (I tried to use 'perf probe', but I get unpredictable results, like null pointer derefs). -- error compiling committee.c: too many arguments to function