From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:49298) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bW5kh-0005ju-EB for qemu-devel@nongnu.org; Sat, 06 Aug 2016 13:51:16 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bW5kf-0002EM-JD for qemu-devel@nongnu.org; Sat, 06 Aug 2016 13:51:14 -0400 Received: from mail-oi0-x22d.google.com ([2607:f8b0:4003:c06::22d]:34069) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bW5kf-0002E8-Ee for qemu-devel@nongnu.org; Sat, 06 Aug 2016 13:51:13 -0400 Received: by mail-oi0-x22d.google.com with SMTP id l203so67946564oib.1 for ; Sat, 06 Aug 2016 10:51:12 -0700 (PDT) MIME-Version: 1.0 From: Ashijeet Acharya Date: Sat, 6 Aug 2016 23:21:12 +0530 Message-ID: Content-Type: text/plain; charset=UTF-8 Subject: [Qemu-devel] Dangling change state handler while hot unplugging ahci adapter List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: QEMU Developers , jsnow@redhat.com Hi, I was working on a patch regarding a device lifecycle bitesize task and I wanted to clear my queries about what the task is exactly. Do I need to create a new function ahci_unrealize() in the hw/ide/ahci.c file which calls for qemu_del_vm_change_state_handler() to free the handler at the time of ahci hot unplug. Please tell me if I am on the right path and correct me if I am wrong. Thanks Ashijeet