[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <0677ed6e-280a-d2f3-d873-1daf99b39551@redhat.com>
Date: Mon, 31 Jul 2017 14:27:17 +0200
From: David Hildenbrand <david@...hat.com>
To: "Longpeng (Mike)" <longpeng2@...wei.com>
Cc: pbonzini@...hat.com, rkrcmar@...hat.com, agraf@...e.com,
borntraeger@...ibm.com, cohuck@...hat.com,
christoffer.dall@...aro.org, marc.zyngier@....com,
james.hogan@...tec.com, kvm@...r.kernel.org,
linux-kernel@...r.kernel.org, weidong.huang@...wei.com,
arei.gonglei@...wei.com, wangxinxin.wang@...wei.com,
longpeng.mike@...il.com
Subject: Re: [RFC] KVM: optimize the kvm_vcpu_on_spin
> I'm not sure whether the operation of get the vcpu's priority-level is
> expensive on all architectures, so I record it in kvm_sched_out() for
> minimal the extra cycles cost in kvm_vcpu_on_spin().
>
as you only care for x86 right now either way, you can directly optimize
here for the good (here: x86) case (keeping changes and therefore
possible bugs minimal).
--
Thanks,
David
Powered by blists - more mailing lists