force PAE patch

force PAE patch

[Paul Larson]

[-- Attachment #1.1: Type: text/plain, Size: 963 bytes --]

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.

1. make CONFIG_SOMETHING=y CONFIG_SOMETHING_ELSE=y CONFIG_YET_ANOTHER=n
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.

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?
 
-- 
Thanks,
Paul Larson
plars@linuxtestproject.org
http://www.linuxtestproject.org

[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Re: force PAE patch

[Ryan Harper]

* Paul Larson <plars@linuxtestproject.org> [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.
> 
> 1. make CONFIG_SOMETHING=y CONFIG_SOMETHING_ELSE=y CONFIG_YET_ANOTHER=n
> 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
ryanh@us.ibm.com

Re: Re: force PAE patch

[Keir Fraser]

On 13 Jul 2005, at 21:32, Ryan Harper wrote:

>> 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.

Config.mk encapsulates some of those config options. For others, 
particularly ones specific to Xen itself, you could put a list in a 
file (e.g., export debug=y, export optimize=n, and so on) and then:
. <config-file> ; make

  -- Keir