From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [PATCH trace-cmd] plugin_kvm: disassemble instructions for kvm_emulate_insn Date: Mon, 20 Sep 2010 11:51:34 +0200 Message-ID: <4C972EA6.2070704@redhat.com> References: <1284906837-2431-1-git-send-email-avi@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org, linux-trace-users@vger.kernel.org To: Steven Rostedt Return-path: In-Reply-To: <1284906837-2431-1-git-send-email-avi@redhat.com> Sender: linux-trace-users-owner@vger.kernel.org List-Id: kvm.vger.kernel.org On 09/19/2010 04:33 PM, Avi Kivity wrote: > Override kvm_emulate_insn formatting to use a disassembler to format > the emulated instruction. If a disassembler (udis86) is not available, > fall back to showing the instruction bytes in hex. > > Signed-off-by: Avi Kivity > --- > > Note 1: on top of 'master' with 'trace-cmd-kvm' cherry-picked on top. > > Note 2: I get output of the form > > ... kvm_emulate_insn: 0:fffff800010527b5: mov $0x0, 0xfffe00b0CAN'T FIND FIELD "guest_rip" > > which leads me to believe there is a bug in trace_seq_printf when the input > to %s is "". > > Note 3: this is not thread safe. If trace-cmd wants to be (or is) multithreaded, we need some kind of plugin context that is passed to all plugin methods, which is initialized separately for each thread. Or we can be lazy and use thread local storage. -- error compiling committee.c: too many arguments to function