WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

RE: [Xen-devel] [PATCH] Allow mini-os to unbind all evtchns

To: "Dietmar Hahn" <dietmar.hahn@xxxxxxxxxxxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: RE: [Xen-devel] [PATCH] Allow mini-os to unbind all evtchns
From: "Petersson, Mats" <Mats.Petersson@xxxxxxx>
Date: Wed, 29 Nov 2006 14:32:32 +0100
Cc: Keir Fraser <keir@xxxxxxxxxxxxx>, Jacob Gorm Hansen <jacobg@xxxxxxx>, Grzegorz Milos <gm281@xxxxxxxxx>
Delivery-date: Wed, 29 Nov 2006 05:32:51 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <200611291426.41973.dietmar.hahn@xxxxxxxxxxxxxxxxxxx>
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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AccTuhobOflXevkORaef5t1iSVb5fgAAGK2A
Thread-topic: [Xen-devel] [PATCH] Allow mini-os to unbind all evtchns
 

> -----Original Message-----
> From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx 
> [mailto:xen-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of 
> Dietmar Hahn
> Sent: 29 November 2006 13:27
> To: xen-devel@xxxxxxxxxxxxxxxxxxx
> Cc: Jacob Gorm Hansen; Keir Fraser; Grzegorz Milos
> Subject: Re: [Xen-devel] [PATCH] Allow mini-os to unbind all evtchns
> 
> Am Mittwoch, 29. November 2006 13:25 schrieb Keir Fraser:
> > ...
> > It looked bogus to me. What if event channels are 
> bound/unbound/bound
> > multiple times during the mini-os lifetime (can't happen 
> right now, but
> > maybe in future). The port array will overflow. Perhaps it 
> should be a
> What does it means "maybe in future"?

> Has it to do with:
> > On Fri, 2006-11-24 at 13:27 +0100, Jacob Gorm Hansen wrote:
> >> ...
> >> ports unbound. This is necessary when using mini-os as the 
> foundation
> >> for a boot-loader.
> Can anybody give me a hint!

I'm not sure that is what Keir meant - more like: If you implement
something, you may just as well think about any future extended features
if it doesn't cause too much problems, for example using a bitmap
instead of a plain array. 

Another solution in this case would be to search/clear the array so that
multiple bind/unbind operations don't cause the array content to "grow".


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



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