profiling virtio (blk in this case)

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

 



The "Host<-->Guest" calls in virtio_blk (using the generic virtio kick/notify)
are as follows:

Guest->Host
-----------
do_virtlkb_request calls kick in the guest side causing handle_output to be
called on the host side.

Host->Guest
-----------
virtio_blk_rw_complete calls notify in the host side causing block_done to be
called on the guest side

My question has to do with the timing of the calls.
Which would be the correct drawing
1. Overlapping:
kick             |------------|
handle_output             |------------|
2. Disjoint:
kick             |------------|
handle_output                    |------------|

In other words:
if I do
g1 = get_cpu_cycles
kick
g2 = get_cpu_cycles
and 
h1 = get_cpu_cycles
handle_output
h2 = get_cpu_cycles
would (g2-g1) + (h2-h2) count some cycles twice?

Same question for notify and block_done.

Thanks very much,
Eran


--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [KVM ARM]     [KVM ia64]     [KVM ppc]     [Virtualization Tools]     [Spice Development]     [Libvirt]     [Libvirt Users]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite Questions]     [Linux Kernel]     [Linux SCSI]     [XFree86]
  Powered by Linux