Re: [Xen-devel] Question to [PATCH 2 of 3] PoD: Allow pod_set_ca

To:	Jan Beulich <JBeulich@xxxxxxxxxx>
Subject:	Re: [Xen-devel] Question to [PATCH 2 of 3] PoD: Allow pod_set_cache_target hypercall to be preempted
From:	Dietmar Hahn <dietmar.hahn@xxxxxxxxxxxxxx>
Date:	Tue, 15 Mar 2011 13:01:49 +0100
Cc:	George Dunlap <George.Dunlap@xxxxxxxxxxxxx>, xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date:	Tue, 15 Mar 2011 05:03:45 -0700
Dkim-signature:	v=1; a=rsa-sha256; c=simple/simple; d=ts.fujitsu.com; i=dietmar.hahn@xxxxxxxxxxxxxx; q=dns/txt; s=s1536b; t=1300190513; x=1331726513; h=from:to:subject:date:cc:references:in-reply-to: mime-version:content-transfer-encoding:message-id; bh=2fmz9UxMmtmcdXNh9CvXM48m/QNICjZVYSfQt5Shra4=; b=dE07iW6vg1YnN+zYrpzsNZTPtcQM/9X/oXCJSJdR2OSryfpDtZrqGCNC 8P+1pP0rHcHj4p6qz7XMaogjt8YwEmpT04GEapJDCUM/3Mzneb2C3l9w/ f1SroG+E6Lb/ReYDKYBxFfdIC3AynXDrGbzs3qoDwBLPHU5Op9mUaHZXO /HLKe0Qo4QnOQ+QvNYZzq5WRKqXZ2WRKhKVEwYGBn3EUNV1jgn5M4Q1iF d9w43ioa7MC54bjHd+WQ3WoJkqTxC;
Domainkey-signature:	s=s1536a; d=ts.fujitsu.com; c=nofws; q=dns; h=X-SBRSScore:X-IronPort-AV:Received:X-IronPort-AV: Received:Received:From:To:Subject:Date:User-Agent:Cc: References:In-Reply-To:X-KMail-Markup:MIME-Version: Content-Type:Content-Transfer-Encoding:Message-Id; b=A+bChglC5eLU0v0V0EV3/1cNpp/d6nISHP50zyMiTn/qULjUl9STx+i1 6sP5WNyAIvw/iHLjxISNm31dGCXgafwljZe8rNeBE+js/d4kSsHZyzqtm SlnuOXBW9zKdIjhrKCHRdTvPppvLCSOSqEK5Tp7fkEkLBWYyLtJpTO9Ow KQgAgYqKpJKQKhgSaEOuhRQGk0gS4f/FPQ479bkxDokxStbI028KxrnVa xB92pHr8vflVXWniaa0Hehzm4kSWT;
Envelope-to:	www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to:	<4D7F42380200007800036869@xxxxxxxxxxxxxxxxxx>
List-help:	<mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id:	Xen developer discussion <xen-devel.lists.xensource.com>
List-post:	<mailto:xen-devel@lists.xensource.com>
List-subscribe:	<http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe:	<http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References:	<201103151000.12411.dietmar.hahn@xxxxxxxxxxxxxx> <4D7F42380200007800036869@xxxxxxxxxxxxxxxxxx>
Sender:	xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent:	KMail/1.13.6 (Linux/2.6.34.7-0.7-xen; KDE/4.6.0; x86_64; ; )

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

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

WARNING - OLD ARCHIVES

xen-devel

Re: [Xen-devel] Question to [PATCH 2 of 3] PoD: Allow pod_set_cache_targ