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

["Petersson, Mats" <Mats.Petersson@xxxxxxx>]

> -----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