This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-devel] Re: force PAE patch

To: Paul Larson <plars@xxxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] Re: force PAE patch
From: Ryan Harper <ryanh@xxxxxxxxxx>
Date: Wed, 13 Jul 2005 15:32:02 -0500
Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, keir@xxxxxxxxxxxxx, ryanh@xxxxxxxxxx
Delivery-date: Wed, 13 Jul 2005 20:30:48 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <1121283453.16631.44.camel@xxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <1121283453.16631.44.camel@xxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.6+20040907i
* Paul Larson <plars@xxxxxxxxxxxxxxxxxxxx> [2005-07-13 14:38]:
> Keir, I noticed your patch to force PAE on.  Things like this are very
> useful for testing config options that are off by default, but I'd like
> to see about putting a more generic method for doing this into Xen.
> Ryan and I had discussed this recently, and there are at least a few
> different scenarios I could see being useful.
> For specifying just a few individual config options.
> 2. make KCONFIG=/path/to/kernel/configfile
> This is useful if you have several different kernel configs that you
> want to reuse for different test runs.  A possible variation of this
> could be to specify DOM0_KCONFIG and DOMU_KCONFIG.

I have an patch that pushes the extraversion variable up to the top
level makefile.  This allows me to control which default config file is
used to populate the kernel source tree.

make KERNELS="xen0-smp xenU-smp" results in copying

sparse/arch/xen/configs/xen0-smp_defconfig_$(TARGET_ARCH) as .config in
the tree.

It also allows me to collapse buildconfigs/mklinux-2.6-{xen,xen0,xenU}
into a single file since they only differ by the extraversion field.

> Speaking for myself at least, this would be great to have and make
> testing of some of the non-default config options much easier.  Would
> anyone else find this useful?

I would like to see at least a way to specify a which config file to be
used ala some form of (2).  I think option (1) is very useful for
testing slightly different configurations or for quick tests when one
needs to do some debugging.

Ryan Harper
Software Engineer; Linux Technology Center
IBM Corp., Austin, Tx
(512) 838-9253   T/L: 678-9253

Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>