Received: by 2002:a05:6358:d09b:b0:dc:cd0c:909e with SMTP id jc27csp257995rwb; Wed, 9 Nov 2022 23:55:14 -0800 (PST) X-Google-Smtp-Source: AMsMyM72IrXmcaZh9TVpe6B6l4ozM2/z0I1BJP6qlcLlk3cxskoxVhsy9bhzP07TLhNHTPoTFE2f X-Received: by 2002:a17:906:7048:b0:7ae:db2:f10a with SMTP id r8-20020a170906704800b007ae0db2f10amr2286134ejj.709.1668066913786; Wed, 09 Nov 2022 23:55:13 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1668066913; cv=none; d=google.com; s=arc-20160816; b=icY6g43HGN+uP4PjPoke07JgYV+xUKFylsqtb/KwIW4DEITGFHLME8srt0Hm/BZS0e USeAoAEmXEi9pbT8CIbXK84Fotp6FouOk/lEkBTqmPPX0FbYcvyzcoAMBKT96Pxs6Ujj eFv/h2pGOFkmyEG5VSyVJY4uku/eWPX5AfBlWdhfzlXKRxJeCloTHc0QnZbp+e8BI+7A J/a4NraZfxFO0YGcv/JlDihwm+HIoYCQpA06fg42Lg+bRMO+ge/Ou7BLuyWM8gAhqDwv BoYTYxjm3ZCnAC5GQXdvoNQEqoj1pUKRCd9mVyi3VSwcWRGUOHSgJtdmY5WzkafNZbRE ltYw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :references:in-reply-to:date:cc:to:from:subject:message-id :dkim-signature; bh=4HMrnjrEUvFoZ4t20nqQmzd6JnuejTnfnu+sOhM4s2Y=; b=US59Jud/D12vqtTCmwoKDxhoa8ZTYFk4fdJkocVl5iJx4Ev6rLpMYCPLETVd1DvLQ9 XGuUz5EQNGogaGRzFWh/x+EnAI9COhW5ZX5XWL8+XeBCBd8ZKI8hvBJ8pB7DRHriGKAS jCXYoMm0jSC1DmSdDW8PlPGxo81cEDLbUWIFwuvyOWD2hpXtprzQP0SYcujBKN76yGZE iH5EPgxb7PyYfztLyBxoG6A7myUUG49fBrQwqKn7/2QjUGb0XbNKAOc65pkJrN/OcAPa EMnOObu2DtCd+I0MsUogHcH7FH3jLutTnL12yxtpB7u2g6IEb329rpZ7BqgsSnRgE5r/ dmXw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b=SR6T61f5; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id q23-20020a056402249700b0045a3b951e8bsi18576199eda.194.2022.11.09.23.54.28; Wed, 09 Nov 2022 23:55:13 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b=SR6T61f5; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232848AbiKJHcD (ORCPT + 93 others); Thu, 10 Nov 2022 02:32:03 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:48066 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232881AbiKJHbz (ORCPT ); Thu, 10 Nov 2022 02:31:55 -0500 Received: from mga04.intel.com (mga04.intel.com [192.55.52.120]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 783EF32B82; Wed, 9 Nov 2022 23:31:53 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1668065513; x=1699601513; h=message-id:subject:from:to:cc:date:in-reply-to: references:mime-version:content-transfer-encoding; bh=K4DExVACpt2lARFBBsyLRbh7EHo+YwPLCynabZeKIUc=; b=SR6T61f5Ot3dK2IU86mrDqzqV6tF4R6lOlNUT7aGnKENyhzAvENoDFKP zkPqsK/DBY01EaiBq41Y2BSxrMYv4lu+l8KZ7Nh37UfJP9wVRPpsVagkV N1gCmsGZUhq1W/lFX7AOiJXfP/+kC6+zA+1BpOQQkHzSgC+QYLfHbLsdp f8EhkmDrKIXpZ/ljJdCMcHr5gkZ3KOj22SLkMtyUgrMl9OI59+JS6rJou SpSG0MlMDGtUT04jdMgjQCBj8m/JvcOepdQnf0mIKY7zw+IPehiXGjRx7 8WjZNvRJzpccv8GgWa/HgLNcI0yr2Je5HnQBvigr4Cp7hh5kWTROk9OJA w==; X-IronPort-AV: E=McAfee;i="6500,9779,10526"; a="309952072" X-IronPort-AV: E=Sophos;i="5.96,153,1665471600"; d="scan'208";a="309952072" Received: from orsmga007.jf.intel.com ([10.7.209.58]) by fmsmga104.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 09 Nov 2022 23:31:53 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=McAfee;i="6500,9779,10526"; a="631556568" X-IronPort-AV: E=Sophos;i="5.96,153,1665471600"; d="scan'208";a="631556568" Received: from sqa-gate.sh.intel.com (HELO robert-ivt.tsp.org) ([10.239.48.212]) by orsmga007.jf.intel.com with ESMTP; 09 Nov 2022 23:31:43 -0800 Message-ID: Subject: Re: [PATCH 32/44] KVM: x86: Unify pr_fmt to use module name for all KVM modules From: Robert Hoo To: Sean Christopherson , Paolo Bonzini , Marc Zyngier , Huacai Chen , Aleksandar Markovic , Anup Patel , Paul Walmsley , Palmer Dabbelt , Albert Ou , Christian Borntraeger , Janosch Frank , Claudio Imbrenda , Matthew Rosato , Eric Farman , Vitaly Kuznetsov Cc: James Morse , Alexandru Elisei , Suzuki K Poulose , Oliver Upton , Atish Patra , David Hildenbrand , kvm@vger.kernel.org, linux-arm-kernel@lists.infradead.org, kvmarm@lists.linux.dev, kvmarm@lists.cs.columbia.edu, linux-mips@vger.kernel.org, linuxppc-dev@lists.ozlabs.org, kvm-riscv@lists.infradead.org, linux-riscv@lists.infradead.org, linux-s390@vger.kernel.org, linux-kernel@vger.kernel.org, Isaku Yamahata , Fabiano Rosas , Michael Ellerman , Chao Gao , Thomas Gleixner , Yuan Yao Date: Thu, 10 Nov 2022 15:31:42 +0800 In-Reply-To: <20221102231911.3107438-33-seanjc@google.com> References: <20221102231911.3107438-1-seanjc@google.com> <20221102231911.3107438-33-seanjc@google.com> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.28.5 (3.28.5-10.el7) Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-4.3 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_EF,RCVD_IN_DNSWL_MED,SPF_HELO_NONE, SPF_NONE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 2022-11-02 at 23:18 +0000, Sean Christopherson wrote: > Define pr_fmt using KBUILD_MODNAME for all KVM x86 code so that > printks > use consistent formatting across common x86, Intel, and AMD code. In > addition to providing consistent print formatting, using > KBUILD_MODNAME, > e.g. kvm_amd and kvm_intel, allows referencing SVM and VMX (and SEV > and > SGX and ...) as technologies without generating weird messages, and > without causing naming conflicts with other kernel code, e.g. "SEV: > ", > "tdx: ", "sgx: " etc.. are all used by the kernel for non-KVM > subsystems. > > Opportunistically move away from printk() for prints that need to be > modified anyways, e.g. to drop a manual "kvm: " prefix. > > Opportunistically convert a few SGX WARNs that are similarly modified > to > WARN_ONCE; in the very unlikely event that the WARNs fire, odds are > good > that they would fire repeatedly and spam the kernel log without > providing > unique information in each print. > > Note, defining pr_fmt yields undesirable results for code that uses > KVM's > printk wrappers, e.g. vcpu_unimpl(). But, that's a pre-existing > problem > as SVM/kvm_amd already defines a pr_fmt, and thankfully use of KVM's > wrappers is relatively limited in KVM x86 code. > > Signed-off-by: Sean Christopherson > --- > arch/x86/kvm/cpuid.c | 1 + > arch/x86/kvm/debugfs.c | 2 ++ > arch/x86/kvm/emulate.c | 1 + > arch/x86/kvm/hyperv.c | 1 + > arch/x86/kvm/i8254.c | 4 ++-- > arch/x86/kvm/i8259.c | 4 +++- > arch/x86/kvm/ioapic.c | 1 + > arch/x86/kvm/irq.c | 1 + > arch/x86/kvm/irq_comm.c | 7 +++--- > arch/x86/kvm/kvm_onhyperv.c | 1 + > arch/x86/kvm/lapic.c | 8 +++---- > arch/x86/kvm/mmu/mmu.c | 6 ++--- > arch/x86/kvm/mmu/page_track.c | 1 + > arch/x86/kvm/mmu/spte.c | 4 ++-- > arch/x86/kvm/mmu/spte.h | 4 ++-- > arch/x86/kvm/mmu/tdp_iter.c | 1 + > arch/x86/kvm/mmu/tdp_mmu.c | 1 + > arch/x86/kvm/mtrr.c | 1 + > arch/x86/kvm/pmu.c | 1 + > arch/x86/kvm/smm.c | 1 + > arch/x86/kvm/svm/avic.c | 2 +- > arch/x86/kvm/svm/nested.c | 2 +- > arch/x86/kvm/svm/pmu.c | 2 ++ > arch/x86/kvm/svm/sev.c | 1 + > arch/x86/kvm/svm/svm.c | 10 ++++----- > arch/x86/kvm/svm/svm_onhyperv.c | 1 + > arch/x86/kvm/svm/svm_onhyperv.h | 4 ++-- > arch/x86/kvm/vmx/evmcs.c | 1 + > arch/x86/kvm/vmx/evmcs.h | 4 +--- > arch/x86/kvm/vmx/nested.c | 3 ++- > arch/x86/kvm/vmx/pmu_intel.c | 5 +++-- > arch/x86/kvm/vmx/posted_intr.c | 2 ++ > arch/x86/kvm/vmx/sgx.c | 5 +++-- > arch/x86/kvm/vmx/vmcs12.c | 1 + > arch/x86/kvm/vmx/vmx.c | 40 ++++++++++++++++--------------- > -- > arch/x86/kvm/vmx/vmx_ops.h | 4 ++-- > arch/x86/kvm/x86.c | 28 ++++++++++++----------- > arch/x86/kvm/xen.c | 1 + > 38 files changed, 97 insertions(+), 70 deletions(-) > After this patch set, still find some printk()s left in arch/x86/kvm/*, consider clean all of them up? arch/x86/kvm/lapic.c:1215: printk(KERN_ERR "TODO: unsupported delivery mode %x\n", arch/x86/kvm/lapic.c:1506: printk(KERN_ERR "Local APIC read with len = %x, " arch/x86/kvm/lapic.c:2586: printk(KERN_ERR "malloc apic regs error for vcpu %x\n", arch/x86/kvm/ioapic.h:95: printk(KERN_EMERG "assertion failed %s: %d: %s\n", \ arch/x86/kvm/ioapic.c:614: printk(KERN_WARNING "ioapic: wrong length %d\n", len); arch/x86/kvm/ioapic.c:641: printk(KERN_WARNING "ioapic: Unsupported size %d\n", len); arch/x86/kvm/mmu/mmu.c:1652: printk(KERN_ERR "%s: %p %llx\n", __func__, arch/x86/kvm/svm/svm.c:3450: printk(KERN_ERR "%s: unexpected exit_int_info 0x%x " arch/x86/kvm/vmx/posted_intr.c:322: printk( KERN_INFO arch/x86/kvm/vmx/posted_intr.c:343: printk(KERN_INF O "%s: failed to update PI IRTE\n", arch/x86/kvm/vmx/vmx.c:6507: printk(KERN_WARNING "%s: Breaking out of NMI-blocked " arch/x86/kvm/x86.c:13027: printk(KERN_INFO "irq bypass consumer (token %p) unregistration"