On Thu, Jul 23, 2020 at 12:00:09AM +0200, Thomas Gleixner wrote:
> From: Thomas Gleixner <t...@linutronix.de>
>
> Use the generic infrastructure to check for and handle pending work before
> transitioning into guest mode.
>
> This now handles TIF_NOTIFY_RESUME as well which was ignored so
> far. Handling it is important as this covers task work and task work will
> be used to offload the heavy lifting of POSIX CPU timers to thread context.
>
> Signed-off-by: Thomas Gleixner <t...@linutronix.de>
> ---
> V5: Rename exit -> xfer
> ---
One nit/question below (though it's really about patch 5).
Reviewed-and-tested-by: Sean Christopherson <sean.j.christopher...@intel.com>
> @@ -8676,15 +8677,11 @@ static int vcpu_run(struct kvm_vcpu *vcp
> break;
> }
>
> - if (signal_pending(current)) {
> - r = -EINTR;
> - vcpu->run->exit_reason = KVM_EXIT_INTR;
> - ++vcpu->stat.signal_exits;
> - break;
> - }
> - if (need_resched()) {
> + if (xfer_to_guest_mode_work_pending()) {
> srcu_read_unlock(&kvm->srcu, vcpu->srcu_idx);
> - cond_resched();
> + r = xfer_to_guest_mode(vcpu);
Any reason not to call this xfer_to_guest_mode_work()? Or handle_work(),
do_work(), etc... Without the "work" part, it looks like a function that
should be invoked unconditionally. It's obvious that's not the case if
one looks at the implementation, but it's a bit confusing on the KVM side
of things.
> + if (r)
> + return r;
> vcpu->srcu_idx = srcu_read_lock(&kvm->srcu);
> }
> }
>
