From: Avi Kivity <avi@qumranet.com>
To: Glauber Costa <gcosta@redhat.com>
Cc: kvm@vger.kernel.org, aliguori@us.ibm.com
Subject: Re: [PATCH 5/9] substitute is_allocated_mem with more general is_containing_region
Date: Wed, 13 Aug 2008 14:41:33 +0300 [thread overview]
Message-ID: <48A2C86D.5030706@qumranet.com> (raw)
In-Reply-To: <1218588489-17182-6-git-send-email-gcosta@redhat.com>
Glauber Costa wrote:
> Signed-off-by: Glauber Costa <gcosta@redhat.com>
> ---
> libkvm/libkvm.c | 34 +++++++++++++++++++++-------------
> libkvm/libkvm.h | 2 +-
> qemu/qemu-kvm.c | 2 +-
> 3 files changed, 23 insertions(+), 15 deletions(-)
>
> diff --git a/libkvm/libkvm.c b/libkvm/libkvm.c
> index 33f00b7..c885dee 100644
> --- a/libkvm/libkvm.c
> +++ b/libkvm/libkvm.c
> @@ -140,6 +140,27 @@ int get_intersecting_slot(unsigned long phys_addr)
> return -1;
> }
>
> +/* Returns -1 if this slot is not totally contained on any other,
> + * and the number of the slot otherwise */
> +int get_container_slot(uint64_t phys_addr, unsigned long size)
> +{
> + int i;
> +
> + for (i = 0; i < KVM_MAX_NUM_MEM_REGIONS ; ++i)
> + if (slots[i].len && slots[i].phys_addr <= phys_addr &&
> + (slots[i].phys_addr + slots[i].len) >= phys_addr + size)
> + return i;
> + return -1;
> +}
> +
>
What about partially containing (or: overlapping) slots?
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2008-08-13 11:41 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 ` [PATCH 6/9] move kvm_cpu_register_memory_area into qemu's Anthony Liguori
2008-08-13 14:33 ` Glauber Costa
2008-08-13 11:41 ` Avi Kivity [this message]
2008-08-13 13:02 ` [PATCH 5/9] substitute is_allocated_mem with more general is_containing_region 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=48A2C86D.5030706@qumranet.com \
--to=avi@qumranet.com \
--cc=aliguori@us.ibm.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