From: "Stephan Bärwolf" <stephan.baerwolf@tu-ilmenau.de>
To: Avi Kivity <avi@redhat.com>
Cc: linux-kernel@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: KVM guest-kernel panics double fault
Date: Tue, 10 Jan 2012 13:48:32 +0100 [thread overview]
Message-ID: <4F0C33A0.6080509@tu-ilmenau.de> (raw)
In-Reply-To: <4F0C3044.7050307@redhat.com>
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
prev parent reply other threads:[~2012-01-10 12:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-29 1:59 Stephan Bärwolf
2011-12-29 10:04 ` Avi Kivity
2012-01-08 2:31 ` Stephan Bärwolf
2012-01-08 10:21 ` Avi Kivity
2012-01-10 10:11 ` Stephan Bärwolf
2012-01-10 10:31 ` Avi Kivity
2012-01-10 12:17 ` Stephan Bärwolf
2012-01-10 12:34 ` Avi Kivity
2012-01-10 12:48 ` Stephan Bärwolf [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4F0C33A0.6080509@tu-ilmenau.de \
--to=stephan.baerwolf@tu-ilmenau.de \
--cc=avi@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome