Le 29/01/2026 à 15:06, Jan Beulich a écrit : > On 29.01.2026 14:58, Teddy Astie wrote: >> While we may not want all the other CPU informations. We likely >> want to keep the CPU string as it's more practical than trying to >> decode it from the family/model/stepping combination. > > Yet why would we want it logged several hundred times by default, on a > big enough system? IOW ... >
Ah I see; one idea I had was to move this to early_cpu_init() or somewhere similar, and only displaying it once (only for BSP ?) ? >> --- a/xen/arch/x86/cpu/common.c >> +++ b/xen/arch/x86/cpu/common.c >> @@ -819,9 +819,6 @@ void print_cpu_info(unsigned int cpu) >> const struct cpuinfo_x86 *c = cpu_data + cpu; >> const char *vendor = NULL; >> >> - if (!opt_cpu_info) >> - return; > > ... this conditional doesn't want removing, but amending. E.g. > > if (!opt_cpu_info && system_state >= SYS_STATE_smp_boot) > return; > > Jan > -- Teddy Astie | Vates XCP-ng Developer XCP-ng & Xen Orchestra - Vates solutions web: https://vates.tech
