Description of problem:
The tapsets installed by qemu into /usr/share/systemtap/tapset/ try to use the name 'function' for a variable, but this is a reserved keyword.  This causes many warnings on pretty much any use of systemtap.  (stap will still run fine, provided you weren't hoping to use anything defined by those qemu*.stp)

Version-Release number of selected component (if applicable):
qemu-user-1.2.0-17.fc18.x86_64

How reproducible:
100%

Steps to Reproduce:
1. stap -l begin
  
Actual results:
Many parse errors across qemu tapsets, all like:
> parse error: expected statement
> 	saw: keyword at /usr/share/systemtap/tapset/qemu-x86_64.stp:1455:3
>      source:   function = $arg3;
>                ^
> parse error: expected identifier
> 	saw: operator '=' at /usr/share/systemtap/tapset/qemu-x86_64.stp:1455:12
>      source:   function = $arg3;
>                         ^
> 2 parse errors.

Expected results:
For "stap -l begin", it should just print "begin" with no errors.

Additional info:
This is related to the problem in bug #831763, just with 'function' this time.  The error looks like the same place in every qemu*.stp, just varying on which qemu binary is referenced:

1451 probe qemu.user.x86_64.usb_uas_tmf_unsupported = process("/usr/bin/qemu-x86_64").mark("usb_uas_tmf_unsupported")
1452 {
1453   addr = $arg1;
1454   tag = $arg2;
1455   function = $arg3;
1456 }