From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:47084) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RGMEO-00071X-0i for qemu-devel@nongnu.org; Tue, 18 Oct 2011 22:50:12 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RGMEN-0000nT-0W for qemu-devel@nongnu.org; Tue, 18 Oct 2011 22:50:11 -0400 Received: from e28smtp01.in.ibm.com ([122.248.162.1]:51586) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RGMEM-0000nN-9W for qemu-devel@nongnu.org; Tue, 18 Oct 2011 22:50:10 -0400 Received: from d28relay01.in.ibm.com (d28relay01.in.ibm.com [9.184.220.58]) by e28smtp01.in.ibm.com (8.14.4/8.13.1) with ESMTP id p9J2o8xh012943 for ; Wed, 19 Oct 2011 08:20:08 +0530 Received: from d28av04.in.ibm.com (d28av04.in.ibm.com [9.184.220.66]) by d28relay01.in.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id p9J2mqEs4313228 for ; Wed, 19 Oct 2011 08:18:52 +0530 Received: from d28av04.in.ibm.com (loopback [127.0.0.1]) by d28av04.in.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id p9J2mp6j030469 for ; Wed, 19 Oct 2011 13:48:52 +1100 From: pingfank@linux.vnet.ibm.com Date: Wed, 19 Oct 2011 10:47:49 +0800 Message-Id: <1318992470-10195-1-git-send-email-pingfank@linux.vnet.ibm.com> Subject: [Qemu-devel] [PATCH 0/1] ACPI: Call ACPI remove handler when handling ACPI eject List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: linux-acpi@vger.kernel.org, seabios@seabios.org, lenb@kernel.org, shaohua.li@intel.com Cc: Liu Ping Fan , aliguori@us.ibm.com, dave@linux.vnet.ibm.com, linux-kernel@vger.kernel.org, qemu-devel@nongnu.org From: Liu Ping Fan When I tried to enable cpu hotplug feature for qemu-kvm, I found that the ACPI device eject event just skipped by kernel. static void acpi_bus_notify(acpi_handle handle, u32 type, void *data) { case ACPI_NOTIFY_EJECT_REQUEST: /* TBD */---> skipped from here } But I notice, in drivers/acpi/dock.c, dock_notify()->handle_eject_request() will handle such event for ACPI _dock device. So what we shall do, changing Qemu's SeaBIOS or changing the kernel? If changing SeaBIOS, will it affect guest MS-Window? Thanks, ping fan