Received: by 10.213.65.68 with SMTP id h4csp84570imn; Mon, 26 Mar 2018 15:45:57 -0700 (PDT) X-Google-Smtp-Source: AG47ELt5rCBtPoQCIcT41Kge0mN7z0VsDktxly1+pKaIpGsOnBfo27ZJIDKHMqCB9D8yJvQz9IXF X-Received: by 2002:a17:902:43a4:: with SMTP id j33-v6mr23193738pld.260.1522104357572; Mon, 26 Mar 2018 15:45:57 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1522104357; cv=none; d=google.com; s=arc-20160816; b=VeIaODebTtn2kOZZpZ5Iqa8l43TfzJoLBA0bP5oRHqmvHDDSYuh6pPZi6NR0mQ0AZ6 Xp/JRNNdsvRtbi/UUrsXBzGoKH9z97z4czYVYsXOwW65qxYOmMF58ZUeZc7ERfNMiZ+2 Xp2uReBOZz5ds2uoApr2HAKw24k837uFG3oNzbjwP/rnxhMzWdzU2u1xpRHteHTJoExb tkwvaBT93VFFEzFvXXLETnqYHpmNz11sx9tz/9klZgMH6VK7u3/rK1sYWc+EBmAOyrjC wsW1NtkLP8ouZ53WN3EGBrDZuxxen7X6Ctf+cpHa+i1Ms3LU3EkqBfqxX3Jvk3lwNKq8 1pjA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:arc-authentication-results; bh=+yM0AkuuUDbjKRGH/mX0LAF68TP5jnJW8cCgnyzdQV0=; b=kKk6g+SWwS7tWmkqGOyDBRa3cs55KZ11DbHTVjaFHhlUr4lXODZMYk2js6cK6bNZ3t 5BqhwbNy3uTyjygipa0pD3uIwdKtvJ/1AH7J1M5Y19NEJrtNC+yUIMPVKbQC1uuxsvY0 MAh8mjBma14vy6sYx+6WB9t1Lz694Qm6+J/vYpVS2+pXneGnZ053/FCx8PVAdmi7jpnK /PXMH4B4WDlme3CSzVXp9bt2uuJOaYe6vfb0NvzU7zn/kuGzL1EmY/CinMLJsdbWH2IR l7/tjXYnj62ezeNbNNQpgYN9WEvJbOd+w1NNvIhTp+gkcJ/Olawrh0Tnqz0zY2rwYL/H 6Big== ARC-Authentication-Results: i=1; mx.google.com; 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id 61-v6si9591692plz.630.2018.03.26.15.45.42; Mon, 26 Mar 2018 15:45:57 -0700 (PDT) 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; 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752210AbeCZWov (ORCPT + 99 others); Mon, 26 Mar 2018 18:44:51 -0400 Received: from mx2.suse.de ([195.135.220.15]:45194 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752069AbeCZWot (ORCPT ); Mon, 26 Mar 2018 18:44:49 -0400 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (charybdis-ext.suse.de [195.135.220.254]) by mx2.suse.de (Postfix) with ESMTP id 6C503AF82; Mon, 26 Mar 2018 22:44:48 +0000 (UTC) Date: Mon, 26 Mar 2018 15:32:32 -0700 From: Davidlohr Bueso To: Wanpeng Li Cc: Peter Zijlstra , LKML , kvm , Paolo Bonzini , Radim Kr??m??? , Davidlohr Bueso Subject: Re: [PATCH 1/2] KVM: X86: Fix setup the virt_spin_lock_key before static key get initialized Message-ID: <20180326223232.ifaoc3zyjii4gq2f@linux-n805> References: <1521951444-5087-1-git-send-email-wanpengli@tencent.com> <20180326002732.qks4cp7qq2xzysnx@linux-n805> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: User-Agent: NeoMutt/20170421 (1.8.2) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 26 Mar 2018, Wanpeng Li wrote: >I didn't see any issue when testing this patch, could you elaborate >what's the bulky mechanism and how it conflicts with early smp bootup >stages? In addition, do you mean the xen fix is also not suitable? I have nothing against your patch (or the xen one for that matter), other than the fact that both seem like band-aid solutions to being able to move up the jump label init call. I was actually peddling a similar patch but didn't want to add the extra callback just for that -- at least xen already had smp_ops.smp_prepare_cpus. Instead of dropping the patches in -tip (ie: delaying the feature), I have nothing against these fixes being merged. If a better solution is available later, we can always move dealing with virt_spin_lock_key back into smp_prepare_boot_cpu(). Also a bit unrelated, but am I correct to assume that KVM_HINTS_DEDICATED can be used via qemu? I've only been dealing with kernel parameters. Thanks, Davidlohr