RE: [Xen-devel] [PATCH] Make HZ a boot-time configurable

To:	"Kip Macy" <kmacy@xxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject:	RE: [Xen-devel] [PATCH] Make HZ a boot-time configurable
From:	"Ian Pratt" <m+Ian.Pratt@xxxxxxxxxxxx>
Date:	Mon, 9 May 2005 06:21:03 +0100
Delivery-date:	Mon, 09 May 2005 05:20:39 +0000
Envelope-to:	www-data@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:	AcVUC92DGsXt1KkzRJ6p1rJ3Mk+2TwASstQw
Thread-topic:	[Xen-devel] [PATCH] Make HZ a boot-time configurable

> I understand the trade-offs that xen is currently optimized 
> for. However, I don't think that HZ=100 is right for all 
> places and all times. I also think that users would 
> appreciate it if they didn't have to go edit config.h and 
> re-compile if they wanted to change HZ. For those using xen 
> as a platform for development it probably makes sense if HZ 
> is the same as the kernel they intend to ship. For example, 
> very early on in testing with HZ=1000 I hit an interrupt race 
> condition in XenFreeBSD that I have never seen before.

I'd really prefer to kill the periodic ticker in Xen altogether. If
domains want a periodic ticker they should just set their alarm timer
appropriately.

Ian


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

WARNING - OLD ARCHIVES

xen-devel

RE: [Xen-devel] [PATCH] Make HZ a boot-time configurable