public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <aliguori@us.ibm.com>
To: Glauber Costa <gcosta@redhat.com>
Cc: kvm@vger.kernel.org, avi@qumranet.com
Subject: Re: [PATCH 6/9] move kvm_cpu_register_memory_area into qemu's
Date: Wed, 13 Aug 2008 09:11:43 -0500	[thread overview]
Message-ID: <48A2EB9F.6070009@us.ibm.com> (raw)
In-Reply-To: <1218588489-17182-7-git-send-email-gcosta@redhat.com>

Glauber Costa wrote:
> Turn the explicit calls to kvm_cpu_register_memoy_area()
> an empty function. Provide a __kvm_cpu_register_memory_area()
> that is called from within cpu_register_memory_area().
> To avoid registering mmio regions to the hypervisor, since we depend on
> them faulting, we keep track of what regions are mmio regions too.
>
> This is to be bisection friendly. Direct calls are to be removed
> in a later commit.
>
> diff --git a/qemu/exec.c b/qemu/exec.c
> index 7a68062..14c3852 100644
> --- a/qemu/exec.c
> +++ b/qemu/exec.c
> @@ -2196,6 +2196,9 @@ void cpu_register_physical_memory(target_phys_addr_t start_addr,
>          kqemu_set_phys_mem(start_addr, size, phys_offset);
>      }
>  #endif
> +
> +    __kvm_cpu_register_physical_memory(start_addr, size, phys_offset);
>
>   

This is a great place to add a callback of some sort (like QEMUAccel).  
Then it can be shared by both kqemu and kvm.

Regards,

Anthony Liguori


  parent reply	other threads:[~2008-08-13 14:12 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-13  0:48 [RFC 0/9] Memory registration rework Glauber Costa
2008-08-13  0:48 ` [PATCH 1/9] add debuging facilities to memory registration at libkvm Glauber Costa
2008-08-13  0:48   ` [PATCH 2/9] experimental change to avoid doing the same thing twice Glauber Costa
2008-08-13  0:48     ` [PATCH 3/9] do not use mem_hole anymore Glauber Costa
2008-08-13  0:48       ` [PATCH 4/9] allow intersecting region to be on the boundary Glauber Costa
2008-08-13  0:48         ` [PATCH 5/9] substitute is_allocated_mem with more general is_containing_region Glauber Costa
2008-08-13  0:48           ` [PATCH 6/9] move kvm_cpu_register_memory_area into qemu's Glauber Costa
2008-08-13  0:48             ` [PATCH 7/9] cleanup kvm memory registration Glauber Costa
2008-08-13  0:48               ` [PATCH 8/9] coalesce mmio regions without an explicit call Glauber Costa
2008-08-13  0:48                 ` [PATCH 9/9] remove explicit calls to kvm_qemu_register_coalesced_mmio Glauber Costa
2008-08-13 14:11             ` Anthony Liguori [this message]
2008-08-13 14:33               ` [PATCH 6/9] move kvm_cpu_register_memory_area into qemu's Glauber Costa
2008-08-13 11:41           ` [PATCH 5/9] substitute is_allocated_mem with more general is_containing_region Avi Kivity
2008-08-13 13:02             ` Glauber Costa
2008-08-13 11:43 ` [RFC 0/9] Memory registration rework Avi Kivity
2008-08-13 14:13   ` Anthony Liguori

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=48A2EB9F.6070009@us.ibm.com \
    --to=aliguori@us.ibm.com \
    --cc=avi@qumranet.com \
    --cc=gcosta@redhat.com \
    --cc=kvm@vger.kernel.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