From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:47373) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1g0qVl-0002m1-M1 for qemu-devel@nongnu.org; Fri, 14 Sep 2018 12:00:02 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1g0qVk-0005uE-T9 for qemu-devel@nongnu.org; Fri, 14 Sep 2018 12:00:01 -0400 Received: from mail-ot1-x342.google.com ([2607:f8b0:4864:20::342]:42622) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1g0qVk-0005tb-O4 for qemu-devel@nongnu.org; Fri, 14 Sep 2018 12:00:00 -0400 Received: by mail-ot1-x342.google.com with SMTP id h26-v6so5051665otl.9 for ; Fri, 14 Sep 2018 09:00:00 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: References: <20180912081747.3228.21861.stgit@pasha-VirtualBox> <20180912081950.3228.68987.stgit@pasha-VirtualBox> <002101d44bee$9edf9720$dc9ec560$@ru> From: Peter Maydell Date: Fri, 14 Sep 2018 16:59:39 +0100 Message-ID: Content-Type: text/plain; charset="UTF-8" Subject: Re: [Qemu-devel] [PATCH v6 21/25] replay: replay BH for IDE trim operation List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Paolo Bonzini Cc: John Snow , Pavel Dovgalyuk , Pavel Dovgalyuk , QEMU Developers , Kevin Wolf , war2jordan@live.com, Juan Quintela , Ciro Santilli , Jason Wang , Peter Crosthwaite , Aleksandr Bezzubikov , Markus Armbruster , maria.klimushenkova@ispras.ru, "Michael S. Tsirkin" , Gerd Hoffmann , Igor R , Thomas Dullien , Max Reitz , =?UTF-8?B?QWxleCBCZW5uw6ll?= , "Dr. David Alan Gilbert" , Richard Henderson On 14 September 2018 at 16:19, Paolo Bonzini wrote: > On 14/09/2018 16:00, John Snow wrote: >>> Maybe not. We can hardly analyze all peripheral devices code and fix all the calls. >>> But I think we can improve that patch and at least look through ide core to fix other calls. >>> >>> Pavel Dovgalyuk >>> >> It just seems odd that if you're working on a replay mechanism that >> requires you to intercept my QEMU API calls that you're only changing a >> trim callback. > > You need it only here because the block layer is already calling > replay_bh_schedule_event (actually replay_bh_schedule_oneshot_event > after patch 22 of this series) on reads and writes. Do we have documentation describing when a device model needs to care about record/replay ? thanks -- PMM