WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] xen intro q

To: Chris Mason <mason@xxxxxxxx>
Subject: Re: [Xen-devel] xen intro q
From: Ian Pratt <Ian.Pratt@xxxxxxxxxxxx>
Date: Mon, 17 Nov 2003 23:01:32 +0000
Cc: Bin Ren <br260@xxxxxxxxx>, Devel Xen <xen-devel@xxxxxxxxxxxxxxxxxxxxx>, Ian.Pratt@xxxxxxxxxxxx
Delivery-date: Mon, 17 Nov 2003 23:02:26 +0000
Envelope-to: steven.hand@xxxxxxxxxxxx
In-reply-to: Your message of "Mon, 17 Nov 2003 15:50:30 EST." <1069102230.15864.34.camel@xxxxxxxxxxxxx>
List-archive: <http://sourceforge.net/mailarchive/forum.php?forum=xen-devel>
List-help: <mailto:xen-devel-request@lists.sourceforge.net?subject=help>
List-id: List for Xen developers <xen-devel.lists.sourceforge.net>
List-post: <mailto:xen-devel@lists.sourceforge.net>
List-subscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=subscribe>
List-unsubscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=unsubscribe>
Sender: xen-devel-admin@xxxxxxxxxxxxxxxxxxxxx
> On Mon, 2003-11-17 at 15:38, Bin Ren wrote:
> 
> > 
> > It's relevant to say that Xen re-uses some Linux kernel source codes,
> > and chooses a similar directory structure, Xen authors gain much
> > knowledge and inspiration from Linux kernel.
> > 
> > The similarity ends here.
> 
> Fair enough, I suppose a better question is how do you plan on
> maintaining support for all the new hardware (even ia32 only)over time? 
> If I had the goal of porting xen to amd64, I'd much rather port a xen
> patch onto the linux kernel than fork the kernel, stuff in the xen
> infrastructure and then maintain my fork for all eternity ;-)

Chris,

As regards maintaining support for new hardware there are two
areas to consider: hardware device drivers and cpu variant
support.

Our plan for the former is to provide source-level compatibility
with Linux device drivers. We're already pretty close to this for
network drivers, but we still have some work to do for SCSI and
other drivers. (this is on our todo list)

As regards CPU variants, these don't occur too frequently.
Looking at the Intel x86 line, the most frequent thing that needs
updating is IOAPIC support. Since Xen's start of day code is very
similar to Linux's, we're able to import these changes pretty
easily. Major changes to the CPU like PAE36 or x86_64 have a
significant impact on Xen, and there's not really much Linux code
we could borrow to help us here, as its rather different. [BTW:
We do have plans (and a design) for x86_64 support, but PAE36
isn't currently high on our agenda right now.]

Apart from the start of day code and device drivers, Xen really
doesn't have much in common with Linux. I think trying to merge
the two would get ugly very quickly.

Xen is really quite small compared to an OS, and I think it's
best to think of Xen as a 'next-generation BIOS replacement' ---
OS neutral, and an opportunity to sort out the current PC device
driver mess, to everyone's benefit. 


Best,
Ian


-------------------------------------------------------
This SF. Net email is sponsored by: GoToMyPC
GoToMyPC is the fast, easy and secure way to access your computer from
any Web browser or wireless device. Click here to Try it Free!
https://www.gotomypc.com/tr/OSDN/AW/Q4_2003/t/g22lp?Target=mm/g22lp.tmpl
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel

<Prev in Thread] Current Thread [Next in Thread>