kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Glauber Costa <glommer@redhat.com>
Cc: kvm@vger.kernel.org, aliguori@us.ibm.com
Subject: Re: [PATCH 8/9] coalesce mmio regions with an explicit call
Date: Wed, 24 Sep 2008 14:10:26 +0300	[thread overview]
Message-ID: <48DA2022.8020807@redhat.com> (raw)
In-Reply-To: <20080923162233.GD3583@poweredge.glommer>

Glauber Costa wrote:
>> You can't coalesce the registers which trigger device action.  You'll  
>> destroy latency and/or functionality.
>>     
>
> which kills the goal of getting rid of explicit kvm code.
>
>   

It's a fact that coalescing helps kvm but not qemu.

> So maybe the solution here is to add calls in qemu to a memory
> coalescing function that in the raw qemu / kqemu case just don't
> do anything?
>   

That's just word games.  s/kvm/qemu/ won't change the fact that this is 
a kvm specific hook.

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


  reply	other threads:[~2008-09-24 11:18 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-19 16:08 [PATCHEY 0/9] Rrrreplace the ol' scurvy memory registration Glauber Costa
2008-09-19 16:08 ` [PATCH 1/9] Don't separate registrations with IO_MEM_ROM set Glauber Costa
2008-09-19 16:08 ` [PATCH 2/9] do not use mem_hole anymore Glauber Costa
2008-09-19 16:08 ` [PATCH 3/9] allow intersecting region to be on the boundary Glauber Costa
2008-09-20 18:32   ` Avi Kivity
2008-09-22 13:48     ` Glauber Costa
2008-09-23 10:30       ` Avi Kivity
2008-09-23 16:18         ` Glauber Costa
2008-09-19 16:08 ` [PATCH 4/9] substitute is_allocated_mem with more general is_containing_region Glauber Costa
2008-09-20 18:33   ` Avi Kivity
2008-09-22 13:51     ` Glauber Costa
2008-09-23  7:35       ` Avi Kivity
2008-09-23 16:19         ` Glauber Costa
2008-09-19 16:08 ` [PATCH 5/9] add debuging facilities to memory registration at libkvm Glauber Costa
2008-09-20 18:34   ` Avi Kivity
2008-09-22 13:52     ` Glauber Costa
2008-09-19 16:08 ` [PATCH 6/9] unregister memory area depending on their flags Glauber Costa
2008-09-19 16:08 ` [PATCH 7/9] register mmio slots Glauber Costa
2008-09-20 18:38   ` Avi Kivity
2008-09-22 13:55     ` Glauber Costa
2008-09-23  7:31       ` Avi Kivity
2008-09-23 16:48         ` Glauber Costa
2008-09-19 16:08 ` [PATCH 8/9] coalesce mmio regions with an explicit call Glauber Costa
2008-09-20 18:39   ` Avi Kivity
2008-09-22 13:56     ` Glauber Costa
2008-09-23  7:29       ` Avi Kivity
2008-09-23 16:22         ` Glauber Costa
2008-09-24 11:10           ` Avi Kivity [this message]
2008-09-24 21:59             ` Glauber Costa
2008-09-25  7:08               ` Avi Kivity
2008-09-25 11:19                 ` Glauber Costa
2009-04-17 14:04   ` Dmitry Eremin-Solenikov
2008-09-19 16:08 ` [PATCH 9/9] move kvm memory registration inside qemu's Glauber Costa
2008-09-19 16:33   ` Jan Kiszka

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=48DA2022.8020807@redhat.com \
    --to=avi@redhat.com \
    --cc=aliguori@us.ibm.com \
    --cc=glommer@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;
as well as URLs for NNTP newsgroup(s).