http://bugzilla.kernel.org/show_bug.cgi?id=9772
------- Comment #7 from [EMAIL PROTECTED] 2008-01-24 17:02 ------- (In reply to comment #3) > There's a couple of problems. So it really works for you, right? ie, "echo 0 > online" first and "echo 1 > eject" then can hot remove a processor successfully. > /sys/devices/system/cpu/cpuX/online doesn't always correspond to > /sys/bus/acpi/drivers/processor/ACPI0007:0X. Especially if you remove and > then > re-add CPUS, you can get a situation where CPU3 corresponds to ACPI0007:08, or > something similar. Yes. Hmm, can we create a sysfs link here, from cpu sysdev to acpi device node? > Ejecting a CPU really needs to fail if the CPU is online, or else it > needs to automatically offline the CPU. Failing if the CPU is online seems > > to make the most sense. Yes. you're right. I'll look into this. -- Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is. ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ acpi-bugzilla mailing list acpi-bugzilla@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla
