Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1348979

Re: [PART1 RFC 5/9] svm: Add VMEXIT handlers for AVIC

From Paolo Bonzini <pbonzini@redhat.com>
Newsgroups linux.kernel
Subject Re: [PART1 RFC 5/9] svm: Add VMEXIT handlers for AVIC
Date 2016-03-03 12:00 +0100
Message-ID <r8z98-5Rb-37@gated-at.bofh.it> (permalink)
References (8 earlier) <r3z05-7H4-1@gated-at.bofh.it> <r3z9N-7KJ-47@gated-at.bofh.it> <r3zCP-8go-7@gated-at.bofh.it> <r3Apd-pQ-29@gated-at.bofh.it> <r8z98-5Rb-39@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw



On 03/03/2016 11:42, Suravee Suthikulpanit wrote:
> In facts, instead of setting up the vAPIC backing page address when
> calling kvm_arch_vcpu_load(), we should be able to do it when calling
> kvm_arch_vcpu_sched_in(). This seems more appropriate since the
> kvm_arch_vcpu_load() is also called in many unnecessary occasions via
> vcpu_load() (in the arch/x86/kvm/x86.c). The same goes for the
> kvm_arch_vcpu_put().
> 
> However, there is no kvm_arch_vcpu_sched_out(). But that can be added
> easily.
> 
> What do you think?

How much code is involved?  It seems an unnecessary complication...
Unless you can profile a difference, I would leave it in
kvm_arch_vcpu_load()/kvm_arch_vcpu_put().

Note that sched_in and sched_out are not called once per invocation of
KVM_RUN---only through the preempt notifiers.  So I'm not sure it is
enough to use sched_in and sched_out.

Paolo

Back to linux.kernel | Previous | Next | Find similar | Unroll thread


Thread

Re: [PART1 RFC 5/9] svm: Add VMEXIT handlers for AVIC Paolo Bonzini <pbonzini@redhat.com> - 2016-03-03 12:00 +0100

csiph-web