From: Avi Kivity <avi@redhat.com>
To: Izik Eidus <ieidus@redhat.com>
Cc: kvm@vger.kernel.org
Subject: Re: [PATCH 1/2] kvm: fix dirty bit tracking for slots with large pages
Date: Sun, 14 Jun 2009 14:10:11 +0300 [thread overview]
Message-ID: <4A34DA93.6000006@redhat.com> (raw)
In-Reply-To: <1244651005-18322-2-git-send-email-ieidus@redhat.com>
Izik Eidus wrote:
> When slot is already allocted and being asked to be tracked we need to break the
> large pages.
>
> This code flush the mmu when someone ask a slot to start dirty bit tracking.
>
>
Applied, thanks.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2009-06-14 11:10 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-10 16:23 [PATCH 0/2] RFC use dirty bit for page dirty tracking (v2) Izik Eidus
2009-06-10 16:23 ` [PATCH 1/2] kvm: fix dirty bit tracking for slots with large pages Izik Eidus
2009-06-10 16:23 ` [PATCH 2/2] kvm: change the dirty page tracking to work with dirty bity Izik Eidus
2009-06-10 17:00 ` Izik Eidus
2009-06-10 20:42 ` Marcelo Tosatti
2009-06-10 23:57 ` Izik Eidus
2009-06-10 23:59 ` Izik Eidus
2009-06-11 1:04 ` Marcelo Tosatti
2009-06-11 11:27 ` Izik Eidus
2009-06-11 12:24 ` Marcelo Tosatti
2009-06-11 15:49 ` Izik Eidus
2009-06-11 8:24 ` Ulrich Drepper
2009-06-11 9:44 ` Izik Eidus
2009-06-11 9:33 ` Avi Kivity
2009-06-11 9:48 ` Izik Eidus
2009-06-11 9:53 ` Avi Kivity
2009-06-14 11:10 ` Avi Kivity [this message]
2009-06-15 14:58 ` [PATCH 0/2] RFC use dirty bit for page dirty tracking (v2) Ryan Harper
2009-06-15 15:19 ` Avi Kivity
2009-07-07 3:32 ` Ryan Harper
2009-07-07 5:11 ` Avi Kivity
-- strict thread matches above, loose matches on Subject: below --
2009-06-10 11:51 [PATCH 0/2] *** SUBJECT HERE *** Izik Eidus
2009-06-10 11:51 ` [PATCH 1/2] kvm: fix dirty bit tracking for slots with large pages Izik Eidus
2009-06-10 11:54 ` Avi Kivity
2009-06-10 12:06 ` Izik Eidus
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=4A34DA93.6000006@redhat.com \
--to=avi@redhat.com \
--cc=ieidus@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.