Received: by 2002:a25:8b91:0:0:0:0:0 with SMTP id j17csp5043698ybl; Tue, 4 Feb 2020 06:43:18 -0800 (PST) X-Google-Smtp-Source: APXvYqzi5MOSgATSjjmyCBNdddyhspG9QtfVwChid6JF9tT8KUJfqOt/4NFVKUazRJTeIsjxomOD X-Received: by 2002:aca:be09:: with SMTP id o9mr3743467oif.177.1580827398560; Tue, 04 Feb 2020 06:43:18 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1580827398; cv=none; d=google.com; s=arc-20160816; b=Ju9baBDzYnwO8doUM+N8Hf37z6X6ttWalaUS4R3VsZfuLL2+sg0Edu8jjx/L1Wamtm 63k0ZmjtgPDLF3t/49dOTs+j5u7ueGZ9Us3hq6VcjEXN+HVf0sXAwQ4m/cda7Je3CQiq GfrI7ile848TRf5r1d8vglkAOgdGIhHyYD+AZ7nMJbJ/mCWAVVLc10eKNTXz7sljIhck fvxIw9QWYcZsttArbBIBr0wXN8jiEjTimIgQkBikQNU3lw+oHPnHxdSWA3D6xKggInQK Fc9jdthg8PPlZ81q2zoGnlEKHB2yNGmm/irdvJ2fJMjqTyjQQyHOpu64rYwmRrJ4wfuh 20nQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:message-id:date:references :in-reply-to:subject:cc:to:from:dkim-signature; bh=CtNuq+c53520XJbZSzjdH2GmUQ771nRPcTR/Jk2Pais=; b=YxuXA82MG8tBChuCVQg4ETUpOy+RV3+1Qs1KJv7vc4CEjJgilum1LBBZDaoEyamXPE YTXFH1AoHguNvT4ivQ1CD5NkvyqL9eU1gChHVrzPEhWTQ4YO2HjpeE9I0oztG82NTQOE QIq7R+SOF32yskpZO2yuFlvr0jgTLLFPwbWqJj4G8WVxdsW2YVqVp8quLiUJlz4Wb7/s vQkIijsE9FJhGvFnq+0I4Rn525uB8McfF4JQQCKRm0h+ewS+pDm6WcgnVQMtMdPN8F+N PgGNv/sxBGjXYRJbSJX71Brfx94wWW0L+ihKhsXSwE4h/gmSweFRca5U1y+xFVFhHHzs camg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=GhK5f+pM; 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=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id s188si9353836oia.277.2020.02.04.06.43.06; Tue, 04 Feb 2020 06:43:18 -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=@redhat.com header.s=mimecast20190719 header.b=GhK5f+pM; 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=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727278AbgBDOmL (ORCPT + 99 others); Tue, 4 Feb 2020 09:42:11 -0500 Received: from us-smtp-delivery-1.mimecast.com ([207.211.31.120]:30263 "EHLO us-smtp-1.mimecast.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1727240AbgBDOmK (ORCPT ); Tue, 4 Feb 2020 09:42:10 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1580827329; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=CtNuq+c53520XJbZSzjdH2GmUQ771nRPcTR/Jk2Pais=; b=GhK5f+pMeZWRQvW/yUXgbHCznJNiTlkNVWIZ0RCgpN04KOcdkkS6G1Ts5848aUysfgdeqf Txh1gXLZCCkbVAqv1pab7vDs/cpZOlbfrkPVnK2F3Enm4vtDul7TyvEoUEtrMmt7kLLqY+ 8f2iHCVb1SQ1jNiAZDFK/5vHoKJ5VMU= Received: from mail-wm1-f69.google.com (mail-wm1-f69.google.com [209.85.128.69]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-207-dlOoZ5gaPneKlSZF2oAnFQ-1; Tue, 04 Feb 2020 09:42:07 -0500 X-MC-Unique: dlOoZ5gaPneKlSZF2oAnFQ-1 Received: by mail-wm1-f69.google.com with SMTP id n17so1468976wmk.1 for ; Tue, 04 Feb 2020 06:42:07 -0800 (PST) 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:in-reply-to:references:date :message-id:mime-version; bh=CtNuq+c53520XJbZSzjdH2GmUQ771nRPcTR/Jk2Pais=; b=KBqJPi4qX6FZ7b5wf9EP8IpoU1+i89MDutKyzKpN4c+RoBZdIyvfMCCHrUj+i2F5jC IU33772UdL+hnEwsYtJdDrfbuVG6CIgCpEwhHqtGZqdgeaZSZb3maSkoWEF8GcDm0Sea nv0XsxU6gLEN9LoRY30IFvBNtrKkYZPpNQSAzcNUj16QUVfcDIiqfD3E1PWv3G41FxB1 CFKVWpjm/ADFTdR0hQis8JDLwYHpjEUWGIwupVTvSL68Diwdw1q3/vrPa9d5FMrZp1CW edjBvgA/7FghniBwO8myT0BX48cEN8Wm+WxQLLXXT4jvGw3MAmZ1fYptgquTYKnGKY20 lFXA== X-Gm-Message-State: APjAAAVBoG1AMBvayX7V20yp1VhhrPNaa7l6kDqn69Gy0H8uXuZWMt2F 6OQRbkDgaHNxkNZbV1mvSrPZczIUaCmPr7ucqh/+isvON1PAFzY8IjQZxHWllZfyhPGyzJxyNVL lvwHt/pXDDcged5qxD3mJgz3p X-Received: by 2002:a1c:9a84:: with SMTP id c126mr6355194wme.111.1580827326388; Tue, 04 Feb 2020 06:42:06 -0800 (PST) X-Received: by 2002:a1c:9a84:: with SMTP id c126mr6355174wme.111.1580827326200; Tue, 04 Feb 2020 06:42:06 -0800 (PST) Received: from vitty.brq.redhat.com (nat-pool-brq-t.redhat.com. [213.175.37.10]) by smtp.gmail.com with ESMTPSA id t5sm29943498wrr.35.2020.02.04.06.42.05 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 04 Feb 2020 06:42:05 -0800 (PST) From: Vitaly Kuznetsov To: Thadeu Lima de Souza Cascardo , Wanpeng Li Cc: LKML , kvm , Paolo Bonzini , Sean Christopherson , Wanpeng Li , Jim Mattson , Joerg Roedel Subject: Re: [PATCH] KVM: Pre-allocate 1 cpumask variable per cpu for both pv tlb and pv ipis In-Reply-To: <20200204142733.GI40679@calabresa> References: <878slio6hp.fsf@vitty.brq.redhat.com> <20200204142733.GI40679@calabresa> Date: Tue, 04 Feb 2020 15:42:04 +0100 Message-ID: <871rrao1mr.fsf@vitty.brq.redhat.com> MIME-Version: 1.0 Content-Type: text/plain Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Thadeu Lima de Souza Cascardo writes: >> > > /* >> > > @@ -624,6 +625,7 @@ static void __init kvm_guest_init(void) >> > > kvm_para_has_feature(KVM_FEATURE_STEAL_TIME)) { >> > > pv_ops.mmu.flush_tlb_others = kvm_flush_tlb_others; >> > > pv_ops.mmu.tlb_remove_table = tlb_remove_table; >> > > + pr_info("KVM setup pv remote TLB flush\n"); >> > > } >> > > > > I am more concerned about printing the "KVM setup pv remote TLB flush" message, > not only when KVM pv is used, but pv TLB flush is not going to be used, but > also when the system is not even paravirtualized. Huh? In Wanpeng's patch this print is under if (kvm_para_has_feature(KVM_FEATURE_PV_TLB_FLUSH) && !kvm_para_has_hint(KVM_HINTS_REALTIME) && kvm_para_has_feature(KVM_FEATURE_STEAL_TIME)) and if you mean another patch we descussed before which was adding (!kvm_para_available() || nopv) check than it's still needed. Or, alternatively, we can make kvm_para_has_feature() check for that. -- Vitaly