[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20250425162331.qwpzuc-8@linutronix.de>
Date: Fri, 25 Apr 2025 18:23:31 +0200
From: Sebastian Andrzej Siewior <bigeasy@...utronix.de>
To: Shrikanth Hegde <sshegde@...ux.ibm.com>
Cc: npiggin@...il.com, vaibhav@...ux.ibm.com, maddy@...ux.ibm.com,
linuxppc-dev@...ts.ozlabs.org, christophe.leroy@...roup.eu,
gautam@...ux.ibm.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/2] powerpc: kvm: use generic transfer to guest mode work
On 2025-04-25 19:54:56 [+0530], Shrikanth Hegde wrote:
> > > But looking at the semantics of usage of xfer_to_guest_mode_work
> > > I think using schedule is probably right over here.
> > > Correct me if i got it all wrong.
> >
> > No, if you do xfer_to_guest_mode_work() then it will invoke schedule()
> > when appropriate. It just the thing in kvmhv_run_single_vcpu() looks odd
> > and might have been duct tape or an accident and could probably be
> > removed.
> >
>
> I was wondering xfer_to_guest_mode_work could also call cond_resched
> instead of schedule since for preempt=full/lazy is preemptible
> as early as possible right?
No, I think it is okay. For preempt=full you shouldn't observe the
flag in xfer_to_guest_mode_work() so it does not matter.
Sebastian
Powered by blists - more mailing lists