Xen 2.0 VMM patches
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 1 line · Ian Pratt
arch-xen : large patch to add
arch/xenandinclude/asm-xen
This is 32bit only right? Do you plan a 64bit guest too? If yes, you would end up with two arch-xens in the end.
Also are the differences to the native architecture really that big that a separate architecture makes sense? It's a lot of long term work to maintain a Linux architecture.
-Andi
Quoted 6 lines
Quoted 1 line · Ian Pratt
arch-xen : large patch to add
arch/xenandinclude/asm-xenThis is 32bit only right? Do you plan a 64bit guest too? If yes, you would end up with two arch-xens in the end.
We have an x86_64 guest port in progress, hence the current directory structure below arch/xen. There's a fair bit of arch/xen-specific code that we can share between the ports.
Quoted 3 lines
Also are the differences to the native architecture really that big that a separate architecture makes sense? It's a lot of long term work to maintain a Linux architecture.
We've experimented with doing thing the other way round, having xen a sub architecture of i386, but it was _really_ messy.
I firmly believe that having a separate arch/xen is the best approach for the moment. In the future, it might make sense to merge arch xen into i386, but to do this cleanly would require significant restructuring of i386. I think that's something we could move toward after everyone's gotten comfortable with having arch xen in the tree.
The fact that arch xen is self contained actually makes it easier for us to maintain in some respects. We've been tracking 2.6 releases for some time without too much difficulty.
Best,
Ian
Quoted 3 lines · Ian Pratt
The fact that arch xen is self contained actually makes it easier for us to maintain in some respects. We've been tracking 2.6 releases for some time without too much difficulty.
2.6 has been relatively easy for now (because it was supposed to be a "stable kernel"), but I suspect it'll get worse again over time. e.g. in 2.5 it was really bad for long times.
Essentially you will need to commit significant man power to this.
Also it's quite hard to always catch all the changes that get done to i386.
Overall I think it's a bad idea to have four different x86 like architectures in the tree. Especially since there will be likely more hypervisors over time. i386 and x86-64 make some sense because 64bit is a natural boundary, but extending it elsewhere doesn't scale very well.
-Andi
Andi> Overall I think it's a bad idea to have four different x86 Andi> like architectures in the tree. Especially since there will Andi> be likely more hypervisors over time. i386 and x86-64 make Andi> some sense because 64bit is a natural boundary, but Andi> extending it elsewhere doesn't scale very well.
Is there any possibility of Xen someday being ported to some non-x86 architecture (eg ppc64 or ia64)?
- Roland
Quoted 8 lines
Andi> Overall I think it's a bad idea to have four different x86 Andi> like architectures in the tree. Especially since there will Andi> be likely more hypervisors over time. i386 and x86-64 make Andi> some sense because 64bit is a natural boundary, but Andi> extending it elsewhere doesn't scale very well.
Is there any possibility of Xen someday being ported to some non-x86 architecture (eg ppc64 or ia64)?
Non x86 architectures are generally much easier to virtualise, so its possible to do it within the existing architecture port.
As a case in point, the soon-to-be-released IA64 port of Linux just requires just a few patches to the standard architecture. I expect PPC will be fairly similar.
x86 and x86_64 are a real pain, hence the separate architecture approach.
Over time, I hope we can merge the i386 xen port in with the native architecture, but its going to require significant restructuring of the native architecture to do it cleanly. In the meantime, I think we just have to bite the bullet and maintain a separate architecture. I believe we have resources to do this.
Ian