Re: [patch 07/15] clocksource: Provide unbind interface in sysfs

2013-05-15 Thread Thomas Gleixner
On Wed, 15 May 2013, John Stultz wrote: > On 05/15/2013 02:47 AM, Thomas Gleixner wrote: > > TSC is current clocksource and we only have ACPI_PM as watchdog and > > its used. So now you try to unbind ACPI_PM then the TSC would be left > > w/o a watchdog instance. That's what I'm preventing. Will re

Re: [patch 07/15] clocksource: Provide unbind interface in sysfs

2013-05-15 Thread John Stultz
On 05/15/2013 02:47 AM, Thomas Gleixner wrote: On Mon, 29 Apr 2013, John Stultz wrote: On 04/25/2013 01:31 PM, Thomas Gleixner wrote: With the module refcount held for the current clocksource there is no way to unload the module. Provide a sysfs interface which allows to unbind the clocksource

Re: [patch 07/15] clocksource: Provide unbind interface in sysfs

2013-05-15 Thread Thomas Gleixner
On Mon, 29 Apr 2013, John Stultz wrote: > On 04/25/2013 01:31 PM, Thomas Gleixner wrote: > > With the module refcount held for the current clocksource there is no > > way to unload the module. > > > > Provide a sysfs interface which allows to unbind the clocksource. One > > could argue that the cl

Re: [patch 07/15] clocksource: Provide unbind interface in sysfs

2013-04-29 Thread John Stultz
On 04/25/2013 01:31 PM, Thomas Gleixner wrote: With the module refcount held for the current clocksource there is no way to unload the module. Provide a sysfs interface which allows to unbind the clocksource. One could argue that the clocksource override could be (ab)used to do so, but the clock

[patch 07/15] clocksource: Provide unbind interface in sysfs

2013-04-25 Thread Thomas Gleixner
With the module refcount held for the current clocksource there is no way to unload the module. Provide a sysfs interface which allows to unbind the clocksource. One could argue that the clocksource override could be (ab)used to do so, but the clocksource override cannot be used from the kernel i