From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LiWYB-0002XS-HK for qemu-devel@nongnu.org; Sat, 14 Mar 2009 12:17:27 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LiWY7-0002XG-08 for qemu-devel@nongnu.org; Sat, 14 Mar 2009 12:17:26 -0400 Received: from [199.232.76.173] (port=46854 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LiWY6-0002XD-Pm for qemu-devel@nongnu.org; Sat, 14 Mar 2009 12:17:22 -0400 Received: from mail-fx0-f161.google.com ([209.85.220.161]:44107) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1LiWY6-0003sX-EL for qemu-devel@nongnu.org; Sat, 14 Mar 2009 12:17:22 -0400 Received: by fxm5 with SMTP id 5so550121fxm.34 for ; Sat, 14 Mar 2009 09:17:19 -0700 (PDT) MIME-Version: 1.0 Date: Sat, 14 Mar 2009 17:17:19 +0100 Message-ID: <68bb87b70903140917m7395453fwabda4ff1a5ed3b5a@mail.gmail.com> From: Patrizio Boschi Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] Help on effort estimation 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 Hi, I'm doing some academical research about the development of device emulators. So far I managed to create an emulator of a simple PCI device (Intel i6300ESB watchdog timer) just to get an idea of the development process in QEMU, and studied some of the other emulators in qemu/hw. I was also looking for some basic metrics (e.g. sloc, emulator sloc/driver sloc, function points) and models (e.g. cocomo II) to do some effort estimation (e.g. how many person-month to emulate a particular device model?). At this point, a little help from you would really benefit my studies and research. So... the questions are very simple :) - does someone have old or future development schedules for some of the qemu modules to share? - could someone (roughly) estimate the work-days needed to develop the emulator of a very simplce device (e.g. an hardware timer), an hard one (e.g. a VMEbus bridge with poor documentation), a mid one (e.g. an ethernet card), given an experienced programmer? - could someone (roughly) estimate which are the prerequisites to successfully develop a particular device emulator? (e.g. datasheet, real hardware, driver source code, vendor help, luck, girls, ...) - that's all but you can give hints if you want :) I'll obviously share all of my work once is finished. Thank you in advance, Patrizio