trace: document how to specify multiple --trace patterns
It is possible to repeat the --trace option to specify multiple patterns. This may be preferrable to users who do not want to create a file with a list of patterns. Suggested-by: BALATON Zoltan <balaton@eik.bme.hu> Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com> Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com> Message-id: 20210112165859.225534-2-stefanha@redhat.com Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
This commit is contained in:
		
							parent
							
								
									c6e93c9d62
								
							
						
					
					
						commit
						3faf22ef44
					
				| @ -22,10 +22,15 @@ events:: | ||||
| This output comes from the "log" trace backend that is enabled by default when | ||||
| ``./configure --enable-trace-backends=BACKENDS`` was not explicitly specified. | ||||
| 
 | ||||
| More than one trace event pattern can be specified by providing a file | ||||
| instead:: | ||||
| Multiple patterns can be specified by repeating the ``--trace`` option:: | ||||
| 
 | ||||
|     $ qemu --trace "kvm_*" --trace "virtio_*" ... | ||||
| 
 | ||||
| When patterns are used frequently it is more convenient to store them in a | ||||
| file to avoid long command-line options:: | ||||
| 
 | ||||
|     $ echo "memory_region_ops_*" >/tmp/events | ||||
|     $ echo "kvm_*" >>/tmp/events | ||||
|     $ qemu --trace events=/tmp/events ... | ||||
| 
 | ||||
| Trace events | ||||
|  | ||||
		Loading…
	
	
			
			x
			
			
		
	
		Reference in New Issue
	
	Block a user
	 Stefan Hajnoczi
						Stefan Hajnoczi