linux-kernel - [PATCH 0/1] ACPI: Call ACPI remove handler when handling ACPI eject

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 19 Oct 2011 10:47:49 +0800
From:	pingfank@...ux.vnet.ibm.com
To:	linux-acpi@...r.kernel.org, seabios@...bios.org, lenb@...nel.org,
	shaohua.li@...el.com
Cc:	linux-kernel@...r.kernel.org, qemu-devel@...gnu.org,
	aliguori@...ibm.com, dave@...ux.vnet.ibm.com,
	Liu Ping Fan <pingfank@...ux.vnet.ibm.com>
Subject: [PATCH 0/1] ACPI: Call ACPI remove handler when handling ACPI eject

From: Liu Ping Fan <pingfank@...ux.vnet.ibm.com>

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

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/