Re: Tapsets with wildcards in the process() statement ?

["Daniel P. Berrange" <berrange at redhat dot com>]

On Tue, Oct 19, 2010 at 09:34:53AM -0700, Josh Stone wrote:
> On 10/19/2010 09:05 AM, Daniel P. Berrange wrote:
> > The 'process("qemu")' statement in my qemu.stp file will only match
> > one of the binaries though. I would like todo 'process("qemu*")'
> > but systemtap doesn't seem to like that wildcard syntax here:
> 
> We've wanted this for a while, and I think Frank recently started to
> tackle it, so hopefully we'll have it for the next release.
> 
> http://sourceware.org/bugzilla/show_bug.cgi?id=6456
> 
> In the mean time, you could chain these together as optional aliases,
> which is cumbersome, but perhaps could be generated with a script:
> 
>   probe qemu.foo =
>     process("qemu").mark("foo") ? ,
>     process("qemu-system-x86_64").mark("foo") ? ,
>     ...
>     process("qemu-kvm").mark("foo") ?
>   {
>     ...
>   }

Thanks, I didn't notice this chaining syntax before. The whole tapset
file is auto-generated, so I can easily try this out and not worry
about the slight ugliness...

Regards,
Daniel
-- 
|: Red Hat, Engineering, London    -o-   http://people.redhat.com/berrange/ :|
|: http://libvirt.org -o- http://virt-manager.org -o- http://deltacloud.org :|
|: http://autobuild.org        -o-         http://search.cpan.org/~danberr/ :|
|: GnuPG: 7D3B9505  -o-   F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|