Re: [PATCH] fix cpufreq_stats attrs removal
- From: Dave Jones <davej@xxxxxxxxxx>
- Date: Thu, 22 Mar 2007 13:14:36 -0400
On Thu, Mar 22, 2007 at 06:02:01PM +0100, Mattia Dongili wrote:
The problem is cpufreq_stats doesn't know when a cpufreq driver is
removed and doesn't cleanup. I guess this affects any setup with
cpufreq_stats.
The attached patch seems to solve both symptoms and yes... it's quite
invasive as it introduce one more cpufreq policy notification (REMOVED).
BTW: the patch is against .21-rc4-mm1 but applies with some fuzz to
2.6.20 too
Alternatively, as it's just debug functionality, we could just
mark it unsafe for rmmod, which is nastier, but a lot less invasive
to the non-debug code.
Dave
--
http://www.codemonkey.org.uk
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- References:
- Oops after cd /sys/.../cpufreq/; rmmod; cat stats/time_in_state
- From: Alexey Dobriyan
- Re: Oops after cd /sys/.../cpufreq/; rmmod; cat stats/time_in_state
- From: Greg KH
- Re: Oops after cd /sys/.../cpufreq/; rmmod; cat stats/time_in_state
- From: Alexey Dobriyan
- Re: Oops after cd /sys/.../cpufreq/; rmmod; cat stats/time_in_state
- From: Greg KH
- Re: Oops after cd /sys/.../cpufreq/; rmmod; cat stats/time_in_state
- From: Dave Jones
- Re: Oops after cd /sys/.../cpufreq/; rmmod; cat stats/time_in_state
- From: Greg KH
- Re: Oops after cd /sys/.../cpufreq/; rmmod; cat stats/time_in_state
- From: Andrew Morton
- [PATCH] fix cpufreq_stats attrs removal
- From: Mattia Dongili
- Oops after cd /sys/.../cpufreq/; rmmod; cat stats/time_in_state
- Prev by Date: Re: [BUG] no boot with 2.6.21-rc3 and later
- Next by Date: Re: 2.6.20.3 AMD64 oops in CFQ code
- Previous by thread: Re: [PATCH] fix cpufreq_stats attrs removal
- Next by thread: Re: [PATCH] fix cpufreq_stats attrs removal
- Index(es):
Relevant Pages
|
