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: Thu, 15 Oct 2009 10:23:07 -0700 Message-ID: <4AD75A7B.7000404@goop.org> References: <8FED46E8A9CA574792FC7AACAC38FE7714FCC2ED95@PDSMSX501.ccr.corp.intel.com> <4AD62D4A.7030301@goop.org> <8FED46E8A9CA574792FC7AACAC38FE7714FCC2EFBF@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: <8FED46E8A9CA574792FC7AACAC38FE7714FCC2EFBF@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 19:13, Wei, Gang wrote: > Call disable_hpet() in dom0 xen setup phase will disable physical hpet and > break hpet usage in hypervisor. There are another path to initialize hpet: > fs_initcall(hpet_late_init), hpet_late_init()->hpet_enable(). > Well, making disable_hpet() non-static and calling it from Xen setup is the same as appending nohpet to the command line, but less hacky. J