All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Glauber Costa <glommer@redhat.com>
Cc: aliguori@us.ibm.com, qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [PATCH] remove smaller slots if registering a bigger one
Date: Wed, 11 Feb 2009 15:23:07 +0100	[thread overview]
Message-ID: <4992DF4B.6070109@siemens.com> (raw)
In-Reply-To: <1234360034-19459-1-git-send-email-glommer@redhat.com>

Glauber Costa wrote:
> It's like a shark eating a bunch of small fishes:
> in some situations (vga linear frame buffer mapping,
> for example), we need to register a new slot in place
> of older, smaller ones. This patch handles this case
> 
> Signed-off-by: Glauber Costa <glommer@redhat.com>
> ---
>  kvm-all.c |   10 ++++++++++
>  1 files changed, 10 insertions(+), 0 deletions(-)
> 
> diff --git a/kvm-all.c b/kvm-all.c
> index 9fb295c..53aca0a 100644
> --- a/kvm-all.c
> +++ b/kvm-all.c
> @@ -582,6 +582,16 @@ void kvm_set_phys_mem(target_phys_addr_t start_addr,
>                  kvm_set_phys_mem(mem_start, mem_size, mem_offset);
>  
>              return;
> +        } else if (start_addr <= mem->start_addr &&
> +                   (start_addr + size) >= (mem->start_addr +
> +                                           mem->memory_size)) {
> +            KVMSlot slot;
> +            /* unregister whole slot */
> +            memcpy(&slot, mem, sizeof(slot));
> +            mem->memory_size = 0;
> +            kvm_set_user_memory_region(s, mem);
> +
> +            kvm_set_phys_mem(start_addr, size, phys_offset);

That may solve some problems, but...

>          } else {
>              printf("Registering overlapping slot\n");
>              abort();
            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
...as long as this line exists, issues will remain. IIRC, the mapping
the i440 tries to re-establish after reboot will hit this case.


BTW, I found the unposted patch below in my attic, maybe you can comment
on it (if it makes sense, I'll properly repost with signed-off).

Thanks,
Jan

---------->

kvm: cleanup unmap condition in kvm_set_phys_mem
    
Testing for TLB_MMIO on unmap makes no sense as A) that flag belongs to
CPUTLBEntry and not to io_memory slots or physical addresses and B) we
already use a different condition before mapping. So make this test
consistent.

diff --git a/kvm-all.c b/kvm-all.c
index 9fb295c..c0481a0 100644
--- a/kvm-all.c
+++ b/kvm-all.c
@@ -540,7 +540,7 @@ void kvm_set_phys_mem(target_phys_addr_t start_addr,
 
     mem = kvm_lookup_slot(s, start_addr);
     if (mem) {
-        if ((flags == IO_MEM_UNASSIGNED) || (flags >= TLB_MMIO)) {
+        if (flags >= IO_MEM_UNASSIGNED) {
             mem->memory_size = 0;
             mem->start_addr = start_addr;
             mem->phys_offset = 0;

  reply	other threads:[~2009-02-11 14:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-11 13:47 [Qemu-devel] [PATCH] remove smaller slots if registering a bigger one Glauber Costa
2009-02-11 14:23 ` Jan Kiszka [this message]
2009-02-11 14:36   ` [Qemu-devel] " Avi Kivity
2009-02-11 14:37   ` Glauber Costa
2009-02-11 14:45     ` Jan Kiszka
2009-02-11 14:52       ` Jan Kiszka
2009-02-11 14:59       ` Glauber Costa
2009-02-11 15:30       ` Avi Kivity
2009-02-11 16:47         ` Jan Kiszka
2009-02-11 16:56           ` Avi Kivity

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=4992DF4B.6070109@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=aliguori@us.ibm.com \
    --cc=glommer@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.