Received: by 10.223.164.202 with SMTP id h10csp386382wrb; Wed, 8 Nov 2017 18:53:08 -0800 (PST) X-Google-Smtp-Source: ABhQp+SIcFLCupXMWh0NF2jh/Rd27Lx3V6ImxBOk49WfeTtYrqYtshzmsZh00b5UDYz5aNPNXhlF X-Received: by 10.99.109.2 with SMTP id i2mr2325550pgc.194.1510195988600; Wed, 08 Nov 2017 18:53:08 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1510195988; cv=none; d=google.com; s=arc-20160816; b=Cq/c/wADB9WhJVEVQtZ0DaSQNACGa/sGQdxytiIRM+ILYwSkFtZ1koeopHswIIdxpf MaO3xorIWjAOg4g7Tvyns7naaRM5ujE44NMsrEeZx4LwlSBBPYoaPzCFZDP86gqGmgvx Drc2AUhX3/leWRf/dri3EW4tCqeJiUgnKC/oMPV4AMPG0VBycYR622h2xvpKFP9HRlAF sZpnITZ78LlRtF9j+IBOTWfU0MiF3ROTOvj8K8GGYQtHYD3O0tiJBAe+noQ+PTT0YNx2 rOk1p+oiwdHkNNqQU8fDf9uZdWN9r7ixfdpSxfWDUjZZhmmj/Odg4vnOcFZ5DI42wcTe jFuw== 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=mYGZ5Yw3Qi/T0h4O/Q8dyXbsHRRr00kMTXWtwqa+hWI=; b=xbgM6dZOfZTDuiCyrTZJAzQ39V7JEMz4EJejkcorPtXoV2/ZPfGTq81B83TjRsqjra PHk8k1UE/JqfQ9622k3cpBSHoCACl/sp2AhmVhMKQ1hXNrexzTHX+m+ZIHrBEIAtQ4WU OiSnxNc+KHLPiy+bzpItVw1nQebpsO/c/txOCyHYAlRga6ubNpu87LgQ9jvXbU639bXx QrXrNgMfNeKDM4u0PowflVJoFErUkeOEXMUNe9lyCX9A5ixD3tNzM8fV9RGMLV0tjt3v cjvr5dOadqP2CKWWIsPg3Cfpb7btrJ2XyPVsgqZvg3Ke+Pne88tyIqVFRsrprXR1bBQO 6kaw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=qz9kFbR8; 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 e3si1110186pld.771.2017.11.08.18.52.56; Wed, 08 Nov 2017 18:53:08 -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=qz9kFbR8; 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 S1752114AbdKICwS (ORCPT + 82 others); Wed, 8 Nov 2017 21:52:18 -0500 Received: from mail-pf0-f194.google.com ([209.85.192.194]:52341 "EHLO mail-pf0-f194.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751470AbdKICwQ (ORCPT ); Wed, 8 Nov 2017 21:52:16 -0500 Received: by mail-pf0-f194.google.com with SMTP id e64so3238517pfk.9; Wed, 08 Nov 2017 18:52:16 -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=mYGZ5Yw3Qi/T0h4O/Q8dyXbsHRRr00kMTXWtwqa+hWI=; b=qz9kFbR8j99+P9Vzi8VJQdUDurJRubmaaMSHtKE5U4BIQLWGik1A5goPaaSOoVjGc3 p9pD1XfCa1gpC8XUuHxqqZlpocA7sJzZErwHRKxySASq5J9uSaOPaxyjsMqjj6+yGkL7 gDSORH3ozQOcjAP5mTUP76e9qYNb6tKI/9toSa62DgcATyXcXKC00aGsyvOFq5UWzi5+ 9emFfUnFRgg6t5Tt9iCPygsl4Ujyi96plsMBV23VvIbqJu5hJlTnx5USwmDMSQzM3jWK sgsLMlFMY6hX4v/B+WO5g4bqG2wBsczTmmTxiQx1U9ERxkCXDbXLOA4ze/s6jCao6aex k2iQ== 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=mYGZ5Yw3Qi/T0h4O/Q8dyXbsHRRr00kMTXWtwqa+hWI=; b=eQ7xFOKJCWjdzUSqObIkE9nGkOtl9iGVhLf6NFoeBt1NscaBUCxJ+pO0l/6xxpFRk6 0Ay79cdNhj5bbOiBLO5LzWTgQUV8evy4drl4ScT9OhZ/W5HmTXu52T71FQmzMRFWrGgn rsmfMLeXOPKLkfKVDsYQHfb/wAeel2oHti2gUupxQTXl5iV43Niz79tuXd1aUII9UdZG pAqxrMMlhoEoRBu3uUEHIfjq0oJJD1xUCX/w10is5xRphQW05XvwziwdGfDJzySeBNe/ Mmb9hP+42v4MTG9h7gEMryEYDucaa9nnx8pdK/4avca/zQcWWJIl5eAmQSar6pliScvJ jt1g== X-Gm-Message-State: AJaThX4oVYQbbpRFOHxnIcdg0EQSxzPUNVZPPAHjsG5Nn5KRqgioNw2S rRFt2ErUMgGktm0PJCKjYz4kew== X-Received: by 10.98.109.134 with SMTP id i128mr236586pfc.66.1510195935745; Wed, 08 Nov 2017 18:52:15 -0800 (PST) Received: from localhost ([203.205.141.123]) by smtp.gmail.com with ESMTPSA id d6sm9918401pfc.29.2017.11.08.18.52.14 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 08 Nov 2017 18:52:15 -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 v3] KVM: X86: Fix softlockup when get the current kvmclock Date: Wed, 8 Nov 2017 18:52:12 -0800 Message-Id: <1510195932-6232-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. __this_cpu_read(cpu_tsc_khz) returns 0 (set in kvmclock_cpu_down_prep()) when the pCPU is unhotplug which results in kvm_get_time_scale() gets into an infinite loop. This patch fixes it by treating the unhotplug pCPU as not using master clock. Cc: Paolo Bonzini Cc: Radim Krčmář Signed-off-by: Wanpeng Li --- arch/x86/kvm/x86.c | 11 +++++++---- 1 file changed, 7 insertions(+), 4 deletions(-) diff --git a/arch/x86/kvm/x86.c b/arch/x86/kvm/x86.c index 03869eb..d61dcce3 100644 --- a/arch/x86/kvm/x86.c +++ b/arch/x86/kvm/x86.c @@ -1795,10 +1795,13 @@ 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()); + if (__this_cpu_read(cpu_tsc_khz)) { + 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()); + } else + ret = ktime_get_boot_ns() + ka->kvmclock_offset; put_cpu(); -- 2.7.4 From 1584195121553377423@xxx Thu Nov 16 04:23:19 +0000 2017 X-GM-THRID: 1584195121553377423 X-Gmail-Labels: Inbox,Category Forums,HistoricalUnread