KVM Archive on lore.kernel.org
 help / color / Atom feed
* Guest identity in VMCS/VMCB
@ 2020-07-30 21:10 Krish Sadhukhan
  0 siblings, 0 replies; only message in thread
From: Krish Sadhukhan @ 2020-07-30 21:10 UTC (permalink / raw)
  To: kvm

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 ?


^ permalink raw reply	[flat|nested] only message in thread

only message in thread, back to index

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-07-30 21:10 Guest identity in VMCS/VMCB Krish Sadhukhan

KVM Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/kvm/0 kvm/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 kvm kvm/ https://lore.kernel.org/kvm \
	public-inbox-index kvm

Example config snippet for mirrors

Newsgroup available over NNTP:

AGPL code for this site: git clone https://public-inbox.org/public-inbox.git