|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [PATCH v3 09/11] x86/vpt: switch interrupt injection model
On Wed, Apr 14, 2021 at 04:05:20PM +0200, Jan Beulich wrote:
> On 14.04.2021 15:37, Roger Pau Monné wrote:
> > On Wed, Apr 14, 2021 at 12:28:43PM +0200, Jan Beulich wrote:
> >> On 31.03.2021 12:33, Roger Pau Monne wrote:
> >>> ---
> >>> xen/arch/x86/hvm/svm/intr.c | 3 -
> >>> xen/arch/x86/hvm/vmx/intr.c | 59 ------
> >>> xen/arch/x86/hvm/vpt.c | 334 ++++++++++++++--------------------
> >>> xen/include/asm-x86/hvm/vpt.h | 5 +-
> >>> 4 files changed, 143 insertions(+), 258 deletions(-)
> >>
> >> Nice.
> >>
> >>> @@ -285,189 +238,144 @@ static void pt_irq_fired(struct vcpu *v, struct
> >>> periodic_time *pt)
> >>> list_del(&pt->list);
> >>> pt->on_list = false;
> >>> pt->pending_intr_nr = 0;
> >>> +
> >>> + return;
> >>> }
> >>> - else if ( mode_is(v->domain, one_missed_tick_pending) ||
> >>> - mode_is(v->domain, no_missed_ticks_pending) )
> >>> +
> >>> + if ( mode_is(v->domain, one_missed_tick_pending) ||
> >>> + mode_is(v->domain, no_missed_ticks_pending) )
> >>> {
> >>> - pt->last_plt_gtime = hvm_get_guest_time(v);
> >>> pt_process_missed_ticks(pt);
> >>> pt->pending_intr_nr = 0; /* 'collapse' all missed ticks */
> >>> + }
> >>> + else if ( !pt->pending_intr_nr )
> >>> + pt_process_missed_ticks(pt);
> >>
> >> Did you lose a -- here? I.e. does the condition mean to match ...
> >>
> >>> + if ( !pt->pending_intr_nr )
> >>> set_timer(&pt->timer, pt->scheduled);
> >>> +}
> >>> +
> >>> +static void pt_timer_fn(void *data)
> >>> +{
> >>> + struct periodic_time *pt = data;
> >>> + struct vcpu *v;
> >>> + time_cb *cb = NULL;
> >>> + void *cb_priv;
> >>> + unsigned int irq;
> >>> +
> >>> + pt_lock(pt);
> >>> +
> >>> + v = pt->vcpu;
> >>> + irq = pt->irq;
> >>> +
> >>> + if ( inject_interrupt(pt) )
> >>> + {
> >>> + pt->scheduled += pt->period;
> >>> + pt->do_not_freeze = 0;
> >>> + cb = pt->cb;
> >>> + cb_priv = pt->priv;
> >>> }
> >>> else
> >>> {
> >>> - pt->last_plt_gtime += pt->period;
> >>> - if ( --pt->pending_intr_nr == 0 )
> >>
> >> ... this original code? Otherwise I can't see why the condition
> >> guards a pt_process_missed_ticks() invocation.
> >
> > I think the logic here changed enough to not match anymore. Certainly
> > pending_intr_nr shouldn't be decreased there, as pt_irq_fired is
> > invoked after an EOI in this patch, instead of being invoked when a
> > vpt related interrupt was injected. I think I should better rename
> > pt_irq_fired to pt_irq_eoi and that would make it clearer.
>
> But pt_process_missed_ticks() should be called only when a tick was
> missed, shouldn't it?
No, I think the purpose of the function is to update the
pending_intr_nr field, ie: calculate if and how many ticks have been
missed.
It's fine for pt_process_missed_ticks to return without having changed
pending_intr_nr at all if no ticks have been missed.
> Or actually, looking at the function, I guess
> I'm confused. Does your patch change the meaning of the field?
Not really, I think pt_process_missed_ticks has always had this logic.
The pending_intr_nr filed should still have the same logic, account
for the amount of missed ticks up to the value in the scheduled field.
> > FWIW, decreasing pending_intr_nr should only be done after an
> > inject_interrupt call.
>
> Then this line (which you leave in place)
>
> pt->pending_intr_nr = 0; /* 'collapse' all missed ticks */
>
> is contradicting the (new) model.
Oh, right, that's mode specific. no_missed_ticks_pending will just
drop any interrupts that haven't been injected when they should have
been. I had the 'account missed ticks' mode in mind when I wrote that.
I now have pt_irq_fired as:
static void irq_eoi(struct periodic_time *pt)
{
if ( pt->one_shot )
{
pt->pending_intr_nr = 0;
return;
}
pt_process_missed_ticks(pt);
/* 'collapse' missed ticks according to the selected mode. */
switch ( pt->vcpu->domain->arch.hvm.params[HVM_PARAM_TIMER_MODE] )
{
case HVMPTM_one_missed_tick_pending:
pt->pending_intr_nr = min(pt->pending_intr_nr, 1u);
break;
case HVMPTM_no_missed_ticks_pending:
pt->pending_intr_nr = 0;
break;
}
if ( !pt->pending_intr_nr )
{
/* Make sure timer follows vCPU. */
migrate_timer(&pt->timer, current->processor);
set_timer(&pt->timer, pt->scheduled);
}
}
But I think it's best if I post it as a new version, so you can see
the context.
Thanks, Roger.
|
![]() |
Lists.xenproject.org is hosted with RackSpace, monitoring our |