From mboxrd@z Thu Jan  1 00:00:00 1970
From: Keir Fraser <keir@xensource.com>
Subject: Re: [PATCH 7/10] linux 2.6.18: time handling
Date: Mon, 05 Mar 2007 15:03:22 +0000
Message-ID: <C211E1BA.A991%keir@xensource.com>
References: <45EC0A4C.76E4.0078.0@novell.com>
Mime-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <45EC0A4C.76E4.0078.0@novell.com>
List-Unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: Jan Beulich <jbeulich@novell.com>, xen-devel@lists.xensource.com
List-Id: xen-devel@lists.xenproject.org




On 5/3/07 11:17, "Jan Beulich" <jbeulich@novell.com> wrote:

> Remove struct timer_opts left-overs, add a Xen clocksource, and adjust
> conditionals for x86-64.
> 
> Signed-off-by: Jan Beulich <jbeulich@novell.com>

There doesn't seem to be much advantage to this (we're already very diverged
from native i386 time handling) and the disadvantages are a bigger diff
versus what we need for x86/64 (hence more ifdefs) and independent_wallclock
probably stops working.

This is all solvable I'm sure, particularly if clocksources are the way of
the future (e.g., is x86/64 native going to use generic_time any time soon)?

 -- Keir