[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] Why backend permanent?

To: xen-devel@xxxxxxxxxxxxxxxxxxx, Jae-Wan Jang <jwjang@xxxxxxxxxxxxxxxxxx>
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
List-id: Xen developer discussion <xen-devel.lists.xensource.com>

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

Follow-Ups:
- Re: [Xen-devel] Why backend permanent?
  - From: pradeep singh rautela

Prev by Date: RE: [Xen-devel] [Patch] Add VMX memory-mapped Local APIC access optimization
Next by Date: RE: [Xen-devel] X11_EnterFullScreen fails
Previous by thread: [Xen-tools] [PATCH] Fix stale email addresses in xenstat and xentop.
Next by thread: Re: [Xen-devel] Why backend permanent?
Index(es):
- Date
- Thread

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.