From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755786AbZERFCb (ORCPT ); Mon, 18 May 2009 01:02:31 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751127AbZERFCW (ORCPT ); Mon, 18 May 2009 01:02:22 -0400 Received: from claw.goop.org ([74.207.240.146]:34698 "EHLO claw.goop.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750775AbZERFCW (ORCPT ); Mon, 18 May 2009 01:02:22 -0400 Message-ID: <4A10EBDD.7030304@goop.org> Date: Sun, 17 May 2009 22:02:21 -0700 From: Jeremy Fitzhardinge User-Agent: Thunderbird 2.0.0.21 (X11/20090320) MIME-Version: 1.0 To: Jesse Barnes CC: "Eric W. Biederman" , Ingo Molnar , the arch/x86 maintainers , Linux Kernel Mailing List , Xen-devel Subject: Re: [GIT PULL] xen /proc/mtrr implementation References: <1242170864-13560-1-git-send-email-jeremy@goop.org> <20090513133021.GA7277@elte.hu> <4A0ADBA2.2020300@goop.org> <20090515182757.GA19256@elte.hu> <4A0DCC11.10307@goop.org> <4A0DFF78.6000501@goop.org> <20090515202250.0f1218ef@jbarnes-g45> <20090516112233.5cb085c8@jbarnes-g45> In-Reply-To: <20090516112233.5cb085c8@jbarnes-g45> X-Enigmail-Version: 0.95.6 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Jesse Barnes wrote: > This is really about what software Xen wants to support though. You > can say, "it would be easier for you to just support new software that > doesn't use MTRRs," and you might be right, but supporting older stuff > doesn't appear that difficult, and it sounds like something they want > to do. > My rough target is that you should be able to take a pvops-dom0 kernel and use it to replace the 2.6.18-xen (or other patched up -xen) kernel on an existing server installation without having to replace very much (or anything) else. In practise that means making it work in something like RHEL 5 or SLES 10(?) environment. That seems to be what at least some of my testers are doing. Of course, most of the deployments will be with whatever new distro ships with the kernel. But that doesn't mean we can write-off the old stuff. (I think AKPM still tests current kernels on something like FC1 or 2 to check for general kernel/distro regressions.) J From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeremy Fitzhardinge Subject: Re: [GIT PULL] xen /proc/mtrr implementation Date: Sun, 17 May 2009 22:02:21 -0700 Message-ID: <4A10EBDD.7030304@goop.org> References: <1242170864-13560-1-git-send-email-jeremy@goop.org> <20090513133021.GA7277@elte.hu> <4A0ADBA2.2020300@goop.org> <20090515182757.GA19256@elte.hu> <4A0DCC11.10307@goop.org> <4A0DFF78.6000501@goop.org> <20090515202250.0f1218ef@jbarnes-g45> <20090516112233.5cb085c8@jbarnes-g45> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20090516112233.5cb085c8@jbarnes-g45> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Jesse Barnes Cc: Xen-devel , Ingo Molnar , the arch/x86 maintainers , "Eric W. Biederman" , Linux Kernel Mailing List List-Id: xen-devel@lists.xenproject.org Jesse Barnes wrote: > This is really about what software Xen wants to support though. You > can say, "it would be easier for you to just support new software that > doesn't use MTRRs," and you might be right, but supporting older stuff > doesn't appear that difficult, and it sounds like something they want > to do. > My rough target is that you should be able to take a pvops-dom0 kernel and use it to replace the 2.6.18-xen (or other patched up -xen) kernel on an existing server installation without having to replace very much (or anything) else. In practise that means making it work in something like RHEL 5 or SLES 10(?) environment. That seems to be what at least some of my testers are doing. Of course, most of the deployments will be with whatever new distro ships with the kernel. But that doesn't mean we can write-off the old stuff. (I think AKPM still tests current kernels on something like FC1 or 2 to check for general kernel/distro regressions.) J