From: Shrikanth Hegde <sshegde@linux.vnet.ibm.com>
To: "Aneesh Kumar K.V" <aneesh.kumar@linux.ibm.com>
Cc: linuxppc-dev@lists.ozlabs.org,
Srikar Dronamraju <srikar@linux.vnet.ibm.com>,
npiggin@gmail.com
Subject: Re: [PATCH] powerpc/sched: Cleanup vcpu_is_preempted()
Date: Tue, 14 Nov 2023 14:53:16 +0530 [thread overview]
Message-ID: <a326ce8a-431f-45dd-a225-691f6f965b6f@linux.vnet.ibm.com> (raw)
In-Reply-To: <20231114071219.198222-1-aneesh.kumar@linux.ibm.com>
On 11/14/23 12:42 PM, Aneesh Kumar K.V wrote:
> No functional change in this patch. A helper is added to find if
> vcpu is dispatched by hypervisor. Use that instead of opencoding.
> Also clarify some of the comments.
>
> Signed-off-by: Aneesh Kumar K.V <aneesh.kumar@linux.ibm.com>
> ---
> arch/powerpc/include/asm/paravirt.h | 33 ++++++++++++++++++++++-------
> 1 file changed, 25 insertions(+), 8 deletions(-)
>
> diff --git a/arch/powerpc/include/asm/paravirt.h b/arch/powerpc/include/asm/paravirt.h
> index ac4279208d63..b78b82d66057 100644
> --- a/arch/powerpc/include/asm/paravirt.h
> +++ b/arch/powerpc/include/asm/paravirt.h
> @@ -76,6 +76,17 @@ static inline bool is_vcpu_idle(int vcpu)
> {
> return lppaca_of(vcpu).idle;
> }
> +
> +static inline bool vcpu_is_dispatched(int vcpu)
> +{
> + /*
> + * This is the yield_count. An "odd" value (low bit on) means that
> + * the processor is yielded (either because of an OS yield or a
> + * hypervisor preempt). An even value implies that the processor is
> + * currently executing.
> + */
> + return (!(yield_count_of(vcpu) & 1));
> +}
> #else
> static inline bool is_shared_processor(void)
> {
> @@ -109,6 +120,10 @@ static inline bool is_vcpu_idle(int vcpu)
> {
> return false;
> }
> +static inline bool vcpu_is_dispatched(int vcpu)
> +{
> + return true;
> +}
> #endif
>
Similar code can be changed in lib/qspinlock.c and lib/locks.c as well.
> #define vcpu_is_preempted vcpu_is_preempted
> @@ -134,12 +149,12 @@ static inline bool vcpu_is_preempted(int cpu)
> * If the hypervisor has dispatched the target CPU on a physical
> * processor, then the target CPU is definitely not preempted.
> */
> - if (!(yield_count_of(cpu) & 1))
> + if (vcpu_is_dispatched(cpu))
> return false;
>
> /*
> - * If the target CPU has yielded to Hypervisor but OS has not
> - * requested idle then the target CPU is definitely preempted.
> + * if the target CPU is not dispatched and the guest OS
> + * has not marked the CPU idle, then it is hypervisor preempted.
> */
> if (!is_vcpu_idle(cpu))
> return true;
> @@ -166,7 +181,7 @@ static inline bool vcpu_is_preempted(int cpu)
>
> /*
> * The PowerVM hypervisor dispatches VMs on a whole core
> - * basis. So we know that a thread sibling of the local CPU
> + * basis. So we know that a thread sibling of the executing CPU
> * cannot have been preempted by the hypervisor, even if it
> * has called H_CONFER, which will set the yield bit.
> */
> @@ -174,15 +189,17 @@ static inline bool vcpu_is_preempted(int cpu)
> return false;
>
> /*
> - * If any of the threads of the target CPU's core are not
> - * preempted or ceded, then consider target CPU to be
> - * non-preempted.
> + * The specific target CPU was marked by guest OS as idle, but
> + * then also check all other cpus in the core for PowerVM
> + * because it does core scheduling and one of the vcpu
> + * of the core getting preempted by hypervisor implies
> + * other vcpus can also be considered preempted.
> */
> first_cpu = cpu_first_thread_sibling(cpu);
> for (i = first_cpu; i < first_cpu + threads_per_core; i++) {
> if (i == cpu)
> continue;
> - if (!(yield_count_of(i) & 1))
> + if (vcpu_is_dispatched(i))
> return false;
> if (!is_vcpu_idle(i))
> return true;
next prev parent reply other threads:[~2023-11-14 9:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-14 7:12 [PATCH] powerpc/sched: Cleanup vcpu_is_preempted() Aneesh Kumar K.V
2023-11-14 9:23 ` Shrikanth Hegde [this message]
2023-11-14 9:29 ` Aneesh Kumar K V
2023-11-14 9:46 ` Srikar Dronamraju
2023-11-14 10:15 ` Aneesh Kumar K V
2023-11-14 15:56 ` Srikar Dronamraju
2023-12-21 10:38 ` Michael Ellerman
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=a326ce8a-431f-45dd-a225-691f6f965b6f@linux.vnet.ibm.com \
--to=sshegde@linux.vnet.ibm.com \
--cc=aneesh.kumar@linux.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=npiggin@gmail.com \
--cc=srikar@linux.vnet.ibm.com \
/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).