[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [Xen-devel] where oh where does the initial .config for dom0 comefrom?


  • To: "Ray Bryant" <raybry@xxxxxxxxxxxxxxxxx>, "xen-devel" <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: "Ian Pratt" <m+Ian.Pratt@xxxxxxxxxxxx>
  • Date: Tue, 22 Aug 2006 21:27:40 +0100
  • Delivery-date: Tue, 22 Aug 2006 13:28:02 -0700
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AcbGJ/89iAWK+DoZRJ60WGa2Vriy8QAATfaA
  • Thread-topic: [Xen-devel] where oh where does the initial .config for dom0 comefrom?

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

Is it picking up a default config from your dist/install/boot/
directory? This has been the behaviour for at least 2 years (though I
don't necessarily like it).

Ian

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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.