[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] Question to [PATCH 2 of 3] PoD: Allow pod_set_cache_target hypercall to be preempted


  • To: "xen-devel" <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: Dietmar Hahn <dietmar.hahn@xxxxxxxxxxxxxx>
  • Date: Tue, 15 Mar 2011 10:00:11 +0100
  • Cc: Dunlap <George.Dunlap@xxxxxxxxxxxxx>
  • Delivery-date: Tue, 15 Mar 2011 02:01:45 -0700
  • 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: X-KMail-Markup:MIME-Version:Content-Type: Content-Transfer-Encoding:Message-Id; b=nlgeLNDkT0X9gbqElgo1a0BHUpDgbbFKMmQwFBIMIbaL5Gcp/go/Xuun XrAoBxPu5XPkfox2dgjyKsdnzMNTqh2VfR1T2hWpS3bd4IdEe7Q/7Wu6o HCOI3RUb9FQEjEzh1yQUkQyeS6sZSy9TTlAol/j/3VtViiJctIrGxo2Ic TfkAQkyTraRJfxXDyPQBt72PUsWVNvVWQ1hkP6SIlm0rGuRiNgOTv1qMw 6mYhT3QOKFtbSM8ROfjgr8OFRbvEl;
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

Hi,


we stumbled over this problem fixed in

http://lists.xensource.com/archives/html/xen-devel/2011-01/msg01155.html

on SLES11 SP1 with domU's with memory >= 64GB.

The effect was that dom0 seemed to hang even though our dom0 were running

on 3 cpus.

Now my question:

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?

Thanks!


Dietmar.


--

Company details: http://ts.fujitsu.com/imprint.html

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

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.