[Bug 216737] New: Call trace happens on guest after running pt vmx tool

[bugzilla-daemon@kernel.org]

https://bugzilla.kernel.org/show_bug.cgi?id=216737

            Bug ID: 216737
           Summary: Call trace happens on guest after running pt vmx tool
           Product: Virtualization
           Version: unspecified
    Kernel Version: 6.1.0-rc4
          Hardware: Intel
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: kvm
          Assignee: virtualization_kvm@kernel-bugs.osdl.org
          Reporter: lixiao.yang@intel.com
        Regression: No

Created attachment 303284
  --> https://bugzilla.kernel.org/attachment.cgi?id=303284&action=edit
Guest dmesg log

Environment:
CPU Architecture: x86_64
Host OS: Red Hat Enterprise Linux 8.4 (Ootpa)
Host kernel: 6.1.0-rc4
Guest OS: Red Hat Enterprise Linux 8.3 (Ootpa)
Guest kernel:5.19.0-rc8
gcc: gcc version 8.4.1
Host kernel source: https://git.kernel.org/pub/scm/virt/kvm/kvm.git
Branch: next
Commit: d72cf8ff

Qemu source: https://git.qemu.org/git/qemu.git
Branch: master
Commit: 6d71357a

Bug Detailed Description:
There are call traces on guest after running pt vmx tool on guest. 

Reproducing Steps:
1. Create a guest:
qemu-system-x86_64 -accel kvm -m 4096 -smp 4 -drive
file=/share/xvs/var/tmp-img_kvm_ptvmx_snapshot_1653283173,if=none,id=virtio-disk0
-device virtio-blk-pci,drive=virtio-disk0,bootindex=0  -cpu host -device
virtio-net-pci,netdev=nic0,mac=00:98:31:f3:d3:59 -netdev
tap,id=nic0,br=virbr0,helper=/usr/local/libexec/qemu-bridge-helper,vhost=on
-monitor pty -daemonize -vnc :11024

2.Log into the guest and run pt_vmx_tool
./pt_vmx_tool/BAT-ipt

Actual Result:
Call trace happens on guest.

Expected Result:
No call trace happens on guest.

Call trace log:
[   54.937709] Call Trace:
[   54.938287]  <TASK>
[   54.938796]  intel_pmu_enable_bts+0x5c/0x70
[   54.939443]  bts_event_add+0x7b/0xa0
[   54.940036]  event_sched_in.isra.133.part.134+0x7a/0x1b0
[   54.940744]  ? sysvec_apic_timer_interrupt+0xab/0xc0
[   54.941428]  merge_sched_in+0x27e/0x4e0
[   54.942029]  visit_groups_merge.constprop.144+0x137/0x460
[   54.942739]  ctx_sched_in+0xcf/0x1e0
[   54.943315]  ctx_resched+0x54/0x90
[   54.943878]  event_function+0x95/0xe0
[   54.944454]  ? perf_duration_warn+0x30/0x30
[   54.945065]  remote_function+0x4a/0x60
[   54.945649]  generic_exec_single+0x64/0xa0
[   54.946244]  smp_call_function_single+0xbd/0x180
[   54.946883]  ? perf_duration_warn+0x30/0x30
[   54.947472]  ? visit_groups_merge.constprop.144+0x164/0x460
[   54.949322]  ? perf_mux_hrtimer_handler+0x330/0x330
[   54.949961]  ? perf_duration_warn+0x30/0x30
[   54.950545]  task_function_call+0x55/0x90
[   54.951109]  ? perf_swevent_get_recursion_context+0x70/0x70
[   54.951781]  event_function_call+0x96/0x120
[   54.952350]  ? perf_mux_hrtimer_handler+0x330/0x330
[   54.952975]  ? __perf_event_task_sched_in+0x5c/0x1d0
[   54.953638]  ? _perf_event_disable+0x50/0x50
[   54.954215]  ? _perf_event_disable+0x50/0x50
[   54.954788]  perf_event_for_each_child+0x37/0x80
[   54.955379]  ? _perf_event_disable+0x50/0x50
[   54.955944]  _perf_ioctl+0x1a6/0x840
[   54.956447]  ? __schedule+0x3fc/0x980
[   54.956960]  ? preempt_count_add+0x70/0xa0
[   54.957495]  ? _raw_spin_lock_irq+0x19/0x40
[   54.958035]  ? ptrace_stop+0x200/0x2a0
[   54.958543]  ? ptrace_do_notify+0x92/0xc0
[   54.959057]  perf_ioctl+0x43/0x70
[   54.959532]  __x64_sys_ioctl+0x89/0xc0
...
Please refer to the attached file for the complete dmesg information.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.