From: Jan Kiszka <jan.kiszka@siemens.com>
To: Stefan Priebe <s.priebe@profihost.ag>,
Paolo Bonzini <pbonzini@redhat.com>,
kvm@vger.kernel.org
Subject: Re: 3.10.X kernel/jump_label kvm
Date: Tue, 04 Mar 2014 11:01:18 +0100 [thread overview]
Message-ID: <5315A46E.7000509@siemens.com> (raw)
In-Reply-To: <5314C752.1070407@profihost.ag>
On 2014-03-03 19:17, Stefan Priebe wrote:
>
> Am 03.03.2014 17:36, schrieb Paolo Bonzini:
>> Il 28/02/2014 20:47, Stefan Priebe ha scritto:
>>> Hello,
>>>
>>> i got this stack trace multiple times while using a vanilla 3.10.32
>>> kernel and already sent it to the list in december but got no replies.
>>
>> Please try the patch of commit 0dce7cd67fd9055c4a2ff278f8af1431e646d346:
>
> Thanks - will try it. So this one should also go into 3.10.X
It's part of 3.10.29. Only .26..28 were affected by the regression below.
Jan
>> diff --git a/arch/x86/kvm/lapic.c b/arch/x86/kvm/lapic.c
>> index 1673940cf9c3..775702f649ca 100644
>> --- a/arch/x86/kvm/lapic.c
>> +++ b/arch/x86/kvm/lapic.c
>> @@ -1355,7 +1355,7 @@ void kvm_lapic_set_base(struct kvm_vcpu *vcpu, u64
>> value)
>> vcpu->arch.apic_base = value;
>>
>> /* update jump label if enable bit changes */
>> - if ((vcpu->arch.apic_base ^ value) & MSR_IA32_APICBASE_ENABLE) {
>> + if ((old_value ^ value) & MSR_IA32_APICBASE_ENABLE) {
>> if (value & MSR_IA32_APICBASE_ENABLE)
>> static_key_slow_dec_deferred(&apic_hw_disabled);
>> else
>>
>> Paolo
--
Siemens AG, Corporate Technology, CT RTC ITP SES-DE
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2014-03-04 10:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-28 19:47 3.10.X kernel/jump_label kvm Stefan Priebe
2014-03-01 14:27 ` Andrey Korolyov
2014-03-01 18:44 ` Stefan Priebe
2014-03-03 16:36 ` Paolo Bonzini
2014-03-03 18:17 ` Stefan Priebe
2014-03-03 18:20 ` Paolo Bonzini
2014-03-04 10:01 ` Jan Kiszka [this message]
2014-03-04 10:26 ` Stefan Priebe - Profihost AG
2014-03-04 11:21 ` Jan Kiszka
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=5315A46E.7000509@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=s.priebe@profihost.ag \
/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;
as well as URLs for NNTP newsgroup(s).