From: Sean Christopherson <seanjc@google.com>
To: zhanghao <76824143@qq.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] KVM: x86: enrich kvm_fast_mmio trace event fields
Date: Mon, 27 Apr 2026 11:37:35 -0700 [thread overview]
Message-ID: <ae-s7x-46gnuc07M@google.com> (raw)
In-Reply-To: <tencent_DB120129B359660BBBD7CCC9681F507C0105@qq.com>
On Fri, Apr 24, 2026, zhanghao wrote:
> kvm_fast_mmio currently logs only the GPA, which makes fast-MMIO traces
> less useful when diagnosing access patterns.
What's the overall use case / motivation? Fast MMIO doesn't consume the value,
length, or type. Why trace something that KVM ignores by design?
prev parent reply other threads:[~2026-04-27 18:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-24 6:05 [PATCH] KVM: x86: enrich kvm_fast_mmio trace event fields zhanghao
2026-04-27 18:37 ` Sean Christopherson [this message]
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=ae-s7x-46gnuc07M@google.com \
--to=seanjc@google.com \
--cc=76824143@qq.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.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.