While I was adding new failing code at the end of the function, I noticed
that the vtimers are not freed which messes up all the timers and will crash
Xen quickly when the page s reused.
Currently neither vcpu_vgic_init nor vcpu_vtimer_init fails, so we
are safe for now. With the new GICv3 code, the former function will be able
to fail. This will result in a memory leak.
Call vcpu_destroy if the initialization has failed. We also need to add a
boolean to know if the vtimers are correctly setup as the timer common code
doesn't have any safeguard against removing a non-initialized timer.
Signed-off-by: Julien Grall <julien.grall@linaro.org>
Acked-by: Ian Campbell <ian.campbell@citrix.com>
processor_vcpu_initialise(v);
if ( (rc = vcpu_vgic_init(v)) != 0 )
- return rc;
+ goto fail;
if ( (rc = vcpu_vtimer_init(v)) != 0 )
- return rc;
+ goto fail;
return rc;
+
+fail:
+ vcpu_destroy(v);
+ return rc;
}
void vcpu_destroy(struct vcpu *v)
: GUEST_TIMER_VIRT_PPI;
t->v = v;
+ v->arch.vtimer_initialized = 1;
+
return 0;
}
void vcpu_timer_destroy(struct vcpu *v)
{
+ if ( !v->arch.vtimer_initialized )
+ return;
+
kill_timer(&v->arch.virt_timer.timer);
kill_timer(&v->arch.phys_timer.timer);
}
struct vtimer phys_timer;
struct vtimer virt_timer;
+ bool_t vtimer_initialized;
} __cacheline_aligned;
void vcpu_show_execution_state(struct vcpu *);