Description of problem:

regression when use systemtap  test tracepoint

Version-Release number of selected component (if applicable):

#uname -r
2.6.32-262.el6.x86_64
#rpm -qa |grep qemu-kvm
qemu-kvm-0.12.1.2-2.282.el6.x86_64
#rpm -qa |grep systemtap
systemtap-1.7-3.el6.x86_64

How reproducible:

100%
Steps to Reproduce:
#cat balloon_event.stp

probe qemu.kvm.balloon_event

{  printf("opaque = %p,  addr =%u ",opaque,addr);

}
1.[root@dhcp-65-153 tracing-script]# stap balloon_event.stp
parse error: expected literal string or number
        saw: operator '=' at /usr/share/systemtap/tapset/qemu-kvm.stp:814:8
     source:   next = $arg1;
                    ^
1 parse error.
WARNING: tapset '/usr/share/systemtap/tapset/qemu-kvm.stp' has errors, and will be skipped.
semantic error: probe point mismatch at position 0  (alternatives: __nfs __scheduler __signal __tcpmib __vm _linuxmib _signal _sunrpc _syscall _vfs begin begin(number) end end(number) error error(number) generic ioblock ioblock_trace ioscheduler ioscheduler_trace ipmib irq_handler kernel kprobe kprocess libvirt linuxmib module(string) nd_syscall netdev never nfs nfsd perf process process(number) process(string) procfs procfs(string) python scheduler scsi signal socket softirq stap staprun sunrpc syscall tcp tcpmib timer tty udp vfs vm workqueue): identifier 'qemu' at balloon_event.stp:1:7 while resolving probe point qemu.kvm.balloon_event
        source: probe qemu.kvm.balloon_event
                      ^
Pass 2: analysis failed.  Try again with another '--vp 01' option.


2.
3.
  
Actual results:
can not probe tracepoint

Expected results:

can be probe
Additional info:bug 720979 seem like the same problem,but fixed on virsion qemu-kvm-0.12.1.2-2.181.el6