Re: trace_printk() support in trace-cmd

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, 2010-11-15 at 19:09 +0200, Avi Kivity wrote:
> trace-cmd doesn't like trace_printk():
> 
> <...>-23775 [000] 26343.288803: kvm_emulate_insn:     0:f14e9: rep insb
> <...>-23775 [000] 26343.288804: bprint:               x86_emulate_insn : 
> (NO FORMAT FOUND at ffffffffa0131460)
> 
> <...>-23775 [000] 26343.288807: bprint:               x86_emulate_insn : 
> (NO FORMAT FOUND at ffffffffa0131460)
> 
> any chance to get it to work with custom printks?
> 
> I guess I should use 'perf probe' instead.
> 

Which kernel are you using, and/or which trace-cmd? It works fine for
me. But there has been bugs with older kernels and older trace-cmds.

-- Steve


--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [KVM ARM]     [KVM ia64]     [KVM ppc]     [Virtualization Tools]     [Spice Development]     [Libvirt]     [Libvirt Users]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite Questions]     [Linux Kernel]     [Linux SCSI]     [XFree86]
  Powered by Linux