[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4F0C2C4E.3000703@tu-ilmenau.de>
Date: Tue, 10 Jan 2012 13:17:18 +0100
From: Stephan Bärwolf <stephan.baerwolf@...ilmenau.de>
To: Avi Kivity <avi@...hat.com>
CC: linux-kernel@...r.kernel.org,
Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: KVM guest-kernel panics double fault
Hi, me again.
Thank you for your instructions, I will send the patch right after this
mail.
On 01/10/12 11:31, 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")
>>> Please post patches separately, not as attachments to a single email.
>>> See Documentation/SubmittingPatches.
>> One thing, which is not fully clear to me: Where exactly should I post
>> the patches?
>> Also to/in this mail/group as an empty mail (containing the patch as
>> text-body) per patch?
>> Or all (3 patches) at once?
> One patch per email, with a cover letter. Git can help you format and
> send them:
>
> # format three patches, with a cover letter:
> $ git format-patch -3 --cover-letter -n -o patches
> # edit the cover letter:
> $ vi patches/0000-cover-letter-patch
> # post them:
> $ git send-email --to kvm@...r.kernel.org patches/*.patch
>
Thx, I'll do it this way...
regards Stephan
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists