linux-hyperv.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Praveen Kumar <kumarpraveen@linux.microsoft.com>
To: Wei Liu <wei.liu@kernel.org>
Cc: linux-hyperv@vger.kernel.org, linux-kernel@vger.kernel.org,
	kys@microsoft.com, haiyangz@microsoft.com,
	sthemmin@microsoft.com, decui@microsoft.com, tglx@linutronix.de,
	mingo@redhat.com, bp@alien8.de, nunodasneves@linux.microsoft.com,
	viremana@linux.microsoft.com, sunilmut@microsoft.com,
	Michael Kelley <mikelley@microsoft.com>
Subject: Re: [PATCH] x86/hyperv: LP creation with lp_index on same CPU-id
Date: Mon, 31 May 2021 16:31:04 +0530	[thread overview]
Message-ID: <572da60e-714f-b207-a89e-6dc40209e2da@linux.microsoft.com> (raw)
In-Reply-To: <20210531105732.muzbpk4yksttsfwz@liuwe-devbox-debian-v2>



On 5/31/2021 4:27 PM, Wei Liu wrote:
> On Mon, May 31, 2021 at 01:10:46PM +0530, Praveen Kumar wrote:
>> The hypervisor expects the lp_index to be same as cpu-id during LP creation
>> This fix correct the same, as cpu_physical_id can give different cpu-id.
> 
> Code looks fine to me, but the commit message can be made clearer.
> 
> """
> The hypervisor expects the logical processor index to be the same as
> CPU's id during logical processor creation. Using cpu_physical_id
> confuses Microsoft Hypervisor's scheduler. That causes the root
> partition not boot when core scheduler is used.
> 
> This patch removes the call to cpu_physical_id and uses the CPU index
> directly for bringing up logical processor. This scheme works for both
> classic scheduler and core scheduler.
> 
> Fixes: 333abaf5abb3 (x86/hyperv: implement and use hv_smp_prepare_cpus)
> """
> 
> No action is required from you. If you are fine with this commit message
> I can incorporate it and update the subject line when committing this
> patch.
> 

Thanks Wei for your comments. I'm fine with your inputs. Please go ahead. Thanks.

Regards,

~Praveen.

>>
>> Signed-off-by: Praveen Kumar <kumarpraveen@linux.microsoft.com>
>> ---
>>  arch/x86/kernel/cpu/mshyperv.c | 2 +-
>>  1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/arch/x86/kernel/cpu/mshyperv.c b/arch/x86/kernel/cpu/mshyperv.c
>> index 22f13343b5da..4fa0a4280895 100644
>> --- a/arch/x86/kernel/cpu/mshyperv.c
>> +++ b/arch/x86/kernel/cpu/mshyperv.c
>> @@ -236,7 +236,7 @@ static void __init hv_smp_prepare_cpus(unsigned int max_cpus)
>>  	for_each_present_cpu(i) {
>>  		if (i == 0)
>>  			continue;
>> -		ret = hv_call_add_logical_proc(numa_cpu_node(i), i, cpu_physical_id(i));
>> +		ret = hv_call_add_logical_proc(numa_cpu_node(i), i, i);
>>  		BUG_ON(ret);
>>  	}
>>  
>> -- 
>> 2.25.1
>>

  reply	other threads:[~2021-05-31 11:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-31  7:40 [PATCH] x86/hyperv: LP creation with lp_index on same CPU-id Praveen Kumar
2021-05-31 10:57 ` Wei Liu
2021-05-31 11:01   ` Praveen Kumar [this message]
2021-06-02 15:16     ` Wei Liu

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=572da60e-714f-b207-a89e-6dc40209e2da@linux.microsoft.com \
    --to=kumarpraveen@linux.microsoft.com \
    --cc=bp@alien8.de \
    --cc=decui@microsoft.com \
    --cc=haiyangz@microsoft.com \
    --cc=kys@microsoft.com \
    --cc=linux-hyperv@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mikelley@microsoft.com \
    --cc=mingo@redhat.com \
    --cc=nunodasneves@linux.microsoft.com \
    --cc=sthemmin@microsoft.com \
    --cc=sunilmut@microsoft.com \
    --cc=tglx@linutronix.de \
    --cc=viremana@linux.microsoft.com \
    --cc=wei.liu@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).