public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Glauber Costa <gcosta@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: kvm-devel@lists.sourceforge.net, qemu-devel@nongnu.org,
	Avi Kivity <avi@qumranet.com>
Subject: Re: [PATCH] [RFC] try to reduce kvm impact in core qemu code.
Date: Tue, 29 Apr 2008 23:59:14 -0300	[thread overview]
Message-ID: <4817E082.2060908@redhat.com> (raw)
In-Reply-To: <4817BD06.5020909@codemonkey.ws>

Anthony Liguori wrote:
> Glauber Costa wrote:
>> 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 don't think the concern from a QEMU perspective is that QEMU is too 
> intimately tied to KVM.  The concern is that overtime, it will be very 
> difficult to make changes to QEMU without breaking KVM support because 
> of the shear number of hooks we require.  Fabrice had actually suggested 
> merging libkvm into QEMU.  We just need to reduce the overall number of 
> if (kvm_enabled()) blocks.

They are not mutually exclusive. Even if we do merge libkvm into qemu, 
having it more modular and separated will be way better than having kvm 
hooks all over.


-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
Don't miss this year's exciting event. There's still time to save $100. 
Use priority code J8TL2D2. 
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone

      reply	other threads:[~2008-04-30  2:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-29 19:43 [PATCH] [RFC] try to reduce kvm impact in core qemu code Glauber Costa
2008-04-29 22:33 ` Avi Kivity
2008-04-29 23:35   ` Glauber Costa
2008-04-30  0:27     ` Anthony Liguori
2008-04-30  2:59       ` 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=4817E082.2060908@redhat.com \
    --to=gcosta@redhat.com \
    --cc=anthony@codemonkey.ws \
    --cc=avi@qumranet.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