September 12, 20169 yr Here's a command to print your socket info, including which core and which ones are hyperthreaded together: <cpus num='8'> <cpu id='0' socket_id='0' core_id='0' siblings='0,4'/> <cpu id='1' socket_id='0' core_id='1' siblings='1,5'/> <cpu id='2' socket_id='0' core_id='2' siblings='2,6'/> <cpu id='3' socket_id='0' core_id='3' siblings='3,7'/> <cpu id='4' socket_id='0' core_id='0' siblings='0,4'/> <cpu id='5' socket_id='0' core_id='1' siblings='1,5'/> <cpu id='6' socket_id='0' core_id='2' siblings='2,6'/> <cpu id='7' socket_id='0' core_id='3' siblings='3,7'/> </cpus> Here's a command to see what vcpus are being used by your VM. In this example, I have my VM configured for emulatorpin on 1,5 and vcpu pinning for 2,6,3,7. So you can see that 2,6,3,7 have more CPU usage. (Sadly, 200% total CPU for an idle system, after login. ) $ ps -mo pid,tid,%cpu,psr,cmd --sort=+psr -p `pgrep qemu` PID TID %CPU PSR CMD 1428 - 184 - /usr/bin/qemu-system-x86_64 -name Windows 10 -machine pc-i440fx-2.5,accel=kvm,usb=off,me - 1428 9.4 1 - - 1433 0.0 5 - - 1435 43.3 2 - - 1436 43.7 6 - - 1437 44.1 3 - - 1438 43.6 7 - - 13620 0.0 5 - - 19283 0.0 1 -
Archived
This topic is now archived and is closed to further replies.