lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <yywvcb5eujvkqwnip46x7c53bkqe6b6rqg3u4etzkjmgcqfpgk@ajulxuswpvcp>
Date: Sat, 1 Nov 2025 09:49:34 +0800
From: Yao Yuan <yaoyuan@...ux.alibaba.com>
To: Sean Christopherson <seanjc@...gle.com>
Cc: Paolo Bonzini <pbonzini@...hat.com>, kvm@...r.kernel.org, 
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] KVM: x86: Add a helper to dedup reporting of unhandled
 VM-Exits

On Fri, Oct 31, 2025 at 10:01:38AM +0800, Sean Christopherson wrote:
> 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.

thanks for your reply, Good point on printks are ratelimited!

Reviewed-by: yaoyuan@...ux.alibaba.com

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ