From: Paul Larson <plars@linuxtestproject.org>
To: keir@xensource.com
Cc: xen-devel <xen-devel@lists.xensource.com>, ryanh@us.ibm.com
Subject: force PAE patch
Date: Wed, 13 Jul 2005 14:37:33 -0500 [thread overview]
Message-ID: <1121283453.16631.44.camel@localhost.localdomain> (raw)
[-- 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
next reply other threads:[~2005-07-13 19:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-13 19:37 Paul Larson [this message]
2005-07-13 20:32 ` force PAE patch Ryan Harper
2005-07-13 20:59 ` Keir Fraser
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1121283453.16631.44.camel@localhost.localdomain \
--to=plars@linuxtestproject.org \
--cc=keir@xensource.com \
--cc=ryanh@us.ibm.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.