Received: by 2002:a25:824b:0:0:0:0:0 with SMTP id d11csp4954308ybn; Sat, 28 Sep 2019 10:26:16 -0700 (PDT) X-Google-Smtp-Source: APXvYqxx0NPMVu7XR6aOi7n0nxH7ka2yfporS9F2GGKJIXh3Iesb/tvt9Hhff6PxWDeGu9K8bsAT X-Received: by 2002:a50:99da:: with SMTP id n26mr10948564edb.293.1569691576240; Sat, 28 Sep 2019 10:26:16 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1569691576; cv=none; d=google.com; s=arc-20160816; b=gciXHwKZAQCElkpfz63JeFDqotKZfx4Oxpx40GrMiNAGYZzFkW4ZRhPQESUulDWRvs Cs068dOuaOilabXLiqMcxAB3N2z+wFQ4BnxSmQP1GStx/sNYTbMrIhZvlYey7BbMwQpK ka2MGoBAmz4l/Cd+jdvt4KU18wrEJgSD+nU1T/Vj33j7MFG2pH93XcqybKJ7i1Ck8Y2J xESLflQtaw4rqEfWSS0h4xMCpwLQLeRe6nm6xxlRm2HeVwsjMtvACRX9JaOk9s/dTA9+ QgSp7yQCk7LzSYK83msAzX90OBkz+lWLf5bm+aKbzBywLkGlI+rxiB2CdXe1nPDpkza9 pBuw== 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 :references:in-reply-to:message-id:date:subject:cc:to:from; bh=MVFU4ua+XpP0w/X98EWrlH3YulwyGgzDoAOCdELPTTU=; b=meGKbAdFQ5vJajQT0shNBUqQeqOu+oqi4pYN0inenYO/DtlEFz8ZbCdnTWsqhR3PdI PouCCkXNwtXxcq/cUD8/sD9XBhwQ57nu3i9QOcE/TpomZz5yIv5xvMnEhmMAXOxCzTY0 hi3uG9KiXKA/B7JOB7ezp1h0/ZlGWEzJIOXPexy6WHzffmver1J2TYr8AVBwllrboVgP itkspAsZ9XATAwJHF0yULmD3kHaCwi8kWt17WMICyXfPBV+Hcc+VriUEHjpLSuyfh1Gp T6P0IEKXicKM0k7TgtTbFjz4Y2tByTLHsuvgt4qPETqZloFrKko5j+m+1JBpQy4BoZE7 kZwg== 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id g21si3820963edq.289.2019.09.28.10.25.52; Sat, 28 Sep 2019 10:26:16 -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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729061AbfI1RYa (ORCPT + 99 others); Sat, 28 Sep 2019 13:24:30 -0400 Received: from mx1.redhat.com ([209.132.183.28]:59544 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728705AbfI1RXZ (ORCPT ); Sat, 28 Sep 2019 13:23:25 -0400 Received: from smtp.corp.redhat.com (int-mx03.intmail.prod.int.phx2.redhat.com [10.5.11.13]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 6480F3091761; Sat, 28 Sep 2019 17:23:25 +0000 (UTC) Received: from mail (ovpn-125-159.rdu2.redhat.com [10.10.125.159]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 436B360600; Sat, 28 Sep 2019 17:23:25 +0000 (UTC) From: Andrea Arcangeli To: kvm@vger.kernel.org, linux-kernel@vger.kernel.org Cc: Paolo Bonzini , Vitaly Kuznetsov , Sean Christopherson Subject: [PATCH 07/14] KVM: monolithic: x86: remove __init section prefix from kvm_x86_cpu_has_kvm_support Date: Sat, 28 Sep 2019 13:23:16 -0400 Message-Id: <20190928172323.14663-8-aarcange@redhat.com> In-Reply-To: <20190928172323.14663-1-aarcange@redhat.com> References: <20190928172323.14663-1-aarcange@redhat.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Scanned-By: MIMEDefang 2.79 on 10.5.11.13 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.41]); Sat, 28 Sep 2019 17:23:25 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Adjusts the section prefixes of some KVM x86 code function because with the monolithic KVM model the section checker can now do a more accurate static analysis at build time. This also allows to build without CONFIG_SECTION_MISMATCH_WARN_ONLY=n. The __init needs to be removed on vmx despite it's only svm calling it from kvm_x86_hardware_enable which is eventually called by hardware_enable_nolock() or there's a (potentially false positive) warning (false positive because this function isn't called in the vmx case). If this isn't needed the right cleanup isn't to put it in the __init section, but to drop it. As long as it's defined in vmx as a kvm_x86 operation, it's expectable that might eventually be called at runtime while hot plugging new CPUs. Signed-off-by: Andrea Arcangeli --- arch/x86/include/asm/kvm_host.h | 2 +- arch/x86/kvm/vmx/vmx.c | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/arch/x86/include/asm/kvm_host.h b/arch/x86/include/asm/kvm_host.h index 0ae65148e5ed..75affbf7861b 100644 --- a/arch/x86/include/asm/kvm_host.h +++ b/arch/x86/include/asm/kvm_host.h @@ -1002,7 +1002,7 @@ struct kvm_lapic_irq { bool msi_redir_hint; }; -extern __init int kvm_x86_cpu_has_kvm_support(void); +extern int kvm_x86_cpu_has_kvm_support(void); extern __init int kvm_x86_disabled_by_bios(void); extern int kvm_x86_hardware_enable(void); extern void kvm_x86_hardware_disable(void); diff --git a/arch/x86/kvm/vmx/vmx.c b/arch/x86/kvm/vmx/vmx.c index 2ae162eb082e..faccffc4709e 100644 --- a/arch/x86/kvm/vmx/vmx.c +++ b/arch/x86/kvm/vmx/vmx.c @@ -2094,7 +2094,7 @@ void kvm_x86_cache_reg(struct kvm_vcpu *vcpu, enum kvm_reg reg) } } -__init int kvm_x86_cpu_has_kvm_support(void) +int kvm_x86_cpu_has_kvm_support(void) { return cpu_has_vmx(); }