From: Peter Xu <peterx@redhat.com>
To: linux-kernel@vger.kernel.org, kvm@vger.kernel.org
Cc: Sean Christopherson <sean.j.christopherson@intel.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Wanpeng Li <kernellwp@gmail.com>,
Krish Sadhukhan <krish.sadhukhan@oracle.com>,
peterx@redhat.com
Subject: [PATCH v4 0/4] KVM: X86: Some tracepoint enhancements
Date: Fri, 6 Sep 2019 10:17:18 +0800 [thread overview]
Message-ID: <20190906021722.2095-1-peterx@redhat.com> (raw)
v4:
- pick r-b
- swap the last two patches [Sean]
v3:
- use unsigned int for vcpu id [Sean]
- a new patch to fix ple_window type [Sean]
v2:
- fix commit messages, change format of ple window tracepoint [Sean]
- rebase [Wanpeng]
Each small patch explains itself. I noticed them when I'm tracing
some IRQ paths and I found them helpful at least to me.
Please have a look. Thanks,
Peter Xu (4):
KVM: X86: Trace vcpu_id for vmexit
KVM: X86: Remove tailing newline for tracepoints
KVM: VMX: Change ple_window type to unsigned int
KVM: X86: Tune PLE Window tracepoint
arch/x86/kvm/svm.c | 16 ++++++++--------
arch/x86/kvm/trace.h | 34 ++++++++++++++--------------------
arch/x86/kvm/vmx/vmx.c | 18 ++++++++++--------
arch/x86/kvm/vmx/vmx.h | 2 +-
arch/x86/kvm/x86.c | 2 +-
5 files changed, 34 insertions(+), 38 deletions(-)
--
2.21.0
next reply other threads:[~2019-09-06 2:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-06 2:17 Peter Xu [this message]
2019-09-06 2:17 ` [PATCH v4 1/4] KVM: X86: Trace vcpu_id for vmexit Peter Xu
2019-09-06 2:17 ` [PATCH v4 2/4] KVM: X86: Remove tailing newline for tracepoints Peter Xu
2019-09-06 2:17 ` [PATCH v4 3/4] KVM: VMX: Change ple_window type to unsigned int Peter Xu
2019-09-06 14:22 ` Sean Christopherson
2019-09-06 2:17 ` [PATCH v4 4/4] KVM: X86: Tune PLE Window tracepoint Peter Xu
2019-09-06 14:23 ` Sean Christopherson
2019-09-10 17:05 ` [PATCH v4 0/4] KVM: X86: Some tracepoint enhancements Paolo Bonzini
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=20190906021722.2095-1-peterx@redhat.com \
--to=peterx@redhat.com \
--cc=kernellwp@gmail.com \
--cc=krish.sadhukhan@oracle.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=sean.j.christopherson@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.