Messages in this thread | | | Subject | RE: Fixing MTRR smp breakage and suspending sysdevs. | Date | Fri, 29 Oct 2004 09:41:03 +0800 | From | "Li, Shaohua" <> |
| |
>> >> Is the problem MTRR resume must be with IRQ enabled, right? Could we >> >> implement a method sysdev resume with IRQ enabled? MTRR driver isn't >> >> the >> > >> >MTRR does not deserve to be sysdev. It is not essential for the >> >system, it only makes it slow. >> It's a CPU driver, cpufreq driver is the same. > >Well, it drives part of cpu. Fortunately that part of cpu is not required >for >other drivers. cpufreq definitely should not be sysdev. If mtrr is not >needed for drivers (I think it is not), it should not be a sysdev. mtrr can not be a sysdev, but this is current cpufreq driver model. I guess you need convince Dominik.
Thanks, Shaohua - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |