Emilio G. Cota 
		cb764d0665 
		
	 
	
	
	qsp: track BQL callers explicitly ... 
			The BQL is acquired via qemu_mutex_lock_iothread(), which makes
the profiler assign the associated wait time (i.e. most of
BQL wait time) entirely to that function. This loses the original
call site information, which does not help diagnose BQL contention.
Fix it by tracking the callers explicitly.
Signed-off-by: Emilio G. Cota <cota@braap.org>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com> 
		
	 
		2018-08-23 18:46:25 +02:00 
	 
	
	
		 
	
	
		
			
			
			
			
			
			2018-02-09 13:50:17 +01:00 
		 
	
		
			
			
			
			
			
			2018-02-09 13:50:17 +01:00 
		 
	
		
			
			
			
			
			
			2018-02-09 13:50:17 +01:00 
		 
	
		
			
			
			
			
			
			2018-02-09 13:50:17 +01:00 
		 
	
		
			
			
			
			
			
			2016-03-17 15:47:56 +01:00 
		 
	
		
			
			
			
			
			
			2016-03-17 15:47:56 +01:00 
		 
	
		
			
			
			
			
			
			2016-02-16 14:29:28 +00:00 
		 
	
		
			
			
			
			
			
			2017-08-15 10:03:27 -05:00 
		 
	
		
			
			
			
			
			
			2016-03-15 18:23:45 +01:00 
		 
	
		
			
			
			
			
			
			2016-02-04 17:01:04 +00:00 
		 
	
		
			
			
			
			
			
			2017-03-14 13:28:29 +01:00 
		 
	
		
			
			
			
			
			
			2018-02-09 13:52:10 +01:00 
		 
	
		
			
			
			
			
			
			2018-07-24 17:35:23 +01:00 
		 
	
		
			
			
			
			
			
			2016-02-04 17:01:04 +00:00 
		 
	
		
			
			
			
			
			
			2018-06-18 15:48:22 +02:00 
		 
	
		
			
			
			
			
			
			2016-03-22 22:20:16 +01:00 
		 
	
		
			
			
			
			
			
			2016-02-04 17:01:04 +00:00 
		 
	
		
			
			
			
			
			
			2018-08-23 18:46:25 +02:00 
		 
	
		
			
			
			
			
			
			2016-10-28 21:50:18 +08:00 
		 
	
		
			
			
			
			
			
			2016-02-04 17:01:04 +00:00 
		 
	
		
			
			
			
			
			
			2018-06-27 13:06:34 +01:00 
		 
	
		
			
			
			
			
			
			2018-03-12 16:12:46 +01:00 
		 
	
		
			
			
			
			
			
			2018-05-07 10:00:02 -03:00 
		 
	
		
			
			
			
			
			
			2017-05-17 12:04:59 +02:00 
		 
	
		
			
			
			
			
			
			2018-07-23 14:00:03 +02:00 
		 
	
		
			
			
			
			
			
			2016-02-04 17:01:04 +00:00 
		 
	
		
			
			
			
			
			
			2017-01-23 21:25:37 -02:00 
		 
	
		
			
			
			
			
			
			2017-09-08 16:15:17 +03:00 
		 
	
		
			
			
			
			
			
			2018-05-07 10:00:02 -03:00 
		 
	
		
			
			
			
			
			
			2016-02-04 17:01:04 +00:00 
		 
	
		
			
			
			
			
			
			2018-02-08 09:22:03 +08:00 
		 
	
		
			
			
			
			
			
			2018-03-12 16:12:50 +01:00 
		 
	
		
			
			
			
			
			
			2016-02-04 17:01:04 +00:00 
		 
	
		
			
			
			
			
			
			2017-02-21 11:14:07 +00:00 
		 
	
		
			
			
			
			
			
			2016-05-19 16:42:28 +02:00 
		 
	
		
			
			
			
			
			
			2016-02-04 17:01:04 +00:00 
		 
	
		
			
			
			
			
			
			2016-03-22 22:20:16 +01:00 
		 
	
		
			
			
			
			
			
			2016-03-22 22:20:16 +01:00 
		 
	
		
			
			
			
			
			
			2018-03-02 13:45:50 -06:00 
		 
	
		
			
			
			
			
			
			2016-10-12 09:35:54 +02:00 
		 
	
		
			
			
			
			
			
			2018-03-02 13:45:50 -06:00 
		 
	
		
			
			
			
			
			
			2016-02-04 17:01:04 +00:00 
		 
	
		
			
			
			
			
			
			2018-03-02 13:45:50 -06:00 
		 
	
		
			
			
			
			
			
			2017-05-17 12:04:59 +02:00 
		 
	
		
			
			
			
			
			
			2017-04-25 11:04:34 -07:00 
		 
	
		
			
			
			
			
			
			2018-03-02 13:45:50 -06:00