From: Liang Chen <liangchen.linux@gmail.com>
To: stable@vger.kernel.org
Cc: mtosatti@redhat.com, pbonzini@redhat.com, lizefan@huawei.com,
gregkh@linuxfoundation.org, jslaby@suse.cz,
sasha.levin@oracle.com
Subject: [PATCH] KVM: x86: move steal time initialization to vcpu entry time
Date: Fri, 11 Mar 2016 16:53:11 +0800 [thread overview]
Message-ID: <1457686391-17855-1-git-send-email-liangchen.linux@gmail.com> (raw)
From: Marcelo Tosatti <mtosatti@redhat.com>
commit 7cae2bedcbd4680b155999655e49c27b9cf020fa upstream
This patch is needed on lts 3.4, 3.10, 3.12, 3.14, 3.18, and 4.1 for
the same issue. Can you please to pick it up?
As reported at https://bugs.launchpad.net/qemu/+bug/1494350,
it is possible to have vcpu->arch.st.last_steal initialized
from a thread other than vcpu thread, say the iothread, via
KVM_SET_MSRS.
Which can cause an overflow later (when subtracting from vcpu threads
sched_info.run_delay).
To avoid that, move steal time accumulation to vcpu entry time,
before copying steal time data to guest.
Signed-off-by: Marcelo Tosatti <mtosatti@redhat.com>
Reviewed-by: David Matlack <dmatlack@google.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
---
arch/x86/kvm/x86.c | 9 ++-------
1 file changed, 2 insertions(+), 7 deletions(-)
diff --git a/arch/x86/kvm/x86.c b/arch/x86/kvm/x86.c
index d6e8bd0..7d4f352 100644
--- a/arch/x86/kvm/x86.c
+++ b/arch/x86/kvm/x86.c
@@ -1987,6 +1987,8 @@ static void accumulate_steal_time(struct kvm_vcpu *vcpu)
static void record_steal_time(struct kvm_vcpu *vcpu)
{
+ accumulate_steal_time(vcpu);
+
if (!(vcpu->arch.st.msr_val & KVM_MSR_ENABLED))
return;
@@ -2120,12 +2122,6 @@ int kvm_set_msr_common(struct kvm_vcpu *vcpu, struct msr_data *msr_info)
if (!(data & KVM_MSR_ENABLED))
break;
- vcpu->arch.st.last_steal = current->sched_info.run_delay;
-
- preempt_disable();
- accumulate_steal_time(vcpu);
- preempt_enable();
-
kvm_make_request(KVM_REQ_STEAL_UPDATE, vcpu);
break;
@@ -2808,7 +2804,6 @@ void kvm_arch_vcpu_load(struct kvm_vcpu *vcpu, int cpu)
vcpu->cpu = cpu;
}
- accumulate_steal_time(vcpu);
kvm_make_request(KVM_REQ_STEAL_UPDATE, vcpu);
}
--
1.9.1
next reply other threads:[~2016-03-11 8:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-11 8:53 Liang Chen [this message]
2016-03-13 3:49 ` [PATCH] KVM: x86: move steal time initialization to vcpu entry time Greg KH
2016-03-14 0:41 ` Zefan Li
2016-03-15 11:37 ` Luis Henriques
-- strict thread matches above, loose matches on Subject: below --
2015-10-14 22:33 Marcelo Tosatti
2015-10-15 17:10 ` David Matlack
2015-10-16 8:34 ` Paolo Bonzini
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=1457686391-17855-1-git-send-email-liangchen.linux@gmail.com \
--to=liangchen.linux@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.cz \
--cc=lizefan@huawei.com \
--cc=mtosatti@redhat.com \
--cc=pbonzini@redhat.com \
--cc=sasha.levin@oracle.com \
--cc=stable@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.