qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <aliguori@us.ibm.com>
To: Paul Brook <paul@codesourcery.com>
Cc: Glauber Costa <glommer@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/6] Bypass tcg memory functions -v1.0-2009
Date: Wed, 21 Jan 2009 13:26:01 -0600	[thread overview]
Message-ID: <497776C9.5050309@us.ibm.com> (raw)
In-Reply-To: <200901210543.07538.paul@codesourcery.com>

Paul Brook wrote:
> On Tuesday 20 January 2009, Glauber Costa wrote:
>   
>> This series is not very different from the last one that did it.
>> Just bringing it back from my vacations. Idea is to replace tcg
>> memory functions with kvm's, selectable at runtime. Right now
>> we use a conditional selection. In the future, we might use
>> function pointers to allow for easy coupling of any hypervisor.
>>     
>
> I dislike that you're introducing two different ways or doing the same thing.  
> Duplicating all the memory region tracking code seems like a bad way to solve 
> this problem.
>   

To me, this patch set is really about defining the memory API for QEMU's 
CPU emulation/virtualization core.  It can be made a lot prettier by 
introducing function pointers and such but doing the separation and 
having two implementations is the first step in that direction.

I believe this is the right level of abstraction.  Trying to make shared 
code with a lower level interface is much more complicated because TCG 
has some need for deep hooks in the memory code.  If TCG ever wants to 
use memory slots instead of a tree, I'd rather see common code 
abstracted into a set of libs than making the slot code the main code 
with hooks for TCG.

A big part of the reason for these patches is to make it possible to 
build QEMU without TCG in an architecturally clean way.

Regards,

Anthony Liguori

> Paul
>   

      parent reply	other threads:[~2009-01-21 19:26 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-20 18:50 [Qemu-devel] [PATCH 0/6] Bypass tcg memory functions -v1.0-2009 Glauber Costa
2009-01-20 18:51 ` [Qemu-devel] [PATCH 1/6] remove smaller slots if registering a bigger one Glauber Costa
2009-01-20 18:51   ` [Qemu-devel] [PATCH 2/6] re-register whole area upon lfb unmap Glauber Costa
2009-01-20 18:51     ` [Qemu-devel] [PATCH 3/6] isolate io handling routine Glauber Costa
2009-01-20 18:51       ` [Qemu-devel] [PATCH 4/6] replace cpu_physical_memory_rw Glauber Costa
2009-01-20 18:51         ` [Qemu-devel] [PATCH 5/6] hook cpu_register_physical_mem Glauber Costa
2009-01-20 18:51           ` [Qemu-devel] [PATCH 6/6] cache slot lookup Glauber Costa
2009-01-20 20:24         ` [Qemu-devel] [PATCH 4/6] replace cpu_physical_memory_rw Avi Kivity
2009-01-20 20:33           ` Glauber Costa
2009-01-21  5:43 ` [Qemu-devel] [PATCH 0/6] Bypass tcg memory functions -v1.0-2009 Paul Brook
2009-01-21 11:46   ` Glauber Costa
2009-01-21 17:16     ` Ian Jackson
2009-01-21 18:40       ` Glauber Costa
2009-01-22  0:11       ` Paul Brook
2009-01-22 14:02         ` Glauber Costa
2009-01-26 20:42         ` Anthony Liguori
2009-01-21 19:26   ` Anthony Liguori [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=497776C9.5050309@us.ibm.com \
    --to=aliguori@us.ibm.com \
    --cc=glommer@redhat.com \
    --cc=paul@codesourcery.com \
    --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).