On Tue, Apr 16, 2024 at 07:07:32AM -0700, Sean Christopherson wrote: > On Tue, Apr 16, 2024, Marcelo Tosatti wrote: > > On Mon, Apr 15, 2024 at 02:29:32PM -0700, Sean Christopherson wrote: > > > And snapshotting the VM-Exit time will get false negatives when the vCPU is about > > > to run, but for whatever reason has kvm_last_guest_exit=0, e.g. if a vCPU was > > > preempted and/or migrated to a different pCPU. > > > > Right, for the use-case where waking up rcuc is a problem, the pCPU is > > isolated (there are no userspace processes and hopefully no kernel threads > > executing there), vCPU pinned to that pCPU. > > > > So there should be no preemptions or migrations. > > I understand that preemption/migration will not be problematic if the system is > configured "correctly", but we still need to play nice with other scenarios and/or > suboptimal setups. While false positives aren't fatal, KVM still should do its > best to avoid them, especially when it's relatively easy to do so. Sure. > > > My understanding is that RCU already has a timeout to avoid stalling RCU. I don't > > > see what is gained by effectively duplicating that timeout for KVM. > > > > The point is not to avoid stalling RCU. The point is to not perform RCU > > core processing through rcuc thread (because that interrupts execution > > of the vCPU thread), if it is known that an extended quiescent state > > will occur "soon" anyway (via VM-entry). > > I know. My point is that, as you note below, RCU will wake-up rcuc after 1 second > even if KVM is still reporting a VM-Enter is imminent, i.e. there's a 1 second > timeout to avoid an RCU stall to due to KVM never completing entry to the guest. Right. So a reply to the sentence: "My understanding is that RCU already has a timeout to avoid stalling RCU. I don't see what is gained by effectively duplicating that timeout for KVM." Is that the current RCU timeout is not functional for KVM VM entries, therefore it needs modification. > > If the extended quiescent state does not occur in 1 second, then rcuc > > will be woken up (the time_before call in rcu_nohz_full_cpu function > > above). > > > > > Why not have > > > KVM provide a "this task is in KVM_RUN" flag, and then let the existing timeout > > > handle the (hopefully rare) case where KVM doesn't "immediately" re-enter the guest? > > > > Do you mean something like: > > > > diff --git a/kernel/rcu/tree.c b/kernel/rcu/tree.c > > index d9642dd06c25..0ca5a6a45025 100644 > > --- a/kernel/rcu/tree.c > > +++ b/kernel/rcu/tree.c > > @@ -3938,7 +3938,7 @@ static int rcu_pending(int user) > > return 1; > > > > /* Is this a nohz_full CPU in userspace or idle? (Ignore RCU if so.) */ > > - if ((user || rcu_is_cpu_rrupt_from_idle()) && rcu_nohz_full_cpu()) > > + if ((user || rcu_is_cpu_rrupt_from_idle() || this_cpu->in_kvm_run) && rcu_nohz_full_cpu()) > > return 0; > > Yes. This, https://lore.kernel.org/all/ZhAN28BcMsfl4gm-@xxxxxxxxxx, plus logic > in kvm_sched_{in,out}(). Question: where is vcpu->wants_to_run set? (or, where is the full series again?). diff --git a/virt/kvm/kvm_main.c b/virt/kvm/kvm_main.c index bfb2b52a1416..5a7efc669a0f 100644 --- a/virt/kvm/kvm_main.c +++ b/virt/kvm/kvm_main.c @@ -209,6 +209,9 @@ void vcpu_load(struct kvm_vcpu *vcpu) { int cpu = get_cpu(); + if (vcpu->wants_to_run) + context_tracking_guest_start_run_loop(); + __this_cpu_write(kvm_running_vcpu, vcpu); preempt_notifier_register(&vcpu->preempt_notifier); kvm_arch_vcpu_load(vcpu, cpu); @@ -222,6 +225,10 @@ void vcpu_put(struct kvm_vcpu *vcpu) kvm_arch_vcpu_put(vcpu); preempt_notifier_unregister(&vcpu->preempt_notifier); __this_cpu_write(kvm_running_vcpu, NULL); + + if (vcpu->wants_to_run) + context_tracking_guest_stop_run_loop(); + preempt_enable(); } EXPORT_SYMBOL_GPL(vcpu_put); A little worried about guest HLT: /** * rcu_is_cpu_rrupt_from_idle - see if 'interrupted' from idle * * If the current CPU is idle and running at a first-level (not nested) * interrupt, or directly, from idle, return true. * * The caller must have at least disabled IRQs. */ static int rcu_is_cpu_rrupt_from_idle(void) { long nesting; /* * Usually called from the tick; but also used from smp_function_call() * for expedited grace periods. This latter can result in running from * the idle task, instead of an actual IPI. */ ... /* Does CPU appear to be idle from an RCU standpoint? */ return ct_dynticks_nesting() == 0; } static __always_inline void ct_cpuidle_enter(void) { lockdep_assert_irqs_disabled(); /* * Idle is allowed to (temporary) enable IRQs. It * will return with IRQs disabled. * * Trace IRQs enable here, then switch off RCU, and have * arch_cpu_idle() use raw_local_irq_enable(). Note that * ct_idle_enter() relies on lockdep IRQ state, so switch that * last -- this is very similar to the entry code. */ trace_hardirqs_on_prepare(); lockdep_hardirqs_on_prepare(); instrumentation_end(); ct_idle_enter(); lockdep_hardirqs_on(_RET_IP_); } So for guest HLT emulation, there is a window between kvm_vcpu_block -> fire_sched_out_preempt_notifiers -> vcpu_put and the idle's task call to ct_cpuidle_enter, where ct_dynticks_nesting() != 0 and vcpu_put has already executed. Even for idle=poll, the race exists. > > /* Is the RCU core waiting for a quiescent state from this CPU? */ > > > > The problem is: > > > > 1) You should only set that flag, in the VM-entry path, after the point > > where no use of RCU is made: close to guest_state_enter_irqoff call. > > Why? As established above, KVM essentially has 1 second to enter the guest after > setting in_guest_run_loop (or whatever we call it). In the vast majority of cases, > the time before KVM enters the guest can probably be measured in microseconds. OK. > Snapshotting the exit time has the exact same problem of depending on KVM to > re-enter the guest soon-ish, so I don't understand why this would be considered > a problem with a flag to note the CPU is in KVM's run loop, but not with a > snapshot to say the CPU recently exited a KVM guest. See the race above. > > 2) While handling a VM-exit, a host timer interrupt can occur before that, > > or after the point where "this_cpu->in_kvm_run" is set to false. > > > > And a host timer interrupt calls rcu_sched_clock_irq which is going to > > wake up rcuc. > > If in_kvm_run is false when the IRQ is handled, then either KVM exited to userspace > or the vCPU was scheduled out. In the former case, rcuc won't be woken up if the > CPU is in userspace. And in the latter case, waking up rcuc is absolutely the > correct thing to do as VM-Enter is not imminent. > > For exits to userspace, there would be a small window where an IRQ could arrive > between KVM putting the vCPU and the CPU actually returning to userspace, but > unless that's problematic in practice, I think it's a reasonable tradeoff. OK, your proposal looks alright except these races. We don't want those races to occur in production (and they likely will). Is there any way to fix the races? Perhaps cmpxchg?
