qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Darryl Dixon <esrever_otua@pythonhacker.is-a-geek.net>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] kqemu and KQemu
Date: Mon, 07 Mar 2005 08:27:06 +1300	[thread overview]
Message-ID: <1110137227.19500.2.camel@localhost.localdomain> (raw)
In-Reply-To: <20050306175658.GA21956@jbrown.mylinuxbox.org>

[-- Attachment #1: Type: text/plain, Size: 622 bytes --]

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?
>

[-- Attachment #2: Type: text/html, Size: 1053 bytes --]

      parent reply	other threads:[~2005-03-06 19:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-06 17:56 [Qemu-devel] kqemu and KQemu Jim C. Brown
2005-03-06 19:03 ` Pascal Terjan
2005-03-06 19:27 ` Darryl Dixon [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1110137227.19500.2.camel@localhost.localdomain \
    --to=esrever_otua@pythonhacker.is-a-geek.net \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).