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

[Xen-devel] Timer and dynamic tick


  • To: xen <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: Marco Tizzoni <marco.tizzoni@xxxxxxxxx>
  • Date: Thu, 10 Dec 2009 22:57:07 +0100
  • Delivery-date: Thu, 10 Dec 2009 13:58:29 -0800
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:from:date:x-google-sender-auth:message-id :subject:to:content-type; b=evqfqc1pSQ1xwnNGxI+1lwYuLk7Ax1VDgTwjDhVgugCnT8XP8MHPZspXRbj6dRpUqO SyvsCDbZQueXCTNA5ZnyTsQOD+QQPMNdRwz+8V/TjKj7tJuRyw0O/ERYKudCnRgRPbpj oRNjJqD6ZkxRD6N2McKr1UHC0u8Y5aAKCNjHY=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

Hello,
sorry for cross-posting but probably devel it's more appropriate.

I'd understand if setting CONFIG_NO_HZ=y in dom0/domU is required/suggested.

Because Xen supports no-tick-on-idle mechanism (http://virt.kernelnewbies.org/ParavirtBenefits#head-360a0849a0639297396542dddcc691e4100287ab) ticks come from the hypervisor only when needed by the guest so, in my understanding, setting CONFIG_NO_HZ=n will make no difference. Any comments?

Regards,
Marco
_______________________________________________
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®.