From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:43595) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1X1cgh-0003B7-5i for qemu-devel@nongnu.org; Mon, 30 Jun 2014 10:36:16 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1X1cgY-0003Ry-5J for qemu-devel@nongnu.org; Mon, 30 Jun 2014 10:36:07 -0400 Received: from mail-wi0-x22c.google.com ([2a00:1450:400c:c05::22c]:59834) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1X1cgX-0003Rf-Ui for qemu-devel@nongnu.org; Mon, 30 Jun 2014 10:35:58 -0400 Received: by mail-wi0-f172.google.com with SMTP id hi2so6179447wib.17 for ; Mon, 30 Jun 2014 07:35:57 -0700 (PDT) Sender: Paolo Bonzini Message-ID: <53B175C9.3070806@redhat.com> Date: Mon, 30 Jun 2014 16:35:53 +0200 From: Paolo Bonzini MIME-Version: 1.0 References: <53ADE6F8.1070303@redhat.com> <53B14064.8010600@redhat.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] The first function called after migration for a block device List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Xiongzi Ge Cc: qemu-devel@nongnu.org Il 30/06/2014 16:03, Xiongzi Ge ha scritto: > I tried. It invalidated the cache of the block device after migration. It didn't invalidate anything in the guest, and there's *NO WAY* absolutely for QEMU to influence the cache in the guest. Again: all you can do is use O_DIRECT in the guest. > So, here, we can use a new cache for the block device after migration. I don't understand what you mean. > Is it right? I can implement a simple block driver in block/ directory. Probably not. Paolo