[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170530095947.4cc19990@xeon-e3>
Date: Tue, 30 May 2017 09:59:47 -0700
From: Stephen Hemminger <stephen@...workplumber.org>
To: Vitaly Kuznetsov <vkuznets@...hat.com>
Cc: x86@...nel.org, devel@...uxdriverproject.org,
Stephen Hemminger <sthemmin@...rosoft.com>,
Jork Loeser <Jork.Loeser@...rosoft.com>,
Haiyang Zhang <haiyangz@...rosoft.com>,
linux-kernel@...r.kernel.org, Steven Rostedt <rostedt@...dmis.org>,
Andy Shevchenko <andy.shevchenko@...il.com>,
Ingo Molnar <mingo@...hat.com>,
Andy Lutomirski <luto@...nel.org>,
"H. Peter Anvin" <hpa@...or.com>,
Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [PATCH v5 02/10] x86/hyper-v: stash the max number of
virtual/logical processor
On Tue, 30 May 2017 13:34:16 +0200
Vitaly Kuznetsov <vkuznets@...hat.com> wrote:
> diff --git a/arch/x86/kernel/cpu/mshyperv.c b/arch/x86/kernel/cpu/mshyperv.c
> index 04cb8d3..bdcc433 100644
> --- a/arch/x86/kernel/cpu/mshyperv.c
> +++ b/arch/x86/kernel/cpu/mshyperv.c
> @@ -175,9 +175,15 @@ static void __init ms_hyperv_init_platform(void)
> ms_hyperv.misc_features = cpuid_edx(HYPERV_CPUID_FEATURES);
> ms_hyperv.hints = cpuid_eax(HYPERV_CPUID_ENLIGHTMENT_INFO);
>
> - pr_info("HyperV: features 0x%x, hints 0x%x\n",
> + pr_info("Hyper-V: features 0x%x, hints 0x%x\n",
> ms_hyperv.features, ms_hyperv.hints);
>
> + ms_hyperv.max_vp_index = cpuid_eax(HVCPUID_IMPLEMENTATION_LIMITS);
> + ms_hyperv.max_lp_index = cpuid_ebx(HVCPUID_IMPLEMENTATION_LIMITS);
> +
> + pr_info("Hyper-V: max %u virtual processors, %u logical processors\n",
> + ms_hyperv.max_vp_index, ms_hyperv.max_lp_index);
> +
I understand as developer why you may need to log stuff.
Do we really need more logging here? Why not pr_debug()?
Powered by blists - more mailing lists