From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: Backwards compat for < 2.6.16? Date: Tue, 02 Oct 2007 10:37:20 +0200 Message-ID: <47020340.60206@qumranet.com> References: <1191311951.17826.11.camel@localhost.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: kvm-devel To: Rusty Russell Return-path: In-Reply-To: <1191311951.17826.11.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: kvm-devel-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org Errors-To: kvm-devel-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org List-Id: kvm.vger.kernel.org Rusty Russell wrote: > Hi all, > > The lapic code uses ktime_t and hrtimers, which means we no longer > build for kernels 2.6.15 and below. Is it worth trying to fake this > infrastructure up, building without lapic, or abandoning < 2.6.16? > > I think we can stub the code away, and hack the feature reporting to hide the crippled functionality. -- error compiling committee.c: too many arguments to function ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/