On Fri, Jan 3, 2014 at 6:46 AM, yuxh <yuxinghai@xxxxxxxxxxxxxx> wrote:
> Hi all,
>
> Happy new year!
>
> The existing trace mechanism in libvirt is dtrace. Although the dtrace
> can work, it's not work well enough. Every time we want get information
> from the trace point we must write a systemtap script and run it
> together with libvirt.
>
> That's really unpractical on some occasion, especially on production
> server since the systemtap script can't be executed automatically.
> And some problems may be not easy to reproduce, then it will cost a
> lot of time to get the trace information again.
>
> So I think it is essential to add supporting for record the trace
> information automatically in libvirt to satisfy the user's requirement.
> That's why I'm currently implementing ftrace support in libvirt.
>
> How do you think about my idea? Any comment will be appreciated!
>
How hard/painless it would be to implement it? And, can you have
both and then select which one to use?
> Thanks,
> Yu
>
> --
> libvir-list mailing list
> libvir-list@xxxxxxxxxx
> https://www.redhat.com/mailman/listinfo/libvir-list
_______________________________________________
libvirt-users mailing list
libvirt-users@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/libvirt-users
