Jinank Jain 3414586995 arch: Change the default topology for x86 guests ... Currently by default each core is allocated it's own socket. Basically it is n socket 1 core 1 thread/core kind of a structure as witnessed from within the guest. CPU(s): 8 On-line CPU(s) list: 0-7 Thread(s) per core: 1 Core(s) per socket: 1 Socket(s): 8 NUMA node(s): 1 This is not a good default topology because resources are distributed across multiple sockets. For example, a Linux guest with multi socket configuration will have to calibrate TSC per socket due to which it might observe a higher amount of boot time than usual. A better idea for default topology would be 1 socket n core 1 thread/core which ensure better resource locality. After this change topology would change to: CPU(s): 8 On-line CPU(s) list: 0-7 Thread(s) per core: 1 Core(s) per socket: 8 Socket(s): 1 NUMA node(s): 1 Fixes: #6497 Signed-off-by: Jinank Jain <jinankjain@microsoft.com>		2024-06-04 17:08:18 +00:00
..
src	arch: Change the default topology for x86 guests	2024-06-04 17:08:18 +00:00
build.rs	build: Add "fuzzing" as a valid cfg(..) attribute	2024-05-08 08:10:28 +00:00
Cargo.toml	build: Bump range_map_vec from 0.1.0 to 0.2.0	2024-06-01 00:53:03 +00:00