[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <169840079677.2701453.9938577942475657211.b4-ty@ellerman.id.au>
Date: Fri, 27 Oct 2023 20:59:56 +1100
From: Michael Ellerman <patch-notifications@...erman.id.au>
To: Srikar Dronamraju <srikar@...ux.vnet.ibm.com>
Cc: linuxppc-dev <linuxppc-dev@...ts.ozlabs.org>,
Aboorva Devarajan <aboorvad@...ux.vnet.ibm.com>,
Shrikanth Hegde <sshegde@...ux.vnet.ibm.com>,
Ajay Kaher <akaher@...are.com>,
Alexey Makhalov <amakhalov@...are.com>,
VMware PV-Drivers Reviewers <pv-drivers@...are.com>,
Nicholas Piggin <npiggin@...il.com>,
Christophe Leroy <christophe.leroy@...roup.eu>,
virtualization@...ts.linux-foundation.org, x86@...nel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v4] powerpc/paravirt: Improve vcpu_is_preempted
On Thu, 19 Oct 2023 14:44:52 +0530, Srikar Dronamraju wrote:
> PowerVM Hypervisor dispatches on a whole core basis. In a shared LPAR, a
> CPU from a core that is CEDED or preempted may have a larger latency. In
> such a scenario, its preferable to choose a different CPU to run.
>
> If one of the CPUs in the core is active, i.e neither CEDED nor
> preempted, then consider this CPU as not preempted.
>
> [...]
Applied to powerpc/next.
[1/1] powerpc/paravirt: Improve vcpu_is_preempted
https://git.kernel.org/powerpc/c/efce8422dd53fae6cdbd37741034ac4eb4730819
cheers
Powered by blists - more mailing lists