Xen 
 
Home About Xen.org Xen Xen Summit Wiki Mailing List Bug Tracker Xen Downloads
 
   
 

xen-devel

[Xen-devel] Why backend permanent?

To: xen-devel@xxxxxxxxxxxxxxxxxxx, Jae-Wan Jang <jwjang@xxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] Why backend permanent?
From: Jae-Wan Jang <jwjang@xxxxxxxxxxxxxxxxxx>
Date: Thu, 31 May 2007 13:56:20 +0900
Delivery-date: Wed, 30 May 2007 21:54:02 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 2.0.0.0 (Windows/20070326)
Hello, friends

I wonder why netbk and all the backend device drivers are
permanent module.
I think they are modules but don't have module_exit function.

In this case, how can I debug or develop new backend device driver
without rebooting the whole system?


Sincerely yours,
Jae-Wan Jang

--

Jae-Wan Jang
jwjang@xxxxxxxxxxxxxxxxxx
+82-42-869-3559
http://camars.kaist.ac.kr/~jwjang


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

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