From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeremy Fitzhardinge Subject: Re: [PATCH] Append 'nohpet' in dom0 cmdline to prevent dom0 from using HPET Date: Wed, 14 Oct 2009 12:58:02 -0700 Message-ID: <4AD62D4A.7030301@goop.org> References: <8FED46E8A9CA574792FC7AACAC38FE7714FCC2ED95@PDSMSX501.ccr.corp.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <8FED46E8A9CA574792FC7AACAC38FE7714FCC2ED95@PDSMSX501.ccr.corp.intel.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: "Wei, Gang" Cc: Xen-devel , Keir Fraser List-Id: xen-devel@lists.xenproject.org On 10/14/09 02:26, Wei, Gang wrote: > Append 'nohpet' in dom0 cmdline to prevent dom0 from using HPET > > Xen is using HPET to wakeup cpu from deep c-states, so the HPET usage in dom0 > must be fobidden. In 2.6.18-xen, the HPET was by default disabled in config > file. For upstream kernel built for pv dom0, it is not practical to disable dom0 > HPET usage in that way because the same image may be also using as bare metal > kernerl. So add cmdline option to do this thing for dom0. > I think it would be better to unstatic disable_hpet() and call it from Xen setup. But as far as I can see hpet_init() should never be called under Xen, because pv_time_ops won't be pointing to it, so there won't be any attempt to use the hpet. J