|
Am 15.03.2011 schrieb "Jan Beulich <JBeulich@xxxxxxxxxx>":
> >>> On 15.03.11 at 10:00, Dietmar Hahn <dietmar.hahn@xxxxxxxxxxxxxx> wrote:
> > I had a look at hypercall_create_continuation() and my understanding is that
> > the caller on this cpu is prepared to start the hypercall again after
> > getting scheduled next time and the hypercall is finished immediately to
> > deliver irqs and events.
> > But what about the other cpus in dom0? Are these waiting for an irq/event
> > from the cpu handling the long running hypercall?
> > How do these benefit from this hypercall continuation?
>
> One vCPU stuck in a long running hypercall can, depending on what
> locks/mutexes/semaphores it holds, keep other vCPU-s in the same
> domain from making progress. Whether that's what happens in
> your case can only be determined by looking at what those other
> vCPU-s were doing (or trying to do) at the time of the hang (from
> SysRq-t or '0' [or 'd'] debug key output).
>
> Jan
>
OK, thanks!
Dietmar.
--
Company details: http://ts.fujitsu.com/imprint.html | 
