[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Z6vwZtnxIX292KLH@google.com>
Date: Tue, 11 Feb 2025 16:50:46 -0800
From: Sean Christopherson <seanjc@...gle.com>
To: Binbin Wu <binbin.wu@...ux.intel.com>
Cc: pbonzini@...hat.com, kvm@...r.kernel.org, rick.p.edgecombe@...el.com,
kai.huang@...el.com, adrian.hunter@...el.com, reinette.chatre@...el.com,
xiaoyao.li@...el.com, tony.lindgren@...el.com, isaku.yamahata@...el.com,
yan.y.zhao@...el.com, chao.gao@...el.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 16/17] KVM: TDX: Handle EXCEPTION_NMI and EXTERNAL_INTERRUPT
On Tue, Feb 11, 2025, Binbin Wu wrote:
> + kvm_pr_unimpl("unexpected exception 0x%x(exit_reason 0x%x qual 0x%lx)\n",
> + intr_info, vmx_get_exit_reason(vcpu).full, vmx_get_exit_qual(vcpu));
This should be vcpu_unimpl(). But I vote to omit it entirely. Ratelimited
printks are notoriously unhelpful, and KVM is already providing a useful exit
to userspace.
Powered by blists - more mailing lists