Re: [Xen-devel] Why backend permanent?

To:	"Jae-Wan Jang" <jwjang@xxxxxxxxxxxxxxxxxx>
Subject:	Re: [Xen-devel] Why backend permanent?
From:	"pradeep singh rautela" <rautelap@xxxxxxxxx>
Date:	Thu, 31 May 2007 12:05:53 +0530
Cc:	xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date:	Wed, 30 May 2007 23:34:01 -0700
Dkim-signature:	a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=tg+ydOn/jPtJpX5oxaMW/Q39m59TlBJ2x300R54k4vmGjnJabB2YtR5OrFLbQSY1GgZJk8Iet8w5a+0UBk9Vji5RIXa+rzbNkQD8NV/lubQZnsr7IqB/2guCGneqiS+1H47+vJXvM2y8LM3zc4ZIr0keICmFARit0Auk6WAn8tI=
Domainkey-signature:	a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=MTtwOSFvXzszZbYehB5cDUWx/rT+kTgKiBCpdv0Z2enHgoGf7q5AnqBsL0B++irxs3CkviuUQeuuo3LT1jzRA2ahsCSBJ4RMN3p2kZheZXGt9vjoMzC5Ubwa+ZlBm6e73Q5j5JNiVDAe5AC07w9zyOWXkjFe/8OzQpGebH1EVNI=
Envelope-to:	www-data@xxxxxxxxxxxxxxxxxx
In-reply-to:	<465E5574.3040705@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>
References:	<465E5574.3040705@xxxxxxxxxxxxxxxxxx>
Sender:	xen-devel-bounces@xxxxxxxxxxxxxxxxxxx

On 5/31/07, Jae-Wan Jang <jwjang@xxxxxxxxxxxxxxxxxx> wrote:

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.


If they do not have a module_exit, this means they are supposed to be
compiled in the kernel statically and thus cannot be compiled a
modules.


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


I wonder if that is an obligation from a developer's point of view?
Did you try building a dummy backend module?
Does it spits some warnings or crashes Xen on insmod?

Thanks
--psr



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



--
---
pradeep singh rautela

"Genius is 1% inspiration, and 99% perspiration" - not me :)

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