From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Lphgb-0006bt-VB for qemu-devel@nongnu.org; Fri, 03 Apr 2009 07:35:50 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LphgW-0006bB-Q2 for qemu-devel@nongnu.org; Fri, 03 Apr 2009 07:35:49 -0400 Received: from [199.232.76.173] (port=48952 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LphgW-0006b6-JT for qemu-devel@nongnu.org; Fri, 03 Apr 2009 07:35:44 -0400 Received: from mx20.gnu.org ([199.232.41.8]:51018) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1LphgV-0006sA-Q2 for qemu-devel@nongnu.org; Fri, 03 Apr 2009 07:35:44 -0400 Received: from mail.codesourcery.com ([65.74.133.4]) by mx20.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1LphgU-0002E5-Ks for qemu-devel@nongnu.org; Fri, 03 Apr 2009 07:35:42 -0400 From: Paul Brook Subject: Re: [Qemu-devel] [RFC] Introduce module API to QEMU Date: Fri, 3 Apr 2009 11:35:32 +0000 References: <1238724755-15929-1-git-send-email-aliguori@us.ibm.com> In-Reply-To: <1238724755-15929-1-git-send-email-aliguori@us.ibm.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200904031235.33157.paul@codesourcery.com> Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Cc: Anthony Liguori > This patch introduces a module API similar to what's in the Linux kernel. > This includes module_init/module_exit functions that register functions > that are run at init and exit respectively. Wouldn't it be much simpler to just have a list of device names, and assume the each device is implemented in $devicename., and provides $devicename_register ? It's then an extremely simple shell script to collate and call these. Paul