From: Sean Christopherson <seanjc@google.com>
To: Yao Yuan <yaoyuan@linux.alibaba.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] KVM: x86: Add a helper to dedup reporting of unhandled VM-Exits
Date: Fri, 31 Oct 2025 10:01:38 -0700 [thread overview]
Message-ID: <aQTrcgT9MMY_69wh@google.com> (raw)
In-Reply-To: <bophxumzbp2yuovzhvt62jeb5e6vwc2mirvcl6uyztse5mqvjt@xmbhgmqnpn5d>
On Fri, Oct 31, 2025, Yao Yuan wrote:
> On Thu, Oct 30, 2025 at 11:50:03AM +0800, Sean Christopherson wrote:
> I like the dedup, and this brings above for tdx which not
> before. Just one small thing: Will it be better if keep the
> "vmx"/"svm" hint as before and plus the "tdx" hint yet ?
It'd be nice to have, but I honestly don't think it's worth going out of our
way to capture that information. If someone can't disambiguate "kvm" to mean
"vmx/tdx" vs. "svm" based on the host, they've got bigger problems.
And as for "vmx" vs. "tdx", I really hope that's not meaningful information for
users, e.g. the printks are ratelimited, and users should really be gleaning
information from the VMM instance, not from dmesg.
next prev parent reply other threads:[~2025-10-31 17:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-30 18:50 [PATCH] KVM: x86: Add a helper to dedup reporting of unhandled VM-Exits Sean Christopherson
2025-10-31 5:44 ` Yao Yuan
2025-10-31 17:01 ` Sean Christopherson [this message]
2025-11-01 1:49 ` Yao Yuan
2025-10-31 10:10 ` Huang, Kai
2025-10-31 11:18 ` Gupta, Pankaj
2025-11-03 17:37 ` Yosry Ahmed
2025-11-04 17:16 ` Sean Christopherson
2025-11-04 2:00 ` Xiaoyao Li
2025-11-04 3:03 ` Binbin Wu
2025-11-04 17:45 ` Sean Christopherson
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=aQTrcgT9MMY_69wh@google.com \
--to=seanjc@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=yaoyuan@linux.alibaba.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