Hi Dan,
Thanks for your support. I have booted Xen0 successfully according to
Akio's Knowhow, but it needs to compile Xen0 twice and need to run make
menuconfig manually every time .So this is not the best solution to solve this
issue. Lastly,I adopted your suggestion to make the generic one for tiger and
ZX. Comparing xen0_defconfig_ia64 in xen-unstable with our
xen0_defconfig_tiger, I found only several items not included in
xen0_defconfig_ia64. Hence, I added them by "make menuconfig". Currently, we
can boot Xen0 with this candidate generic one. We haven't ZX box, so can you
help me to validate it on ZX box? Thanks. If it is OK with ZX Box, we can use
this one as generic configuration file for all IA64 machine.
Best wishes!
Thanks
Zhang Xiantao
CSD-OTC PRC Virtualization
Intel (China) Limited
-----Original Message-----
From: Magenheimer, Dan (HP Labs Fort Collins) [mailto:dan.magenheimer@xxxxxx]
Sent: 2005年12月19日 23:56
To: Tian, Kevin; Zhang, Xiantao; xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
Subject: RE: [Xen-ia64-devel] RE: [PATCH]Allow different config file
forxenlinux on same arch
I support the patch but I think it should be accepted
and committed by someone in Cambridge or Xensource because
it affects important common (and Xen/x86) build files.
Try resubmitting it to xen-devel.
However, I think the best answer is to figure out what's
wrong in the generic config file and fix that.
> -----Original Message-----
> From: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx
> [mailto:xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf
> Of Tian, Kevin
> Sent: Monday, December 19, 2005 2:10 AM
> To: Zhang, Xiantao; xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
> Subject: [Xen-ia64-devel] RE: [PATCH]Allow different config
> file forxenlinux on same arch
>
> Hi, Dan,
> Any comments upon this thread? We also posted the patch
> to xen mailing list earlier, since it changes common part.
> Previously the generic one was once checked in, but then
> reversed back to ZX specific one. However customer is waiting
> for specific configuration file to run on tiger box. So below
> is another way to achieve it. If you agree with this
> alternative, please help push it since it's a key step to let
> XEN/IA64 deployed and experienced more widely. ;-)
>
> Thanks,
> Kevin
>
> >-----Original Message-----
> >From: Zhang, Xiantao
> >Sent: 2005年12月19日 9:50
> >To: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
> >Cc: Tian, Kevin
> >Subject: [PATCH]Allow different config file for xenlinux on same arch
> >
> >Currently there is no generic configure file to compile
> xenlinux on ia64, since there're
> >several different system types like HP-ZX, DIG, etc. Current
> Makefile can't meet this
> >need and default one (xen0_defconfig_ia64) is only for HP-ZX
> type. Hence, this
> >patch can append an additional param to configuration file
> name to differentiate
> >system types when make.
> >
> >For example, we can use "make world XEN_SYSTYPE=dig" to
> compile, and if a
> >config file named as xen0_defconfig_ia64dig exists under
> arch/xen/configs, it will be
> >copied to override xen0_defconfig_ia64 before real
> compilation.. If no value for this
> >option, it use default configure file for their archs.
> >
> >Configuration file is not attached here. If this approach is
> an agreed approach to
> >solve such requirement, we will check in the config file in
> another mail.
> >
> >Signed-off-by Zhang Xiantao <xiantao.zhang@xxxxxxxxx>
> >Signed-off-by Tian Kevin <kevin.tian@xxxxxxxxx>
> >
> >diff -r 0255f48b757f Makefile
> >--- a/Makefile Sun Dec 4 19:12:00 2005
> >+++ b/Makefile Wed Dec 14 17:35:04 2005
> >@@ -10,7 +10,7 @@
> > # Export target architecture overrides to Xen and Linux sub-trees.
> > ifneq ($(XEN_TARGET_ARCH),)
> > SUBARCH := $(subst x86_32,i386,$(XEN_TARGET_ARCH))
> >-export XEN_TARGET_ARCH SUBARCH
> >+export XEN_TARGET_ARCH SUBARCH XEN_SYSTYPE
> > endif
> >
> > # Default target must appear before any include lines
> >diff -r 0255f48b757f buildconfigs/mk.linux-2.6-xen
> >--- a/buildconfigs/mk.linux-2.6-xen Sun Dec 4 19:12:00 2005
> >+++ b/buildconfigs/mk.linux-2.6-xen Wed Dec 14 17:35:04 2005
> >@@ -30,7 +30,7 @@
> > CONFIG_VERSION=$$(sed -ne 's/^EXTRAVERSION = //p'
> >$(LINUX_DIR)/Makefile); \
> > [ -r
> >$(DESTDIR)/boot/config-$(LINUX_VER)$$CONFIG_VERSION-$(EXTRAVERSION)
> > ] && \
> > cp
> >$(DESTDIR)/boot/config-$(LINUX_VER)$$CONFIG_VERSION-$(EXTRAVERSION)
> >$(LINUX_DIR)/.config \
> >- || cp
> >$(LINUX_DIR)/arch/xen/configs/$(EXTRAVERSION)_defconfig_$(XEN
> _TARGET_A
> >RCH) \
> >+ || cp
> >$(LINUX_DIR)/arch/xen/configs/$(EXTRAVERSION)_defconfig_$(XEN
> _TARGET_A
> >RCH)$(XEN_SYSTYPE) \
> > $(LINUX_DIR)/.config
> > # See if we need to munge config to enable PAE
> > $(MAKE) CONFIG_FILE=$(LINUX_DIR)/.config -f
> buildconfigs/Rules.mk
> >config-update-pae
> >
> >Zhang Xiantao
> >CSD-OTC PRC Virtualization
> >Intel (China) Limited
>
>
> _______________________________________________
> Xen-ia64-devel mailing list
> Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-ia64-devel
>
xen0_defconfig_ia64.new
Description: xen0_defconfig_ia64.new
_______________________________________________
Xen-ia64-devel mailing list
Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-ia64-devel
|
Home