From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:37738) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aim2T-0006jO-I8 for qemu-devel@nongnu.org; Wed, 23 Mar 2016 12:53:46 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aim2O-0008Eu-EK for qemu-devel@nongnu.org; Wed, 23 Mar 2016 12:53:45 -0400 Received: from mx1.redhat.com ([209.132.183.28]:59034) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aim2O-0008Eg-97 for qemu-devel@nongnu.org; Wed, 23 Mar 2016 12:53:40 -0400 References: <1455744555-22101-1-git-send-email-hollis_blanchard@mentor.com> <1455744555-22101-2-git-send-email-hollis_blanchard@mentor.com> <1458751625.2947.19.camel@mentor.com> From: Paolo Bonzini Message-ID: <56F2CA0F.9030307@redhat.com> Date: Wed, 23 Mar 2016 17:53:35 +0100 MIME-Version: 1.0 In-Reply-To: <1458751625.2947.19.camel@mentor.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH 2/2] trace: separate MMIO tracepoints from TB-access tracepoints List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Hollis Blanchard Cc: qemu-devel@nongnu.org, stefanha@redhat.com On 23/03/2016 17:47, Hollis Blanchard wrote: > Paolo, is it true that only TB-invalidating writes go through the > io_mem_notdirty path? I'm looking at the live migration code now, and it > seems like every memory write will go through that path when global > dirty memory logging is enabled. When live migration is enabled, writes to clean memory (almost all of them) will go through that path indeed. Some writes to the framebuffer will go through that path too. It depends on cpu_physical_memory_is_clean( memory_region_get_ram_addr(section->mr) + xlat)) in tlb_set_page_with_attrs. Paolo