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] Howto embed Network Driver from Linux source tree into x

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-devel] Howto embed Network Driver from Linux source tree into xen-hypervisor!
From: Mark Williamson <mark.williamson@xxxxxxxxxxxx>
Date: Mon, 13 Aug 2007 18:51:17 +0100
Cc: MT Rezaie <mmrezaie@xxxxxxxxx>
Delivery-date: Mon, 13 Aug 2007 10:52:08 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <939c1b470708130736t71c8f007h245e39c2fc436eaa@xxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <939c1b470708130736t71c8f007h245e39c2fc436eaa@xxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: KMail/1.9.6
> 1. For enabling to xen-hypervisors from different computers, to
> communicate from Ethernet (Without the help from other rings on top of
> it), I think I need integrate a network driver into xen itself. (IS
> THIS THE CORRECT SOLUTION?)

Xen used to have ethernet drivers built into the hypervisor itself in the 1.x 
series, but this got dropped since the Xen 2 release.  I'd have thought it'd 
be somewhat undesirable to try to put this back in there...  Especially since 
a load of the PCI code has moved to dom0 as well now.

What are you actually trying to achieve?  Are you sure you can't do this from 
dom0?  e.g. run a daemon in each dom0 communicating with Xen by hypercalls or 
ring buffers, and then use normal Linux networking?  I'd have thought that'd 
be a cleaner solution too.

Of course, what is best does rather depend on what you're trying to do ;-)

> 2. For that purpose I choosed to use e1000 driver from Linux's source
> tree. (CAN SOME ONE GET ME DIRECTIONS FOR DOING THIS!)

You could take a look at some of the older releases of Xen to see how PCI and 
network code used to be part of the hypervisor.  I'd recommend avoiding doing 
that though!

Cheers,
Mark

-- 
Dave: Just a question. What use is a unicyle with no seat?  And no pedals!
Mark: To answer a question with a question: What use is a skateboard?
Dave: Skateboards have wheels.
Mark: My wheel has a wheel!

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

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