[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <49AB1C7D.2040605@goop.org>
Date: Sun, 01 Mar 2009 15:38:37 -0800
From: Jeremy Fitzhardinge <jeremy@...p.org>
To: Andi Kleen <andi@...stfloor.org>
CC: Jody Belka <lists-xen@...b.org>,
Nick Piggin <nickpiggin@...oo.com.au>,
Xen-devel <xen-devel@...ts.xensource.com>,
the arch/x86 maintainers <x86@...nel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
"H. Peter Anvin" <hpa@...or.com>,
Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCH] xen: core dom0 support
Andi Kleen wrote:
> Jody Belka <lists-xen@...b.org> writes:
>
>> Is it duplication though? I personally have machines with older processors
>> that don't have hvm support. I plan on keeping these around for a good amount
>> of time, and would love to be running them on mainline. So for me, unless KVM
>> is somehow going to support para-virtualisation, this isn't duplication.
>>
>
> The old systems will continue to run fine with a 2.6.18 Dom0 though.
But that suggests the *only* reason to update kernels is to get new
hardware support. Or conversely, we should stop trying to be backwards
compatible with old hardware in new kernels because there's no reason to
keep it.
While a lot of the delta between 2.6.18 has been hardware support
updates, there have been a lot of other useful things: a new CPU
scheduler, tickless operation (which directly important for
virtualization), all the cgroups stuff, new filesystems, IO schedulers,
etc, etc. All good things to have, even on older hardware.
J
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists