From: "Glauber Costa" <glommer@gmail.com>
To: qemu-devel@nongnu.org
Cc: Chris Wright <chrisw@redhat.com>, Jes Sorensen <jes@sgi.com>,
kvm@vger.kernel.org, Hollis Blanchard <hollisb@us.ibm.com>
Subject: Re: [Qemu-devel] Re: QEMU Accel - git tree
Date: Mon, 7 Jul 2008 14:41:48 -0300 [thread overview]
Message-ID: <5d6222a80807071041y5d6e3038nde9f827b0c7f426f@mail.gmail.com> (raw)
In-Reply-To: <20080707171207.GB7707@shareable.org>
On Mon, Jul 7, 2008 at 2:12 PM, Jamie Lokier <jamie@shareable.org> wrote:
> Gerd Hoffmann wrote:
>> Glauber Costa wrote:
>> > Talking to hollis last week, he pointed out that a better solution
>> > would be to make all of them to use the same kernel interface. It's a
>> > valid approach, but I believe an user-space interface would be more
>> > flexible. That's why I'm still maintaining this set (now in tree-form
>> > ;-) )
>>
>> Especially in case we'll add xen to the picture ...
>
> However, don't forget that plain QEMU doesn't use a kernel interface.
> Does that count as a "different" kernel interface for the purpose of
> these hooks? :-)
I don't think the word "kernel interface" has any need to be involved
whatsoever, but to ilustrate a particular kvm / kqemu issue.
The way it is now, that's just a userspace interface for an an
accelerator, whatever it is.
> -- Jamie
>
>
>
--
Glauber Costa.
"Free as in Freedom"
http://glommer.net
"The less confident you are, the more serious you have to act."
prev parent reply other threads:[~2008-07-07 17:41 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 ` [Qemu-devel] " Carlo Marcelo Arenas Belon
2008-07-04 21:27 ` Glauber Costa
2008-07-07 12:51 ` Gerd Hoffmann
2008-07-07 17:12 ` Jamie Lokier
2008-07-07 17:41 ` Glauber Costa [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=5d6222a80807071041y5d6e3038nde9f827b0c7f426f@mail.gmail.com \
--to=glommer@gmail.com \
--cc=chrisw@redhat.com \
--cc=hollisb@us.ibm.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).