From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Philippe Berthault" Subject: A reorganization of Xen sources is necessary before integrating Xen into Linux. Date: Mon, 21 Feb 2005 17:14:10 +0100 Message-ID: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0000_01C51838.C23F7120" Sender: xen-devel-admin@lists.sourceforge.net Errors-To: xen-devel-admin@lists.sourceforge.net List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , List-Archive: To: Xen-Devel List-Id: xen-devel@lists.xenproject.org This is a multi-part message in MIME format. ------=_NextPart_000_0000_01C51838.C23F7120 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="iso-8859-1" I have searched assembly code in Xen sources (xen-unstable) and I'm very surprised because the assembly code isn't located in 'arch' directories. I have found assembly code in the following directories: - extras/mini-os - linux-2.6.10-xen-sparse/drivers/xen/privcmd - tools/blktap - tools/ioemu/iodev - tools/libxc - tools/python/xen/lowlevel/xu - tools/x2d2 - tools/xcs All these assembly code seems to be specific to IA32. So porting Xen to a new architecture (such as IA64) will be acrobatic ! Is there a plan to reorganize source code into a better and cleanest architecture ? I thinks this would be mandatory before integrating Xen into Linux. PhB ------=_NextPart_000_0000_01C51838.C23F7120 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset="iso-8859-1"

I have = searched=20 assembly code in Xen sources (xen-unstable)

and = I'm very=20 surprised because the assembly code isn't located

in = 'arch'=20 directories.

I have = found=20 assembly code in the following directories:

= -=20 extras/mini-os

= -=20 linux-2.6.10-xen-sparse/drivers/xen/privcmd

= -=20 tools/blktap

= -=20 tools/ioemu/iodev

= -=20 tools/libxc

= -=20 tools/python/xen/lowlevel/xu

= -=20 tools/x2d2

= -=20 tools/xcs

All = these assembly=20 code seems to be specific to IA32.

So = porting Xen to a=20 new architecture (such as IA64) will be acrobatic !

Is = there a plan to=20 reorganize source code into a better and cleanest

architecture=20 ?

I = thinks this would=20 be mandatory before integrating Xen into Linux.

PhB

------=_NextPart_000_0000_01C51838.C23F7120-- ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keir Fraser Subject: Re: A reorganization of Xen sources is necessary before integrating Xen into Linux. Date: Mon, 21 Feb 2005 16:57:28 +0000 Message-ID: References: Mime-Version: 1.0 (Apple Message framework v619.2) Content-Type: multipart/alternative; boundary=Apple-Mail-1--298653588 In-Reply-To: Sender: xen-devel-admin@lists.sourceforge.net Errors-To: xen-devel-admin@lists.sourceforge.net List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , List-Archive: To: Philippe Berthault Cc: Xen-Devel List-Id: xen-devel@lists.xenproject.org --Apple-Mail-1--298653588 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; format=flowed On 21 Feb 2005, at 16:14, Philippe Berthault wrote: > I have searched assembly code in Xen sources (xen-unstable) > and I'm very surprised because the assembly code isn't located > in 'arch' directories. Clean-up work is ongoing -- you'll notice that Xen itself contains no assembly code, or other arch-specific routines, outside the arch subdirectories. The particular XenLinux file you point out is our one rather arch-specific driver -- that one is likely to get moved to arch/xen/i386 at some point. There is some work to be done on the tools: no architecture apart from x86 currently uses them. > Is there a plan to reorganize source code into a better and cleanest > architecture ? > I thinks this would be mandatory before integrating Xen into Linux. Xen and XenLinux are already clean (apart from that one driver file), so this is not a barrier to getting our Linux changes integrated into the mainline repository. -- Keir --Apple-Mail-1--298653588 Content-Transfer-Encoding: 7bit Content-Type: text/enriched; charset=US-ASCII On 21 Feb 2005, at 16:14, Philippe Berthault wrote: ArialI have searched assembly code in Xen sources (xen-unstable) Arialand I'm very surprised because the assembly code isn't located Arialin 'arch' directories. Clean-up work is ongoing -- you'll notice that Xen itself contains no assembly code, or other arch-specific routines, outside the arch subdirectories. The particular XenLinux file you point out is our one rather arch-specific driver -- that one is likely to get moved to arch/xen/i386 at some point. There is some work to be done on the tools: no architecture apart from x86 currently uses them. ArialIs there a plan to reorganize source code into a better and cleanest Arialarchitecture ? ArialI thinks this would be mandatory before integrating Xen into Linux. Xen and XenLinux are already clean (apart from that one driver file), so this is not a barrier to getting our Linux changes integrated into the mainline repository. -- Keir --Apple-Mail-1--298653588-- ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click From mboxrd@z Thu Jan 1 00:00:00 1970 From: Arun Sharma Subject: Re: A reorganization of Xen sources is necessary before integrating Xen into Linux. Date: Wed, 23 Feb 2005 15:33:54 -0800 Message-ID: <421D12E2.7040407@intel.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit In-Reply-To: Sender: xen-devel-admin@lists.sourceforge.net Errors-To: xen-devel-admin@lists.sourceforge.net List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , List-Archive: To: Philippe Berthault Cc: xen-devel@lists.sourceforge.net, aliguori@us.ibm.com List-Id: xen-devel@lists.xenproject.org On 2/21/2005 8:14 AM, Philippe Berthault wrote: > I have searched assembly code in Xen sources (xen-unstable) > and I'm very surprised because the assembly code isn't located > in 'arch' directories. > > [..] > - tools/ioemu/iodev Yes, that one is my fault. The main issue is that we don't have a common place to put arch specific definitions accessible from user space. This came up in the other thread related to rmb/wmb as well. If we agree that: or is the right thing to do, I'll be happy to submit patches. -Arun ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click