From mboxrd@z Thu Jan 1 00:00:00 1970 From: Paolo Bonzini Subject: Re: Calling to kvm_mmu_load Date: Thu, 31 Oct 2013 10:52:26 +0100 Message-ID: <5272285A.70907@redhat.com> References: <52676AF4.4080906@redhat.com> <5269BEAC.90809@redhat.com> <526FB05E.1070204@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: kvm , Jan Kiszka To: Arthur Chunqi Li Return-path: Received: from mx1.redhat.com ([209.132.183.28]:28910 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750712Ab3JaJwa (ORCPT ); Thu, 31 Oct 2013 05:52:30 -0400 In-Reply-To: Sender: kvm-owner@vger.kernel.org List-ID: Il 31/10/2013 09:05, Arthur Chunqi Li ha scritto: >> > >> > Basically everything that accesses the dirty_bitmap field of struct >> > kvm_memory_slot is involved. It all starts when the >> > KVM_SET_USER_MEMORY_REGION ioctl is called with the >> > KVM_MEM_LOG_DIRTY_PAGES flag set. > I find the mechanism here is set all pages read-only to track all the > dirty pages. But EPT provides such a dirty bit in EPT paging > structures. Why don't we use this? It doesn't provide it on all processors. Check eptad in /sys/module/kvm_intel/parameters. Paolo