kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Krish Sadhukhan <krish.sadhukhan@oracle.com>
To: kvm <kvm@vger.kernel.org>
Subject: Guest identity in VMCS/VMCB
Date: Thu, 30 Jul 2020 14:10:42 -0700	[thread overview]
Message-ID: <8f77270a-b47e-8e69-2e36-f28de927cd7a@oracle.com> (raw)

When I am debugging and looking at the trace-point output for a guest, there is no way for me to determine whether a given trace-point, say, {vmx|svm}_handle_exit() or {vmx|svm}_vcpu_run(), was executed as part of which L1/L2 guest. As VMs do such operations so many times in a short period of time, trace-point output looks overwhelming and is of no use when  analyzed from this angle.

Does it makes sense to embed some sort of guest identification within the VMCS/VMCB, say, loaded_vmcs or vmcb, so that trace-points can spit out which guest/nested-guest executed the operation ?


-Krish


                 reply	other threads:[~2020-07-30 21:10 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=8f77270a-b47e-8e69-2e36-f28de927cd7a@oracle.com \
    --to=krish.sadhukhan@oracle.com \
    --cc=kvm@vger.kernel.org \
    /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).