Messages in this thread | | | Date | Tue, 10 Jan 2012 13:48:32 +0100 | From | Stephan Bärwolf <> | Subject | Re: KVM guest-kernel panics double fault |
| |
On 01/10/12 13:34, Avi Kivity wrote: > I prepare/adapt everything to the mentioned styles/policy. > (I'll insert 2 additional ops for getting "cpuid" and "id of vcpu"...) >>> What do you mean by "id of vcpu"? >> I mean the number of the corresponding vcpu. >> (So mostly "vcpu->vcpu_id" ...) >> It is necessary for "pr_err_ratelimited"-complains, if cpuid-vendor is >> unknown ... >> ("Jan 10 12:14:55 thinkrat kernel: [ 4476.484359] kvm: 15680: cpu0 >> unknown vendor - assuming intel") > It isn't worthwhile - just don't print the vcpu number (the task ID > contains enough information, and anyway this should be rare to the point > of never ever happening) >
The message itself can be user-triggered ("-cpu core2duo,vendor=StephansQemu"), but you are right. Normally all cpus got the same cpuid, so it shouln't interest which one had the unknown vendor...
...fixing it and then sending...
regards Stephan
-- Dipl.-Inf. Stephan Bärwolf Ilmenau University of Technology, Integrated Communication Systems Group Phone: +49 (0)3677 69 4130 Email: stephan.baerwolf@tu-ilmenau.de, Web: http://www.tu-ilmenau.de/iks
-- 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/
| |