From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-13.3 required=3.0 tests=BAYES_00,DKIMWL_WL_MED, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,USER_IN_DEF_DKIM_WL autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 19D73C4707F for ; Tue, 25 May 2021 16:21:06 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id EDE72611C2 for ; Tue, 25 May 2021 16:21:05 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232696AbhEYQWe (ORCPT ); Tue, 25 May 2021 12:22:34 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:44622 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230511AbhEYQWb (ORCPT ); Tue, 25 May 2021 12:22:31 -0400 Received: from mail-pl1-x635.google.com (mail-pl1-x635.google.com [IPv6:2607:f8b0:4864:20::635]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 39449C061756 for ; Tue, 25 May 2021 09:21:01 -0700 (PDT) Received: by mail-pl1-x635.google.com with SMTP id v13so16596735ple.9 for ; Tue, 25 May 2021 09:21:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to; bh=XFC9iWJT/MQ8UEFztmuB49DTENqBYgd89Ij8J4hz14w=; b=bX5fLELA0/L/al7izHeFvwadEsP7L/qU8d3yun2fUzzW8+1Z7qpxKGvzfGm/2sky3H vwt/3hQ8/RBUy/fJFmqpnP+LYP2O5bOsA8RhtGjMp0TDQ+heuI8yfLb2j0+UaD8WIpq7 TbvPoMMJUMtFcF7cPS6n75TDrTsKov7dQQaHeY9V2SIYjiZIe7ZflWyx9DcKTfJLAvPp gJcVDpwYsIT4QQxfJe70EfCfMCMA/C6WX9hC+EA47WABARytB+0krmDQMh1Uq7DHNYVz 1GC1fC8cQfjPI2E1imroo2moXw8cM+2suiw6VQ09lkq7AStC+9qJjzBJEeMOf9FOX4IK r0Pg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=XFC9iWJT/MQ8UEFztmuB49DTENqBYgd89Ij8J4hz14w=; b=aXMUR9pBg/TIPgzIWpIBJ/Qtpjst5epZdYC4TC9IBp2YEzIpFiJjNknNVpFagKMTSd c6ty+yrUN11IhJOGCNqn3KWqk9frfF/x6KVRLCPUJv7PIQzj6AinKcI1EwPH4muMDDiJ iqkRLmnsRKI6C69+rfWUYp9o6OZczxJmwxNwtXFfaWbi3wuBs9nNX3AiDpCqEYQ6jGuU ZpWXdnTVgXcDBGhEgI18L1+0TAVpnl+2dOcGGxFrcpi5WzGGXM6Pi+Xzd+ISXsqDmB6d jjxg1j/nrTtEwDsVw4eorJFgcBP58+EOAqSiz0OkKb+YvvXp78w3l8bmSIgkwGShuDvb cF+Q== X-Gm-Message-State: AOAM532ilMlEppch/+D7UCrwLB+VyP9l2B0UDIV5mfgnb6pE8r8bnkE1 NpQtovGh10zHsVBvQRdS5QTZS+GTe16RTg== X-Google-Smtp-Source: ABdhPJz4EUTjaP4w7VQByc/KHY+qRzurLSemWKMMDKHGjZyqNhbJH+fDs0qdTtOturi+Xh3NixjSuA== X-Received: by 2002:a17:90a:ec05:: with SMTP id l5mr5677044pjy.141.1621959660505; Tue, 25 May 2021 09:21:00 -0700 (PDT) Received: from google.com (240.111.247.35.bc.googleusercontent.com. [35.247.111.240]) by smtp.gmail.com with ESMTPSA id r28sm14388368pgm.53.2021.05.25.09.20.59 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 25 May 2021 09:20:59 -0700 (PDT) Date: Tue, 25 May 2021 16:20:56 +0000 From: Sean Christopherson To: Dario Faggioli Cc: Stefano De Venuto , linux-kernel@vger.kernel.org, pbonzini@redhat.com, vkuznets@redhat.com, wanpengli@tencent.com, jmattson@google.com, x86@kernel.org, hpa@zytor.com, kvm@vger.kernel.org, rostedt@goodmis.org, y.karadz@gmail.com Subject: Re: [PATCH] Move VMEnter and VMExit tracepoints closer to the actual event Message-ID: References: <20210519182303.2790-1-stefano.devenuto99@gmail.com> <5e6ad92a72e139877fa0e7a1d77682a075060d16.camel@suse.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5e6ad92a72e139877fa0e7a1d77682a075060d16.camel@suse.com> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, May 21, 2021, Dario Faggioli wrote: > Hi Sean, > > On Thu, 2021-05-20 at 15:32 +0000, Sean Christopherson wrote: > > I 100% agree that the current behavior can be a bit confusing, but I wonder > > if we'd be better off "solving" that problem through documentation. > > > Indeed. So, do you happen to have in mind what could be the best place > and the best way for documenting this? I didn't have anything in mind, but my gut reaction is to add a new file dedicated to tracing/tracepoints in KVM, e.g. Documentation/virt/kvm/tracepoints.rst or Documentation/virt/kvm/tracing.rst I'm sure there are all sorts of tips and tricks people have for using KVM's tracepoints, it would be nice to provide a way to capture and disseminate them. My only hesitation is that Documentation/virt/kvm/ might be too formal for what would effectively be a wiki of sorts.