automation: build some customised configs
PATCH 1/1 automation: build some customised configs
Introduce a new directory to put in configs we care about. Modify build script to build with those configs.
While we only introduce x86 configs initially, provision for non-x86 configs.
---
Cc: Jan Beulich <[email protected]>
Jan, feel free to put configs here.
--- automation/configs/x86/hvm_only_config | 2 ++ automation/configs/x86/no_hvm_pv_config | 2 ++ automation/configs/x86/pv_only_config | 2 ++ automation/scripts/build | 15 +++++++++++++++ 4 files changed, 21 insertions(+) create mode 100644 automation/configs/x86/hvm_only_config create mode 100644 automation/configs/x86/no_hvm_pv_config create mode 100644 automation/configs/x86/pv_only_config
automation/configs/x86/hvm_only_config new file +2 -0
@@ -0,0 +1,2 @@ +CONFIG_HVM=y +# CONFIG_PV is not set
automation/configs/x86/no_hvm_pv_config new file +2 -0
@@ -0,0 +1,2 @@ +# CONFIG_HVM is not set +# CONFIG_PV is not set
automation/configs/x86/pv_only_config new file +2 -0
@@ -0,0 +1,2 @@ +CONFIG_PV=y +# CONFIG_HVM is not set
automation/scripts/build +15 -0
@@ -31,3 +31,18 @@ fi ./configure "${cfgargs[@]}" make -j$(nproc) dist + +# Build all the configs we care about +case ${XEN_TARGET_ARCH} in + x86_64) arch=x86 ;; + *) exit 0 ;; +esac + +cfg_dir="automation/configs/${arch}" +for cfg in `ls ${cfg_dir}`; do + echo "Building $cfg" + rm -f xen/.config + make -C xen KBUILD_DEFCONFIG=../../../../${cfg_dir}/${cfg} XEN_CONFIG_EXPERT=y defconfig + make -j$(nproc) -C xen XEN_CONFIG_EXPERT=y +done +
Signature · 7 lines
2.11.0 _______________________________________________ Xen-devel mailing list [email protected] https://lists.xenproject.org/mailman/listinfo/xen-devel
Quoted 8 lines
Quoted 1 line
Quoted 1 line · On 02.11.18 at 20:33, <[email protected]> wrote:
Introduce a new directory to put in configs we care about. Modify build script to build with those configs.
While we only introduce x86 configs initially, provision for non-x86 configs.
Signed-off-by Wei Liu <[email protected]>
Quoted 1 line
Jan, feel free to put configs here.
Are you referring to some part of a prior discussion we've had, and that I forgot about in the meantime? I don't recall having pointed out specific configs we'd want to routinely test (albeit I certainly can think of some).
Jan
_______________________________________________
Xen-devel mailing list
[email protected]
https://lists.xenproject.org/mailman/listinfo/xen-devel
Quoted 9 lines · Jan Beulich
Quoted 8 lines
Quoted 1 line
Quoted 1 line · On 02.11.18 at 20:33, <[email protected]> wrote:
Introduce a new directory to put in configs we care about. Modify build script to build with those configs.
While we only introduce x86 configs initially, provision for non-x86 configs.
Signed-off-by Wei Liu <[email protected]>
Quoted 8 lines
Acked-by Jan Beulich <[email protected]>Quoted 1 line
Jan, feel free to put configs here.
Are you referring to some part of a prior discussion we've had, and that I forgot about in the meantime? I don't recall having pointed out specific configs we'd want to routinely test (albeit I certainly can think of some).
In one of the mails to my previous version, you said:
"We don't have no-shadow and bigmem defconfigs, yet I think we (should) care about not breaking those builds (I routinely check them every once in a while)."
Once this patch is merged, you can add whatever configs you care about to this directory and they will be built by Gitlab CI constantly.
Wei.
_______________________________________________
Xen-devel mailing list
[email protected]
https://lists.xenproject.org/mailman/listinfo/xen-devel
Quoted 71 lines · Wei Liu
Introduce a new directory to put in configs we care about. Modify build script to build with those configs.
While we only introduce x86 configs initially, provision for non-x86 configs.
Signed-off-by Wei Liu <[email protected]>---
Cc: Jan Beulich <[email protected]>Jan, feel free to put configs here.
--- automation/configs/x86/hvm_only_config | 2 ++ automation/configs/x86/no_hvm_pv_config | 2 ++ automation/configs/x86/pv_only_config | 2 ++ automation/scripts/build | 15 +++++++++++++++ 4 files changed, 21 insertions(+) create mode 100644 automation/configs/x86/hvm_only_config create mode 100644 automation/configs/x86/no_hvm_pv_config create mode 100644 automation/configs/x86/pv_only_configautomation/configs/x86/hvm_only_config new file +2
-0@@ -0,0 +1,2 @@ +CONFIG_HVM=y +# CONFIG_PV is not setautomation/configs/x86/no_hvm_pv_config new file +2
-0@@ -0,0 +1,2 @@ +# CONFIG_HVM is not set +# CONFIG_PV is not setautomation/configs/x86/pv_only_config new file +2
-0@@ -0,0 +1,2 @@ +CONFIG_PV=y +# CONFIG_HVM is not setautomation/scripts/build +15
-0@@ -31,3 +31,18 @@ fi ./configure "${cfgargs[@]}" make -j$(nproc) dist + +# Build all the configs we care about +case ${XEN_TARGET_ARCH} in + x86_64) arch=x86 ;; + *) exit 0 ;; +esac + +cfg_dir="automation/configs/${arch}" +for cfg in `ls ${cfg_dir}`; do + echo "Building $cfg" + rm -f xen/.config + make -C xen KBUILD_DEFCONFIG=../../../../${cfg_dir}/${cfg} XEN_CONFIG_EXPERT=y defconfig + make -j$(nproc) -C xen XEN_CONFIG_EXPERT=y +done +Signature · 1 line
2.11.0
Seems very reasonable to me.
_______________________________________________
Xen-devel mailing list
[email protected]
https://lists.xenproject.org/mailman/listinfo/xen-devel