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

Re: [Xen-devel] Why backend permanent?

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

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

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?


Sincerely yours,
Jae-Wan Jang


Jae-Wan Jang

Xen-devel mailing list

pradeep singh rautela

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

Xen-devel mailing list



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