From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1D81jO-0000xJ-Kp for qemu-devel@nongnu.org; Sun, 06 Mar 2005 14:48:02 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1D81jE-0000qt-MM for qemu-devel@nongnu.org; Sun, 06 Mar 2005 14:47:54 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1D81jD-0000qU-EQ for qemu-devel@nongnu.org; Sun, 06 Mar 2005 14:47:51 -0500 Received: from [65.19.178.186] (helo=pythonhacker.is-a-geek.net) by monty-python.gnu.org with esmtp (Exim 4.34) id 1D81PY-0001g8-Ko for qemu-devel@nongnu.org; Sun, 06 Mar 2005 14:27:33 -0500 Received: from localhost (localhost.localdomain [127.0.0.1]) by pythonhacker.is-a-geek.net (Postfix) with ESMTP id D2320403D4 for ; Sun, 6 Mar 2005 14:27:30 -0500 (EST) Received: from pythonhacker.is-a-geek.net ([127.0.0.1]) by localhost (pythonhacker.is-a-geek.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 06847-03 for ; Sun, 6 Mar 2005 14:27:10 -0500 (EST) Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by pythonhacker.is-a-geek.net (Postfix) with ESMTP id 618DA403CF for ; Sun, 6 Mar 2005 14:27:08 -0500 (EST) Subject: Re: [Qemu-devel] kqemu and KQemu From: Darryl Dixon In-Reply-To: <20050306175658.GA21956@jbrown.mylinuxbox.org> References: <20050306175658.GA21956@jbrown.mylinuxbox.org> Content-Type: multipart/alternative; boundary="=-jdPRreriCK0+97fTuunI" Date: Mon, 07 Mar 2005 08:27:06 +1300 Message-Id: <1110137227.19500.2.camel@localhost.localdomain> Mime-Version: 1.0 Reply-To: esrever_otua@pythonhacker.is-a-geek.net, 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 --=-jdPRreriCK0+97fTuunI Content-Type: text/plain Content-Transfer-Encoding: 7bit I was thinking about this too. In the (unlikely??) event that, say PPC on PPC gets accelerated, or x86-64 on x86-64 (or even x86-on-windows), we will want other names for the accelerators for these. Perhaps something descriptive like qemu-x86-accel or qemu-ppc-accel... Cheers, D On Sun, 2005-03-06 at 12:56 -0500, Jim C. Brown wrote: >I am wondering why the accelerator module is named kqemu. I know it >probably means "Kernel QEMU" but there is a KDE frontend for qemu called >KQEMU at kqemu.sf.net, and it looks like KQEMU (the gui) had the name first. > >So why give the accelerator module a conflicting name? > --=-jdPRreriCK0+97fTuunI Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 7bit I was thinking about this too. In the (unlikely??) event that, say PPC on PPC gets accelerated, or x86-64 on x86-64 (or even x86-on-windows), we will want other names for the accelerators for these. Perhaps something descriptive like qemu-x86-accel or qemu-ppc-accel...

Cheers,
D

On Sun, 2005-03-06 at 12:56 -0500, Jim C. Brown wrote:

I am wondering why the accelerator module is named kqemu. I know it
probably means "Kernel QEMU" but there is a KDE frontend for qemu called
KQEMU at kqemu.sf.net, and it looks like KQEMU (the gui) had the name first.

So why give the accelerator module a conflicting name?

--=-jdPRreriCK0+97fTuunI--