From: Sean Christopherson <seanjc@google.com>
To: Dario Faggioli <dfaggioli@suse.com>
Cc: Stefano De Venuto <stefano.devenuto99@gmail.com>,
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
Date: Tue, 25 May 2021 16:20:56 +0000 [thread overview]
Message-ID: <YK0j6MrOCFeQSHCa@google.com> (raw)
In-Reply-To: <5e6ad92a72e139877fa0e7a1d77682a075060d16.camel@suse.com>
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.
next prev parent reply other threads:[~2021-05-25 16:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-19 18:23 [PATCH] Move VMEnter and VMExit tracepoints closer to the actual event Stefano De Venuto
2021-05-20 6:05 ` Dario Faggioli
2021-05-20 7:21 ` Thomas Gleixner
2021-05-21 7:13 ` Dario Faggioli
2021-05-20 15:32 ` Sean Christopherson
2021-05-20 16:18 ` Paolo Bonzini
2021-05-21 7:58 ` Dario Faggioli
2021-05-28 16:55 ` Dario Faggioli
2021-05-28 16:57 ` Paolo Bonzini
2021-05-21 7:51 ` Dario Faggioli
2021-05-25 16:20 ` Sean Christopherson [this message]
2021-05-28 17:03 ` Dario Faggioli
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YK0j6MrOCFeQSHCa@google.com \
--to=seanjc@google.com \
--cc=dfaggioli@suse.com \
--cc=hpa@zytor.com \
--cc=jmattson@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=rostedt@goodmis.org \
--cc=stefano.devenuto99@gmail.com \
--cc=vkuznets@redhat.com \
--cc=wanpengli@tencent.com \
--cc=x86@kernel.org \
--cc=y.karadz@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox