From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Dan Magenheimer" Subject: RE: [PATCH] clocksource=tsc Date: Tue, 15 Jul 2008 10:04:03 -0600 Message-ID: <20080715100403015.00000080236@djm-pc> References: <20080715094609687.00000080236@djm-pc> Reply-To: "dan.magenheimer@oracle.com" Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <20080715094609687.00000080236@djm-pc> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: "dan.magenheimer@oracle.com" , Keir Fraser , "Xen-Devel (E-mail)" Cc: Dave Winchell List-Id: xen-devel@lists.xenproject.org Hmmm... 18055 also fails to boot on my machine. Could we perhaps fall back to my original patch and do cleanup later/separately? I also want to try implementing an hpet64-based get_s_time() so will be working more in this code later... but want to get clocksource=3Dtsc working now with minimal code impact given the freeze. > -----Original Message----- > From: Dan Magenheimer [mailto:dan.magenheimer@oracle.com] > Sent: Tuesday, July 15, 2008 9:46 AM > To: 'Keir Fraser'; 'Xen-Devel (E-mail)' > Cc: 'Dave Winchell' > Subject: RE: [PATCH] clocksource=3Dtsc > = > > Actually in this mode of operation we hardly need a platform = > > timer *at all*. > > The idea is that we let the TSCs free-run, because we know = > > they will behave. > > Returning to 32-bit read_counter(), and having NULL = > read_counter when > > clocksource=3Dtsc would be another possibility... > = > That's essentially what the original tscstable.patch did, though > I was perhaps much uglier in the miscellaneous parts. > = > Thanks, > Dan >