qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Carlo Marcelo Arenas Belon <carenas@sajinet.com.pe>
To: Glauber Costa <glommer@gmail.com>
Cc: Chris Wright <chrisw@redhat.com>,
	kvm@vger.kernel.org, Jes Sorensen <jes@sgi.com>,
	qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: QEMU Accel - git tree
Date: Fri, 4 Jul 2008 16:38:44 -0500	[thread overview]
Message-ID: <20080704213844.GB29672@tapir> (raw)
In-Reply-To: <5d6222a80807041340j367cfe3ah67a9d771caa0ee63@mail.gmail.com>

On Fri, Jul 04, 2008 at 05:40:03PM -0300, Glauber Costa wrote:
> Hey Folks
> 
> I'm publishing a git repository for the QEMU Accel patches. It lives at
> 
> git://git.kernel.org/pub/scm/virt/qemu/glommer/qemu-accel.git

for the few of us that had been living under a rock, could you give an
explanation on what is QEMU Accel and why we need one?

google bounced me back to the a broken link in the qemu homepage that  doesn't
have a reference to it, and also showed some patches which seem to be trying
to abstract kqemu and kvm which I presume are part of this git tree.

how is this mean to fit on a qemu or kvm installation, and if its main
objective is to be able to have a version of qemu compiled with support for
both kvm and kqemu accelerators, is it at least feature complete enough to
have that working and let you select which one to use?, under which
circumstances?

Carlo

  reply	other threads:[~2008-07-04 21:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-04 20:40 [Qemu-devel] QEMU Accel - git tree Glauber Costa
2008-07-04 21:38 ` Carlo Marcelo Arenas Belon [this message]
2008-07-04 21:27   ` [Qemu-devel] " Glauber Costa
2008-07-07 12:51     ` Gerd Hoffmann
2008-07-07 17:12       ` Jamie Lokier
2008-07-07 17:41         ` Glauber Costa

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=20080704213844.GB29672@tapir \
    --to=carenas@sajinet.com.pe \
    --cc=chrisw@redhat.com \
    --cc=glommer@gmail.com \
    --cc=jes@sgi.com \
    --cc=kvm@vger.kernel.org \
    --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).