[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1d406410-631d-487a-9b02-ed23d2cb8302@amd.com>
Date: Thu, 11 Sep 2025 22:25:07 +0530
From: K Prateek Nayak <kprateek.nayak@....com>
To: Shrikanth Hegde <sshegde@...ux.ibm.com>
CC: <vschneid@...hat.com>, <iii@...ux.ibm.com>, <huschle@...ux.ibm.com>,
<rostedt@...dmis.org>, <dietmar.eggemann@....com>, <vineeth@...byteword.org>,
<jgross@...e.com>, <pbonzini@...hat.com>, <seanjc@...gle.com>,
<mingo@...hat.com>, <peterz@...radead.org>, <juri.lelli@...hat.com>,
<vincent.guittot@...aro.org>, <tglx@...utronix.de>, <yury.norov@...il.com>,
<maddy@...ux.ibm.com>, <linux-kernel@...r.kernel.org>,
<linuxppc-dev@...ts.ozlabs.org>, <gregkh@...uxfoundation.org>
Subject: Re: [RFC PATCH v3 05/10] sched/fair: Don't consider paravirt CPUs for
wakeup and load balance
Hello Shrikanth,
On 9/11/2025 9:26 PM, Shrikanth Hegde wrote:
>>> +check_new_cpu:
>>> + if (is_cpu_paravirt(new_cpu))
>>> + return cpu;
>>> + else
>>
>> nit. redundant else.
>>
>
> Do you mean "is_cpu_paravirt(new_cpu) ? cpu; new_cpu"
Sorry for the confusion! I meant we can have:
if (is_cpu_paravirt(new_cpu))
return cpu;
return new_cpu;
Since we return from the if clause, we don't need to specify else.
--
Thanks and Regards,
Prateek
Powered by blists - more mailing lists