On Mon, 07 Oct 2019 10:43:27 +0100,
Andrew Murray <andrew.murray@xxxxxxx> wrote:
>
> On Sun, Oct 06, 2019 at 11:46:36AM +0100, maz@xxxxxxxxxx wrote:
> > From: Marc Zyngier <maz@xxxxxxxxxx>
> >
> > The PMU emulation code uses the perf event sample period to trigger
> > the overflow detection. This works fine for the *first* overflow
> > handling
>
> Although, even though the first overflow is timed correctly, the value
> the guest reads may be wrong...
>
> Assuming a Linux guest with the arm_pmu.c driver, if I recall correctly
> this writes the -remainingperiod to the counter upon stopping/starting.
> In the case of a perf_event that is pinned to a task, this will happen
> upon every context switch of that task. If the counter was getting close
> to overflow before the context switch, then the value written to the
> guest counter will be very high and thus the sample_period written in KVM
> will be very low...
>
> The best scenario is when the host handles the overflow, the guest
> handles its overflow and rewrites the guest counter (resulting in a new
> host perf_event) - all before the first host perf_event fires again. This
> is clearly the assumption the code makes.
>
> Or - the host handles its overflow and kicks the guest, but the guest
> doesn't respond in time, so we end up endlessly and pointlessly kicking it
> for each host overflow - thus resulting in the large difference between number
> of interrupts between host and guest. This isn't ideal, because when the
> guest does read its counter, the value isn't correct (because it overflowed
> a zillion times at a value less than the arrchitected max).
>
> Worse still is when the sample_period is so small, the host doesn't
> even keep up.
Well, there are plenty of ways to make this code go mad. The
overarching reason is that we abuse the notion of sampling period to
generate interrupts, while what we'd really like is something that
says "call be back in that many events", rather than the sampling
period which doesn't match the architecture.
Yes, small values will results in large drifts. Nothing we can do
about it.
>
> > , but results in a huge number of interrupts on the host,
> > unrelated to the number of interrupts handled in the guest (a x20
> > factor is pretty common for the cycle counter). On a slow system
> > (such as a SW model), this can result in the guest only making
> > forward progress at a glacial pace.
> >
> > It turns out that the clue is in the name. The sample period is
> > exactly that: a period. And once the an overflow has occured,
> > the following period should be the full width of the associated
> > counter, instead of whatever the guest had initially programed.
> >
> > Reset the sample period to the architected value in the overflow
> > handler, which now results in a number of host interrupts that is
> > much closer to the number of interrupts in the guest.
>
> This seems a reasonable pragmatic approach - though of course you will end
> up counting slightly slower due to the host interrupt latency. But that's
> better than the status quo.
Slower than what?
>
> It may be possible with perf to have a single-fire counter (this mitigates
> against my third scenario but you still end up with a loss of precision) -
> See PERF_EVENT_IOC_REFRESH.
Unfortunately, that's a userspace interface, not something that's
available to the kernel at large...
> Ideally the PERF_EVENT_IOC_REFRESH type of functionality could be updated
> to reload to a different value after the first hit.
Which is what I was hinting at above. I'd like a way to reload the
next period on each expiration, much like a timer.
>
> This problem also exists on arch/x86/kvm/pmu.c (though I'm not sure what
> their PMU drivers do with respect to the value they write).
>
> >
> > Fixes: b02386eb7dac ("arm64: KVM: Add PMU overflow interrupt routing")
> > Signed-off-by: Marc Zyngier <maz@xxxxxxxxxx>
> > ---
> > virt/kvm/arm/pmu.c | 12 ++++++++++++
> > 1 file changed, 12 insertions(+)
> >
> > diff --git a/virt/kvm/arm/pmu.c b/virt/kvm/arm/pmu.c
> > index c30c3a74fc7f..3ca4761fc0f5 100644
> > --- a/virt/kvm/arm/pmu.c
> > +++ b/virt/kvm/arm/pmu.c
> > @@ -444,6 +444,18 @@ static void kvm_pmu_perf_overflow(struct perf_event *perf_event,
> > struct kvm_pmc *pmc = perf_event->overflow_handler_context;
> > struct kvm_vcpu *vcpu = kvm_pmc_to_vcpu(pmc);
> > int idx = pmc->idx;
> > + u64 val, period;
> > +
> > + /* Start by resetting the sample period to the architectural limit */
> > + val = kvm_pmu_get_pair_counter_value(vcpu, pmc);
> > +
> > + if (kvm_pmu_idx_is_64bit(vcpu, pmc->idx))
>
> This is correct, because in this case we *do* care about _PMCR_LC.
>
> > + period = (-val) & GENMASK(63, 0);
> > + else
> > + period = (-val) & GENMASK(31, 0);
> > +
> > + pmc->perf_event->attr.sample_period = period;
> > + pmc->perf_event->hw.sample_period = period;
>
> I'm not sure about the above line - does direct manipulation of sample_period
> work on a running perf event? As far as I can tell this is already done in the
> kernel with __perf_event_period - however this also does other stuff (such as
> disable and re-enable the event).
I'm not sure you could do that in the handler, which is run in atomic
context. It doesn't look like anything bad happens when updating the
sample period directly (the whole thing has stopped getting crazy),
but I'd really like someone who understands the perf internals to help
here (hence Mark being on cc).
Thanks,
M.
--
Jazz is not dead, it just smells funny.
_______________________________________________
kvmarm mailing list
kvmarm@xxxxxxxxxxxxxxxxxxxxx
https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
