Messages in this thread | | | Date | Wed, 12 Feb 2003 07:52:03 -0500 (EST) | From | Zwane Mwaikambo <> | Subject | VMWare monitor error on read/modify/write to cr4 |
| |
Hi, Current 2.5.60 has code which disables TSC access for tasks running in lower privelege level than ring0 when disabling kernel TSC usage. Doing a read, modify, write with only the TSD bit being set causes it to report a monitor error. This happens before console_init so it hangs on 'Uncompressing Linux... Ok booting the kernel'
To reproduce, build a 2.5.60 i586+ kernel and boot with notsc.
if (tsc_disable && cpu_has_tsc) { printk(KERN_NOTICE "Disabling TSC...\n"); /**** FIX-HPA: DOES THIS REALLY BELONG HERE? ****/ clear_bit(X86_FEATURE_TSC, boot_cpu_data.x86_capability); set_in_cr4(X86_CR4_TSD); }
This isn't a bug report, just an FYI for people using VMWare, and the TSC in vmware does work.
Zwane -- function.linuxpower.ca - 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/
| |