Ray Bryant
2006-Aug-22 20:14 UTC
[Xen-devel] where oh where does the initial .config for dom0 come from?
Can someone tell me where the initial .config for the linux-2.6.16.13-xen tree comes from these days? It used to come from buildconfigs/linux-defconfig_xen_x86_64 for example, for my x86_64 builds. Reason I am asking, is that I typically enable profiling support in dom0, and by modifying the buildconfig file to include profiling, and then after doing a "make world", even for the first time in a freshly downloaded .hg tree, the resulting xen linux was profile enabled I and didn''t have to go in there and remake the darn thing just to get profiling enabled. This hack stopped working for me with CS 11134, but the previous changeset I was working on was 10650. -- Ray Bryant AMD Performance Labs Austin, Tx 512-602-0038 (o) 512-507-7807 (c) _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Horms
2006-Aug-23 03:14 UTC
[Xen-devel] Re: where oh where does the initial .config for dom0 come?from?
On Tue, 22 Aug 2006 15:14:29 -0500, Ray Bryant wrote:> Can someone tell me where the initial .config for the linux-2.6.16.13-xen > tree comes from these days? It used to come from > > buildconfigs/linux-defconfig_xen_x86_64I am pretty sure that is still the case, I tested it a few days ago on x86_32, x86_64 and ia64 and it seemed to work as before. One gotcha that I have noticed is that if linux-2.6.16.13-xen/ is already seeded, and buildconfigs/linux-defconfig_xen_ARCH is subsequently updated, the change does not seem to be picked up. Generally at that point I just deal with ref-linux-2.6.16.13/.config Though dealing with linux-2.6.16.13-xen/ is a daily battle. -- Horms H: http://www.vergenet.net/~horms/ W: http://www.valinux.co.jp/en/ _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel