qemu-devel
[Top][All Lists]
Advanced

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

Re: [Qemu-devel] Virtio related trace events.


From: Stefan Hajnoczi
Subject: Re: [Qemu-devel] Virtio related trace events.
Date: Wed, 10 Aug 2016 10:56:05 +0100
User-agent: Mutt/1.6.2 (2016-07-01)

On Tue, Aug 09, 2016 at 09:15:20AM +0530, Gadre Nayan wrote:
> echo virtqueue_kick_prepare > /sys/kernel/debug/tracing/set_ftrace_filter
> echo virtqueue_kick >> /sys/kernel/debug/tracing/set_ftrace_filter
> echo scsi_kick_queue >> /sys/kernel/debug/tracing/set_ftrace_filter
> echo virtio_dev_match >> /sys/kernel/debug/tracing/set_ftrace_filter
> echo virtio_config_changed >> /sys/kernel/debug/tracing/set_ftrace_filter
> echo virtio_dev_remove >> /sys/kernel/debug/tracing/set_ftrace_filter
> echo virtio_uevent >> /sys/kernel/debug/tracing/set_ftrace_filter
> echo unregister_virtio_driver >> /sys/kernel/debug/tracing/set_ftrace_filter
> echo register_virtio_device >> /sys/kernel/debug/tracing/set_ftrace_filter
> echo unregister_virtio_device >> /sys/kernel/debug/tracing/set_ftrace_filter
> echo virtio_init >> /sys/kernel/debug/tracing/set_ftrace_filter
> echo virtio_check_driver_offered_feature >>
> /sys/kernel/debug/tracing/set_ftrace_filter
> echo register_virtio_driver >> /sys/kernel/debug/tracing/set_ftrace_filter
> echo virtio_finalize_features >> /sys/kernel/debug/tracing/set_ftrace_filter
> echo virtio_config_enable >> /sys/kernel/debug/tracing/set_ftrace_filter
> echo virtio_dev_probe >> /sys/kernel/debug/tracing/set_ftrace_filter
> echo virtio_device_restore >> /sys/kernel/debug/tracing/set_ftrace_filter
> echo virtio_device_freeze >> /sys/kernel/debug/tracing/set_ftrace_filter
> echo virtio_break_device >> /sys/kernel/debug/tracing/set_ftrace_filter
> echo virtio_mmio_remove >> /sys/kernel/debug/tracing/set_ftrace_filter
> echo virtio_mmio_probe >> /sys/kernel/debug/tracing/set_ftrace_filter
> echo virtio_pci_modern_probe >> /sys/kernel/debug/tracing/set_ftrace_filter
> echo virtio_pci_modern_remove >> /sys/kernel/debug/tracing/set_ftrace_filter
> echo virtio_pci_release_dev >> /sys/kernel/debug/tracing/set_ftrace_filter
> echo virtio_pci_restore >> /sys/kernel/debug/tracing/set_ftrace_filter
> echo virtio_pci_freeze >> /sys/kernel/debug/tracing/set_ftrace_filter
> echo virtio_pci_remove >> /sys/kernel/debug/tracing/set_ftrace_filter
> echo virtio_pci_probe >> /sys/kernel/debug/tracing/set_ftrace_filter
> echo virtio_pci_legacy_probe >> /sys/kernel/debug/tracing/set_ftrace_filter
> echo virtio_pci_legacy_remove >> /sys/kernel/debug/tracing/set_ftrace_filter
> echo virtio_queue_rq >> /sys/kernel/debug/tracing/set_ftrace_filter

These functions are in the virtio guest drivers.  You can trace them
inside the guest, the host doesn't call them.

I guess you haven't set up ftrace correctly.  If you have trouble with
ftrace, try using perf-probe(1).

Stefan

Attachment: signature.asc
Description: PGP signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]