All of lore.kernel.org
 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 4/9] substitute is_allocated_mem with more general	is_containing_region
Date: Tue, 23 Sep 2008 10:35:24 +0300	[thread overview]
Message-ID: <48D89C3C.3080502@redhat.com> (raw)
In-Reply-To: <20080922135117.GC3618@poweredge.glommer>

Glauber Costa wrote:
> On Sat, Sep 20, 2008 at 11:33:56AM -0700, Avi Kivity wrote:
>   
>> Glauber Costa wrote:
>>     
>>> is_allocated_mem is a function that checks if every relevant aspect of the memory slot
>>> match (start and size). Replace it with a more generic function that checks if a memory
>>> region is totally contained into another. The former case is also covered.
>>>   
>>>       
>> I think enabling dirty page tracking requires the slot to match exactly.
>>     
>
> The registering function was the only caller for that. As dirty tracking was happening
> _inside_ it, so we're not really losing anything here.
>
> That said, I believe in the future, it will. (would be a logical next step, and start
> addressing the problem that Jan raised). Maybe we can keep the function that checks for
> exact matching, but another alternative is to pass a phys_addr, and turn dirty tracking on/off
> for whatever slot that contains that phys_addr. What do you think?
>   

Exact matching would avoid surprises (catch errors early).

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


  reply	other threads:[~2008-09-23  7:35 UTC|newest]

Thread overview: 35+ 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 [this message]
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
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
  -- strict thread matches above, loose matches on Subject: below --
2008-09-12 15:10 [PATCH 0/9] Simplify memory registration Glauber Costa
2008-09-12 15:10 ` [PATCH 4/9] substitute is_allocated_mem with more general is_containing_region Glauber Costa

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=48D89C3C.3080502@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 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.