On 05/09/2017 03:00 AM, Peter Xu wrote:
It'll be nice to know which virq belongs to which device/vector when
adding msi routes, so adding two more parameters for the add trace.
Meanwhile, releasing virq has no tracing before. Add one for it.
Signed-off-by: Peter Xu
Reviewed-by: Philippe Math
It'll be nice to know which virq belongs to which device/vector when
adding msi routes, so adding two more parameters for the add trace.
Meanwhile, releasing virq has no tracing before. Add one for it.
Signed-off-by: Peter Xu
---
kvm-all.c| 4 +++-
trace-events | 3 ++-
2 files changed, 5 i
