[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20191028162734.GI1554@sasha-vm>
Date: Mon, 28 Oct 2019 12:27:34 -0400
From: Sasha Levin <sashal@...nel.org>
To: Michael Kelley <mikelley@...rosoft.com>
Cc: Andrea Parri <parri.andrea@...il.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-hyperv@...r.kernel.org" <linux-hyperv@...r.kernel.org>,
"x86@...nel.org" <x86@...nel.org>,
KY Srinivasan <kys@...rosoft.com>,
Haiyang Zhang <haiyangz@...rosoft.com>,
Stephen Hemminger <sthemmin@...rosoft.com>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>, Borislav Petkov <bp@...en8.de>,
"H . Peter Anvin" <hpa@...or.com>, vkuznets <vkuznets@...hat.com>,
Dexuan Cui <decui@...rosoft.com>, Wei Liu <wei.liu@...nel.org>
Subject: Re: [PATCH v2] x86/hyperv: Set pv_info.name to "Hyper-V"
On Tue, Oct 15, 2019 at 01:06:33PM +0000, Michael Kelley wrote:
>From: Andrea Parri <parri.andrea@...il.com> Sent: Tuesday, October 15, 2019 3:35 AM
>>
>> Michael reported that the x86/hyperv initialization code printed the
>> following dmesg when running in a VM on Hyper-V:
>>
>> [ 0.000738] Booting paravirtualized kernel on bare hardware
>>
>> Let the x86/hyperv initialization code set pv_info.name to "Hyper-V";
>> with this addition, the dmesg read:
>>
>> [ 0.000172] Booting paravirtualized kernel on Hyper-V
>>
>> Reported-by: Michael Kelley <mikelley@...rosoft.com>
>> Signed-off-by: Andrea Parri <parri.andrea@...il.com>
>
>Reviewed-by: Michael Kelley <mikelley@...rosoft.com>
Thomas, will you be taking this? Would you rather have me deal with the
hyperv bits under arch/x86/?
--
Thanks,
Sasha
Powered by blists - more mailing lists