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

[Xen-devel] The differences between two patch methods in Xen?


  • To: xen-devel@xxxxxxxxxxxxxxxxxxx
  • From: Zongyun Lai <zlai.zju@xxxxxxxxx>
  • Date: Sat, 7 Apr 2007 14:45:32 +0800
  • Delivery-date: Sat, 07 Apr 2007 00:04:08 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:from:organization:to:subject:date:user-agent:mime-version:content-type:content-transfer-encoding:content-disposition:message-id; b=nNsYOzJBDMRxoIQJY0i+ktJEU2BgUgcSBcDlvc1Yzs8O7UasyQba2v4uodM2I/ccoVQZemIguSsK11CYG9kJlTJba87GhymsjvsE+nE5cGJD0HLP7rBehZBEKEwhhw1Osna+kh18HzjXBb5wtxit3BJhwY1vfWTFedNqUTlZz0g=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

Hi all, 
    I am new to Xen. I have gone through the source code directory of 
xen-unstable, and have kept a log of all the compiling procedure. I noticed 
that 'make dist-kernels' command will apply patches 
from 'patches/linux-2.6.18/' to the vanilla kernel. And after that, the 
command will apply the the so-call 'arch-xen patches' 
in 'linux-2.6-xen-sparse' directory to the patched kernel by 
running ./mkbuildtree command. I found that this procedure is actually 
not 'patching', but just overwrite some .c, .h, Kconfig and Makefile in 
the 'linux-2.6.18-xen' by symbolic links to the 'linux-2.6-xen-sparse' 
directory. 
   So, my question is what is the differences between the two patch 
mechanisms, one in the 'patches' directory, and the other in 
the 'linux-2.6-xen-sparse' directory? That is to say, what is the reason to 
keep them separate instead of keeping them in a common patch pool? 

Cheers, 
          Zongyun


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