From: Avi Kivity <avi@redhat.com>
To: Gleb Natapov <gleb@redhat.com>
Cc: kvm@vger.kernel.org, mtosatti@redhat.com
Subject: Re: [PATCH 3/8] KVM: mark apic enabled on start up.
Date: Sun, 05 Aug 2012 17:39:33 +0300 [thread overview]
Message-ID: <501E85A5.9050108@redhat.com> (raw)
In-Reply-To: <20120805141713.GO27579@redhat.com>
On 08/05/2012 05:17 PM, Gleb Natapov wrote:
> On Sun, Aug 05, 2012 at 05:14:59PM +0300, Avi Kivity wrote:
>> On 08/05/2012 03:58 PM, Gleb Natapov wrote:
>> > According to SDM apic is enabled on start up.
>> >
>> > Signed-off-by: Gleb Natapov <gleb@redhat.com>
>> > ---
>> > arch/x86/kvm/lapic.c | 3 ++-
>> > 1 file changed, 2 insertions(+), 1 deletion(-)
>> >
>> > diff --git a/arch/x86/kvm/lapic.c b/arch/x86/kvm/lapic.c
>> > index 49f4ac0..c3f14fe 100644
>> > --- a/arch/x86/kvm/lapic.c
>> > +++ b/arch/x86/kvm/lapic.c
>> > @@ -1311,7 +1311,8 @@ int kvm_create_lapic(struct kvm_vcpu *vcpu)
>> > HRTIMER_MODE_ABS);
>> > apic->lapic_timer.timer.function = apic_timer_fn;
>> >
>> > - kvm_lapic_set_base(vcpu, APIC_DEFAULT_PHYS_BASE);
>> > + kvm_lapic_set_base(vcpu,
>> > + APIC_DEFAULT_PHYS_BASE | MSR_IA32_APICBASE_ENABLE);
>> >
>>
>> I'm guessing that in practice this is a no-op since qemu reset involves
>> programming this MSR.
>>
> Qemu is not the only userspace :) But this is here to avoid unneeded
> jump label patching truth to be told.
It's also correct, otherwise it wouldn't be here.
But won't the patching happen anyway? since it starts software disabled?
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2012-08-05 14:39 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-05 12:58 [PATCH 0/8] use jump labels to streamline common APIC configuration Gleb Natapov
2012-08-05 12:58 ` [PATCH 1/8] KVM: clean up kvm_(set|get)_apic_base Gleb Natapov
2012-08-05 12:58 ` [PATCH 2/8] KVM: use kvm_lapic_set_base() to change apic_base Gleb Natapov
2012-08-05 12:58 ` [PATCH 3/8] KVM: mark apic enabled on start up Gleb Natapov
2012-08-05 14:14 ` Avi Kivity
2012-08-05 14:17 ` Gleb Natapov
2012-08-05 14:39 ` Avi Kivity [this message]
2012-08-05 14:43 ` Gleb Natapov
2012-08-05 12:58 ` [PATCH 4/8] Export jump_label_rate_limit() Gleb Natapov
2012-08-05 14:16 ` Avi Kivity
2012-08-06 12:37 ` Jason Baron
2012-08-05 12:58 ` [PATCH 5/8] KVM: use jump label to optimize checking for HW enabled APIC in APIC_BASE MSR Gleb Natapov
2012-08-05 14:35 ` Avi Kivity
2012-08-05 14:42 ` Gleb Natapov
2012-08-05 14:48 ` Avi Kivity
2012-08-05 14:55 ` Gleb Natapov
2012-08-05 12:58 ` [PATCH 6/8] KVM: use jump label to optimize checking for SW enabled apic in spurious interrupt register Gleb Natapov
2012-08-05 12:58 ` [PATCH 7/8] KVM: use jump label to optimize checking for in kernel local apic presence Gleb Natapov
2012-08-05 12:58 ` [PATCH 8/8] KVM: inline kvm_apic_present() and kvm_lapic_enabled() Gleb Natapov
2012-08-05 13:33 ` [PATCH 0/8] use jump labels to streamline common APIC configuration Avi Kivity
2012-08-05 13:35 ` Gleb Natapov
2012-08-05 13:42 ` Avi Kivity
2012-08-05 13:48 ` Gleb Natapov
2012-08-05 14:00 ` Avi Kivity
2012-08-05 14:03 ` Gleb Natapov
2012-08-14 14:00 ` Jan Kiszka
2012-08-14 14:03 ` Gleb Natapov
2012-08-14 14:20 ` Jan Kiszka
2012-08-14 14:37 ` Gleb Natapov
2012-08-14 14:58 ` Jan Kiszka
2012-08-14 16:21 ` Avi Kivity
2012-08-14 16:38 ` Jan Kiszka
2012-08-14 17:00 ` Avi Kivity
2012-08-14 17:16 ` Jan Kiszka
2012-08-14 14:04 ` Avi Kivity
2012-08-14 14:05 ` Jan Kiszka
2012-08-14 14:08 ` Gleb Natapov
2012-08-14 14:07 ` Gleb Natapov
2012-08-14 14:13 ` Jan Kiszka
2012-08-14 14:44 ` Gleb Natapov
2012-08-14 15:09 ` Jan Kiszka
2012-08-05 19:30 ` Eric Northup
2012-08-06 8:35 ` Avi Kivity
2012-08-06 8:52 ` Gleb Natapov
2012-08-06 13:23 ` Avi Kivity
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=501E85A5.9050108@redhat.com \
--to=avi@redhat.com \
--cc=gleb@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.com \
/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).