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

RE: [Xen-devel]Two dead-lock situation occurs on 32bit HVM SMP Windows

To: "Keir Fraser" <keir@xxxxxxxxxxxxx>, "Xin, Xiaohui" <xiaohui.xin@xxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
From: "Li, Xin B" <xin.b.li@xxxxxxxxx>
Date: Wed, 15 Nov 2006 02:02:30 +0800
Cc: "Mallick, Asit K" <asit.k.mallick@xxxxxxxxx>, "Tian, Kevin" <kevin.tian@xxxxxxxxx>, "Li, Susie" <susie.li@xxxxxxxxx>, "He, Qing" <qing.he@xxxxxxxxx>, "Nakajima, Jun" <jun.nakajima@xxxxxxxxx>
Delivery-date: Tue, 14 Nov 2006 10:02:51 -0800
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
Thread-index: AccAF9dKTIq91n6sSkWEGX/0OhiYJwAK0KTSAfN1PNAAAKU53QAAC2cwAAClB2MAABubMA==
Thread-topic: [Xen-devel]Two dead-lock situation occurs on 32bit HVM SMP Windows

>
>I'll leave it to Tim to decide what the best thing to do here 
>is. But I'm
>sure we don't need a max_gpfn parameter. Xen could maintain its own
>highwater mark, updated by the alloc_p2m path, if it needs it.

Yeah, surely that also works for me.  I'm thinking about max gpfn may
change during guest lifecycle, and we need maintain it.
-Xin

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

Prev by Date: Re: [Xen-devel]Two dead-lock situation occurs on 32bit HVM SMP Windows
Next by Date: Re: [Xen-devel] Is anyone working on HVM Paravirt drivers for windows?
Previous by thread: Re: [Xen-devel]Two dead-lock situation occurs on 32bit HVM SMP Windows
Next by thread: RE: [Xen-devel] Re: Getting rid of xenbus_suspend(): tpmfrontdriver impacted?
Index(es):
- Date
- Thread

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