From: Glauber Costa <gcosta@redhat.com>
To: Avi Kivity <avi@qumranet.com>
Cc: kvm-devel@lists.sourceforge.net, glommer@gmail.com,
qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [PATCH] [RFC] try to reduce kvm impact in core qemu code.
Date: Tue, 29 Apr 2008 20:35:36 -0300 [thread overview]
Message-ID: <4817B0C8.8080301@redhat.com> (raw)
In-Reply-To: <4817A257.7000800@qumranet.com>
Avi Kivity wrote:
> Glauber Costa wrote:
>> Hi. This is a proposal for reducing the impact of kvm functions in
>> core qemu
>> code. This is by all means not ready, but I felt like posting it, so a
>> discussion
>> on it could follow.
>>
>> The idea in this patch is to replace the specific kvm details from
>> core qemu files
>> like vl.c, with driver_yyy() functions. When kvm is not running, those
>> functions would
>> just return (most of time), absolutely reducing the impact of kvm code.
>>
>> As I wanted to test it, in this patch I changed the kvm functions to
>> be called driver_yyy(),
>> but that's not my final goal. I intend to use a function pointer
>> schema, similar to what the linux
>> kernel already do for a lot of its subsystem, to isolate the changes.
>>
>> Comments deeply welcome.
>>
>
> While I would be very annoyed if someone referred to kvm as a qemu
> accelerator, I think accelerator_yyy() is more descriptive than
> driver_yyy().
How about booster? ;-)
> I did not see any references to kqemu, but I imagine you mean this to
> abstract kqemu support as well.
Yeah, even the kvm part is not complete. As I said, just wanted to get
it going.
>
> Other than that, looks really good.
>
thanks
next prev parent reply other threads:[~2008-04-29 23:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-29 19:43 [Qemu-devel] [PATCH] [RFC] try to reduce kvm impact in core qemu code Glauber Costa
2008-04-29 22:33 ` [Qemu-devel] " Avi Kivity
2008-04-29 23:35 ` Glauber Costa [this message]
2008-04-30 0:27 ` [Qemu-devel] Re: [kvm-devel] " Anthony Liguori
2008-04-30 2:59 ` 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=4817B0C8.8080301@redhat.com \
--to=gcosta@redhat.com \
--cc=avi@qumranet.com \
--cc=glommer@gmail.com \
--cc=kvm-devel@lists.sourceforge.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).