On 04/17/2012 05:54 PM, Takuya Yoshikawa wrote: > On Tue, 17 Apr 2012 15:41:39 +0300 > Avi Kivity <a...@redhat.com> wrote: > > > > Since there are many known algorithms to predict hot memory pages, > > > the userspace will be able to tune the frequency of GET_DIRTY_LOG for such > > > parts not to get too many faults repeatedly, if we can restrict the range > > > of pages to protect. > > > > > > This is the fine-grained control. > > > > Do you want per-page control, or just range-based? > > Difficult question. > > For live migration, range-based control may be enough duo to the locality > of WWS.
What's WWS? I don't see a reason to assume locality in gpa space (or in gva space either, for some workloads). -- error compiling committee.c: too many arguments to function -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
