>> ?? >> If resource was not allocated a driver, a driver doesn't need to >> deallocate it when >> error path. I haven't caught your point. >> > > REMOVAL_NORMAL can be in 2 cases: > 1. error path. If init call fails, we don't call it. We call this function > only when something fails after init. > 2. unbind the device from the driver. > If we don't offline and remove memory when unbinding the device from the > driver, > the device may be out of control. When we eject this driver, we don't > offline and
Memory never be out of control by driver unloading. It is controled from kernel core. It is an exception from regular linux driver model. > remove it, but we will eject and poweroff the device. It is very dangerous > because > the kernel uses the memory but we poweroff it. > > acpi_bus_hot_remove_device() > acpi_bus_trim() // this function successes because the device has no > driver > _PS3 // poweroff > _EJ0 // eject -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
