From: Dario Faggioli <dfaggioli@suse.com>
To: linux-kernel@vger.kernel.org
Cc: Lorenzo Brescia <lorenzo.brescia@edu.unito.it>,
Paolo Bonzini <pbonzini@redhat.com>,
Sean Christopherson <seanjc@google.com>,
Vitaly Kuznetsov <vkuznets@redhat.com>,
Wanpeng Li <wanpengli@tencent.com>,
Jim Mattson <jmattson@google.com>, Joerg Roedel <joro@8bytes.org>,
kvm@vger.kernel.org
Subject: Re: [PATCH] kvm: tracing: Fix unmatched kvm_entry and kvm_exit events
Date: Sat, 16 Jan 2021 02:25:57 +0100 [thread overview]
Message-ID: <0a32e141d8929f75025a0d9544a4552f2a916c5d.camel@suse.com> (raw)
In-Reply-To: <160873470698.11652.13483635328769030605.stgit@Wayrath>
[-- Attachment #1: Type: text/plain, Size: 1082 bytes --]
On Wed, 2020-12-23 at 14:45 +0000, Dario Faggioli wrote:
> From: Lorenzo Brescia <lorenzo.brescia@edu.unito.it>
>
> On VMX, if we exit and then re-enter immediately without leaving
> the vmx_vcpu_run() function, the kvm_entry event is not logged.
> That means we will see one (or more) kvm_exit, without its (their)
> corresponding kvm_entry, as shown here:
>
> CPU-1979 [002] 89.871187: kvm_entry: vcpu 1
> CPU-1979 [002] 89.871218: kvm_exit: reason MSR_WRITE
> CPU-1979 [002] 89.871259: kvm_exit: reason MSR_WRITE
>
> It also seems possible for a kvm_entry event to be logged, but then
> we leave vmx_vcpu_run() right away (if vmx->emulation_required is
> true). In this case, we will have a spurious kvm_entry event in the
> trace.
>
Gentle ping... :-)
Thanks and Regards
--
Dario Faggioli, Ph.D
http://about.me/dario.faggioli
Virtualization Software Engineer
SUSE Labs, SUSE https://www.suse.com/
-------------------------------------------------------------------
<<This happens because _I_ choose it to happen!>> (Raistlin Majere)
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2021-01-16 1:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-23 14:45 [PATCH] kvm: tracing: Fix unmatched kvm_entry and kvm_exit events Dario Faggioli
2021-01-16 1:25 ` Dario Faggioli [this message]
2021-01-18 18:20 ` Paolo Bonzini
2021-01-21 14:55 ` 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=0a32e141d8929f75025a0d9544a4552f2a916c5d.camel@suse.com \
--to=dfaggioli@suse.com \
--cc=jmattson@google.com \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lorenzo.brescia@edu.unito.it \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.com \
--cc=vkuznets@redhat.com \
--cc=wanpengli@tencent.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;
as well as URLs for NNTP newsgroup(s).