Received: by 2002:a05:6a10:206:0:0:0:0 with SMTP id 6csp5187430pxj; Wed, 9 Jun 2021 11:10:17 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxpyXFDUqVD4i7nP8SnHvYs8eonwVYEMhPDC879pUMMvvozGRMjTv93zxrMAW1y9se1Q45+ X-Received: by 2002:a50:ee8b:: with SMTP id f11mr647739edr.329.1623262217053; Wed, 09 Jun 2021 11:10:17 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1623262217; cv=none; d=google.com; s=arc-20160816; b=CW8+P83RiP5iVXUtsSfVsHAlUBqznQTvvTArOeYvfB1X1rpUL4ZLtuBGU7b28X/r3x C19vT2Blzwv5B8gyuAmRppuFsYL6OyQQdz3TWYi/Otx3X3fmIfb0JZOFwZatAgIIt4S6 9wLgUzA3rmoy+9qSUnGihXnw7DCK/CDlrJ6HjRqqQlfKXhRok16VM51QCCMrLQPiqNiT roLitInEBhJXtBinDtq4fZV8UnXsZOlEctxtDz8lN3xevOmcZOXstuUpGi8f2C0a+mLr vkepBLeTTNnBX9RYntW0S1POJWNxbHGtblqzYX/q1oQJsicFzz5vIACM/yr2ZZPxoZwr UFig== 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:message-id:subject:cc:to:from:date; bh=q1gNISDJUYUNsLBLdhuIVJ+FSCACepzF6DTeYfATHCY=; b=vk39Tf17M1yZjkLYLVPPw3++cJLwE8sSGWPnzN/BQ3P8hMtPGIPrIW3j2lMUpcEb/G IfgPqbJUpIFixSjkE+xw+mEY8VL66k3VdslDqeNLuGX0nbpG/slFXWk5m0eMqziymVPT lMNc7N/Z0oy052RU4gNFOJHcC7jBJG8ryZPr7rlXuw0aAdAv8SUPghmLcrBmmTf4LFgx zXyuR5AQSpSxSB3sx4mRlilXKq8i9r9tsWqcl63GsRwXmUuitgRr3ep6jMlGS4LTzHEi jyRymeqzb7C5Y9GMCoVdlLTXXZPsZXV77fH1J1iGgAZwwP7rhyKdZAARfx3GwbFeOFae cTfw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id y22si287801edv.206.2021.06.09.11.09.52; Wed, 09 Jun 2021 11:10:17 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230454AbhFIRDw (ORCPT + 99 others); Wed, 9 Jun 2021 13:03:52 -0400 Received: from mail.kernel.org ([198.145.29.99]:48750 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230205AbhFIRDu (ORCPT ); Wed, 9 Jun 2021 13:03:50 -0400 Received: from oasis.local.home (cpe-66-24-58-225.stny.res.rr.com [66.24.58.225]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 538C660C40; Wed, 9 Jun 2021 17:01:55 +0000 (UTC) Date: Wed, 9 Jun 2021 13:01:53 -0400 From: Steven Rostedt To: Sean Christopherson Cc: Wanpeng Li , Paolo Bonzini , Vitaly Kuznetsov , Wanpeng Li , Jim Mattson , Joerg Roedel , kvm , LKML Subject: Re: [PATCH] KVM: x86: Ensure liveliness of nested VM-Enter fail tracepoint message Message-ID: <20210609130153.42b3ca81@oasis.local.home> In-Reply-To: References: <20210607175748.674002-1-seanjc@google.com> X-Mailer: Claws Mail 3.17.3 (GTK+ 2.24.33; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 9 Jun 2021 09:12:40 -0700 Sean Christopherson wrote: > > I can observe tons of other kvm tracepoints warning like this after > > commit 9a6944fee68e25 (tracing: Add a verifier to check string > > pointers for trace events), just echo 1 > > > /sys/kernel/tracing/events/kvm/enable and boot a linux guest. > > Can you provide your .config? With all of events/kvm and events/kvmmmu enabled > I don't get any warnings running a Linux guest, a nested Linux guest, and > kvm-unit-tests. > > Do you see the behavior with other tracepoints? E.g. enabling all events on my > systems yields warnings for a USB module, but everything else is clean. Right, I tested this with running KVM guests when it was added. I was actually surprised with Sean's report saying it was a kvm trace event, until I noticed that the problem event is only triggered on error paths. -- Steve