linux-kernel - Re: [PATCH] Move VMEnter and VMExit tracepoints closer to the actual event

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <YK0j6MrOCFeQSHCa@google.com>
Date:   Tue, 25 May 2021 16:20:56 +0000
From:   Sean Christopherson <seanjc@...gle.com>
To:     Dario Faggioli <dfaggioli@...e.com>
Cc:     Stefano De Venuto <stefano.devenuto99@...il.com>,
        linux-kernel@...r.kernel.org, pbonzini@...hat.com,
        vkuznets@...hat.com, wanpengli@...cent.com, jmattson@...gle.com,
        x86@...nel.org, hpa@...or.com, kvm@...r.kernel.org,
        rostedt@...dmis.org, y.karadz@...il.com
Subject: Re: [PATCH] Move VMEnter and VMExit tracepoints closer to the actual
 event

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.