[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <cfc43786-5a9d-4813-b8ac-a8a55f430f03@redhat.com>
Date: Mon, 20 Oct 2025 17:05:37 +0200
From: Paolo Bonzini <pbonzini@...hat.com>
To: Sean Christopherson <seanjc@...gle.com>,
Shrikanth Hegde <sshegde@...ux.ibm.com>
Cc: 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,
vschneid@...hat.com, iii@...ux.ibm.com, huschle@...ux.ibm.com,
rostedt@...dmis.org, dietmar.eggemann@....com, vineeth@...byteword.org,
jgross@...e.com
Subject: Re: [RFC PATCH v3 00/10] paravirt CPUs and push task for less vCPU
preemption
On 10/20/25 16:32, Sean Christopherson wrote:
> : Till the hint from underlying hypervisor arrives, another idea is to
> : approximate the hint from steal time.
I think this is the first thing to look at.
Perhaps single_task_running() can be exposed in the x86 steal time data
structure, and in fact even in the rseq data for non-VM usecases? This
is not specific to VMs and I'd like the steal time implementation to
follow the footsteps of rseq rather than the opposite.
Paolo
Powered by blists - more mailing lists