qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Glauber Costa <glommer@redhat.com>
Cc: Ian.Jackson@eu.citrix.com, qemu-devel@nongnu.org,
	kvm@vger.kernel.org, stefano.stabellini@eu.citrix.com
Subject: [Qemu-devel] Re: [PATCH 5/5] cache slot lookup
Date: Thu, 18 Dec 2008 11:41:24 +0200	[thread overview]
Message-ID: <494A1AC4.30704@redhat.com> (raw)
In-Reply-To: <1229546822-11972-6-git-send-email-glommer@redhat.com>

Glauber Costa wrote:
> record slot used in last lookup. For the common mmio case,
> we'll usually access the same memory slot repeatedly.
>   

> --- a/kvm-all.c
> +++ b/kvm-all.c
> @@ -75,16 +75,25 @@ static KVMSlot *kvm_alloc_slot(KVMState *s)
>      return NULL;
>  }
>  
> +static KVMSlot *last_slot = NULL;
> +
>  static KVMSlot *kvm_lookup_slot(KVMState *s, target_phys_addr_t start_addr)
>  {
>      int i;
>  
> +
> +    if (last_slot && (start_addr >= last_slot->start_addr &&
> +            start_addr < (last_slot->start_addr + last_slot->memory_size)))
> +        return last_slot;
> +
>      for (i = 0; i < ARRAY_SIZE(s->slots); i++) {
>          KVMSlot *mem = &s->slots[i];
>  
>          if (start_addr >= mem->start_addr &&
> -            start_addr < (mem->start_addr + mem->memory_size))
> +            start_addr < (mem->start_addr + mem->memory_size)) {
> +            last_slot = mem;
>              return mem;
> +        }
>      }
>  

This wasn't introduced by this patch, but the comparison is broken ion 
i386 hosts, where target_phys_addr_t is 32 bits wide.  mem->start_addr + 
mem->memory_size can overflow (this in fact happens for the bios slot at 
4G-128K)

-- 
error compiling committee.c: too many arguments to function

  reply	other threads:[~2008-12-18  9:41 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-17 20:46 [Qemu-devel] [PATCH 0/5] Replace tcg memory functions Glauber Costa
2008-12-17 20:46 ` [Qemu-devel] [PATCH 1/5] re-register whole area upon lfb unmap Glauber Costa
2008-12-17 20:46   ` [Qemu-devel] [PATCH 2/5] isolate io handling routing Glauber Costa
2008-12-17 20:47     ` [Qemu-devel] [PATCH 3/5] replace cpu_physical_memory_rw Glauber Costa
2008-12-17 20:47       ` [Qemu-devel] [PATCH 4/5] hook cpu_register_physical_mem Glauber Costa
2008-12-17 20:47         ` [Qemu-devel] [PATCH 5/5] cache slot lookup Glauber Costa
2008-12-18  9:41           ` Avi Kivity [this message]
2008-12-18 10:48             ` [Qemu-devel] " Glauber Costa
2008-12-18 11:00               ` Daniel P. Berrange
2008-12-18 11:07                 ` Glauber Costa
2008-12-18 11:24               ` Avi Kivity
2008-12-17 20:56       ` [Qemu-devel] Re: [PATCH 3/5] replace cpu_physical_memory_rw Anthony Liguori
2008-12-17 21:00         ` Glauber Costa
2008-12-17 20:54     ` [Qemu-devel] Re: [PATCH 2/5] isolate io handling routing Anthony Liguori
2008-12-17 20:53   ` [Qemu-devel] Re: [PATCH 1/5] re-register whole area upon lfb unmap Anthony Liguori
2008-12-25 20:08     ` andrzej zaborowski
2008-12-22 17:10 ` [Qemu-devel] [PATCH 0/5] Replace tcg memory functions Ian Jackson
2008-12-22 17:18   ` Glauber Costa
2008-12-22 17:22     ` Ian Jackson

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=494A1AC4.30704@redhat.com \
    --to=avi@redhat.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=glommer@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stefano.stabellini@eu.citrix.com \
    /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).