[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20251022013657.n2he5yabfgunm5vb@desk>
Date: Tue, 21 Oct 2025 18:36:57 -0700
From: Pawan Gupta <pawan.kumar.gupta@...ux.intel.com>
To: Sean Christopherson <seanjc@...gle.com>
Cc: Paolo Bonzini <pbonzini@...hat.com>, kvm@...r.kernel.org,
linux-kernel@...r.kernel.org, Brendan Jackman <jackmanb@...gle.com>
Subject: Re: [PATCH v3 3/4] KVM: VMX: Disable L1TF L1 data cache flush if
CONFIG_CPU_MITIGATIONS=n
On Thu, Oct 16, 2025 at 01:04:16PM -0700, Sean Christopherson wrote:
> @@ -302,6 +303,16 @@ static int vmx_setup_l1d_flush(enum vmx_l1d_flush_state l1tf)
> return 0;
> }
>
> +static int vmx_setup_l1d_flush(void)
> +{
> + /*
> + * Hand the parameter mitigation value in which was stored in the pre
> + * module init parser. If no parameter was given, it will contain
> + * 'auto' which will be turned into the default 'cond' mitigation mode.
> + */
> + return vmx_setup_l1d_flush(vmentry_l1d_flush_param);
A likely typo here, it should be:
return __vmx_setup_l1d_flush(vmentry_l1d_flush_param);
Powered by blists - more mailing lists