Received: by 10.223.164.200 with SMTP id h8csp620518wrb; Sun, 5 Nov 2017 16:56:41 -0800 (PST) X-Google-Smtp-Source: ABhQp+RB5L53lCZnkz6609DGYEDL98aB+e3r+1oY7uttDiDfuQhGiJkY8COokuutwU1e3VKGedXD X-Received: by 10.98.210.129 with SMTP id c123mr15009316pfg.77.1509929801004; Sun, 05 Nov 2017 16:56:41 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1509929800; cv=none; d=google.com; s=arc-20160816; b=mPDs4xpL1kX8juN5g46/15qmP0bAO4Pfl5UllRVzkRaYHLSFKgsKE4yaZgVspwUQV3 HqocXP1lR6owp/23qTxlXN++Dj8oQXTqbCO8EINVqmJ3ukA7Emo/aAglnd9TP0GUQqy3 Xft5j4Q6Vbn5F1PUO/evIRsFW0FpQhtQvzsmK0K7zcgBL9oa+jSWyBYYyPecm+pKIYlE nQ1gzPMq1OTQ74m/qr8KQEp6fmpJ3QsQyGrMpsHVzi5Dy+0IlZwoRFYRsevT4+dwnvQR fKr4c6JqcXZSEd/a0OHnryKXzHzEBL9c8pYDZJvVepDR+VMpmvg3biHlTjLKMfFFflgM U6LA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :message-id:date:subject:cc:to:from:dkim-signature :arc-authentication-results; bh=l5ymcnn7tpJHNTLRxFLT/SWXUBohHZWxKHP70sCKIq4=; b=VDKZ4bu4fAcH4bz+ScyiC3pg5w3aA8D/gUPKpSCwMxw8OQwjmBBje0YimJ3gD07/E6 eZu2i5xYxdgtVzbjOzYaJ9j2n6pE2lswx760XkLJou6jXIih5yWvpFKVGowTDAOGflwF XnTlhtiEVOGspeMWkNF7aKgDdA/iPyH0O1SH2WLdzbXOJ5+kUKZc16YFqHchjRSzu3ht MyIip3Hd+4uTIBM/B2+ljG4oX6ykDlUAgqSdGC87b/6SccR3JLXWu8UTzvjUJ0HjFuGL p1uNbx6sVB4ZHGa4v+xB9MZW9cqagjtCGy8mOuyRD59mHx62GVgdawr8ur0DTJuhAqPH 1JLQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=EaqH/2Cs; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id m21si10643371pgc.762.2017.11.05.16.56.27; Sun, 05 Nov 2017 16:56:40 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=EaqH/2Cs; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751593AbdKFAzb (ORCPT + 96 others); Sun, 5 Nov 2017 19:55:31 -0500 Received: from mail-pg0-f68.google.com ([74.125.83.68]:55791 "EHLO mail-pg0-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751550AbdKFAza (ORCPT ); Sun, 5 Nov 2017 19:55:30 -0500 Received: by mail-pg0-f68.google.com with SMTP id 15so6891004pgc.12; Sun, 05 Nov 2017 16:55:29 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:cc:subject:date:message-id:mime-version :content-transfer-encoding; bh=l5ymcnn7tpJHNTLRxFLT/SWXUBohHZWxKHP70sCKIq4=; b=EaqH/2Csa1oh6SgQVWnVuakpbAVOuiViF5ZokrywdB6qOscP11daR9qiQsbuIDJv+n 0inCHoVhr6/kDqI0PFwnjHQrOq+N+rDFxZNoUpIDdFw8sim481sDhInc4HzpsciXZ5rD tTh9nBkeJj3AJlYz9iFisc0YvFh84ft//2+/1zQSmt+E1j8hN8iywO4rtc0qSRXRumB7 +GXV0TtMn5ybWUF3qzgiUMbzkZYm46kgOjGLA3AnVFjF5cf3e09PnoBU7Kd0ZdYPCcHH BA/zKYiwWF5J4swS4GVpsG42QAzUzP/wW/mkBkqUkhsk9GYwomjxm4RFGhgzO0P4o/+J 19Bg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id:mime-version :content-transfer-encoding; bh=l5ymcnn7tpJHNTLRxFLT/SWXUBohHZWxKHP70sCKIq4=; b=tafb/ao0pbGrBBf7re+34jX3jCV2IjwE14qtPfYl/vp9RNz1PIQYRqsg5Ry2ibg0d3 oWUNbqN8LwdV65qjbs/FCUwdOmHizGzrFq95Y/w4+0iRebqjhKVMskX78lwJvj3mTK7J hf/ahjJoJG6lSiuj99E2ud+uM5ydhN00ypbLzJBh4kcbck1DhDMd8pcgb5AqQoVhc2uk jOR7Ds+JL9Ad/m9bhskpbtkNrVx7HqepqlH0HRgH76lJLV8dkN6Z2rOa/gmESc+wzMnv OUUzHQBW1jJPxJUr01wMlIt866jysaPj90fyNZJ3LnHemAHTL6q4aLfmkvryu/djrCyj p5sg== X-Gm-Message-State: AMCzsaX+nx35mrF7FrIV1u4pjQK0tFk3J2R4SWK397+3BtOo7dWBT7iJ szlsMPmrAEJ2l+zNpMsP5YQCtA== X-Received: by 10.99.145.73 with SMTP id l70mr13721133pge.132.1509929729336; Sun, 05 Nov 2017 16:55:29 -0800 (PST) Received: from localhost ([203.205.141.123]) by smtp.gmail.com with ESMTPSA id v22sm17469411pgb.65.2017.11.05.16.55.28 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 05 Nov 2017 16:55:28 -0800 (PST) From: Wanpeng Li X-Google-Original-From: Wanpeng Li To: linux-kernel@vger.kernel.org, kvm@vger.kernel.org Cc: Paolo Bonzini , =?UTF-8?q?Radim=20Kr=C4=8Dm=C3=A1=C5=99?= , Wanpeng Li Subject: [PATCH] KVM: X86: Fix softlockup when get the current kvmclock timestamp Date: Sun, 5 Nov 2017 16:55:21 -0800 Message-Id: <1509929721-3027-1-git-send-email-wanpeng.li@hotmail.com> X-Mailer: git-send-email 2.7.4 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Wanpeng Li watchdog: BUG: soft lockup - CPU#6 stuck for 22s! [qemu-system-x86:10185] CPU: 6 PID: 10185 Comm: qemu-system-x86 Tainted: G OE 4.14.0-rc4+ #4 RIP: 0010:kvm_get_time_scale+0x4e/0xa0 [kvm] Call Trace: ? get_kvmclock_ns+0xa3/0x140 [kvm] get_time_ref_counter+0x5a/0x80 [kvm] kvm_hv_process_stimers+0x120/0x5f0 [kvm] ? kvm_hv_process_stimers+0x120/0x5f0 [kvm] ? preempt_schedule+0x27/0x30 ? ___preempt_schedule+0x16/0x18 kvm_arch_vcpu_ioctl_run+0x4b4/0x1690 [kvm] ? kvm_arch_vcpu_load+0x47/0x230 [kvm] kvm_vcpu_ioctl+0x33a/0x620 [kvm] ? kvm_vcpu_ioctl+0x33a/0x620 [kvm] ? kvm_vm_ioctl_check_extension_generic+0x3b/0x40 [kvm] ? kvm_dev_ioctl+0x279/0x6c0 [kvm] do_vfs_ioctl+0xa1/0x5d0 ? __fget+0x73/0xa0 SyS_ioctl+0x79/0x90 entry_SYSCALL_64_fastpath+0x1e/0xa9 This can be reproduced when running kvm-unit-tests/hyperv_stimer.flat and cpu-hotplug stress simultaneously. kvm_get_time_scale() takes too long which results in softlockup. This patch fixes it by disabling preemption just for rdtsc() and __this_cpu_read() section in order to reduce preemption disable time, the per-CPU variable is just read operation and the master clock is active, so it is as safe as how it is used in kvm_guest_time_update(). Cc: Paolo Bonzini Cc: Radim Krčmář Signed-off-by: Wanpeng Li --- arch/x86/kvm/x86.c | 13 +++++++++---- 1 file changed, 9 insertions(+), 4 deletions(-) diff --git a/arch/x86/kvm/x86.c b/arch/x86/kvm/x86.c index 34c85aa..2542f9b 100644 --- a/arch/x86/kvm/x86.c +++ b/arch/x86/kvm/x86.c @@ -1781,6 +1781,7 @@ u64 get_kvmclock_ns(struct kvm *kvm) struct kvm_arch *ka = &kvm->arch; struct pvclock_vcpu_time_info hv_clock; u64 ret; + unsigned long this_tsc_khz, host_tsc; spin_lock(&ka->pvclock_gtod_sync_lock); if (!ka->use_master_clock) { @@ -1795,13 +1796,17 @@ u64 get_kvmclock_ns(struct kvm *kvm) /* both __this_cpu_read() and rdtsc() should be on the same cpu */ get_cpu(); - kvm_get_time_scale(NSEC_PER_SEC, __this_cpu_read(cpu_tsc_khz) * 1000LL, - &hv_clock.tsc_shift, - &hv_clock.tsc_to_system_mul); - ret = __pvclock_read_cycles(&hv_clock, rdtsc()); + this_tsc_khz = __this_cpu_read(cpu_tsc_khz); + host_tsc = rdtsc(); put_cpu(); + /* With all the info we got, fill in the values */ + kvm_get_time_scale(NSEC_PER_SEC, this_tsc_khz * 1000LL, + &hv_clock.tsc_shift, + &hv_clock.tsc_to_system_mul); + ret = __pvclock_read_cycles(&hv_clock, host_tsc); + return ret; } -- 2.7.4 From 1585210154446734797@xxx Mon Nov 27 09:16:50 +0000 2017 X-GM-THRID: 1585016442219507132 X-Gmail-Labels: Inbox,Category Forums,HistoricalUnread