Hi folks. I was just thinking about how that CPUID change caused problems when running ChromeOS, and it occurred to me that it doesn't matter what gem5 supports when CPUID is run if the host system doesn't support the features it claims. To be really safe, when running with KVM, we should report at most the features the host supports, as much as that's possible. That could cause a problem, though, if gem5 supports a feature that the host system doesn't. We'd either have to consistently disable that feature if KVM is used, the feature bits reported by CPUID would change depending on what CPU was being used, or we'd just have to hope the simulated system didn't use the feature when under KVM.
Food for thought. Gabe _______________________________________________ gem5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/gem5-dev
