[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Fri, 9 Sep 2022 15:32:41 +0800
From: Chao Gao <chao.gao@...el.com>
To: <isaku.yamahata@...el.com>
CC: <linux-kernel@...r.kernel.org>, <kvm@...r.kernel.org>,
Paolo Bonzini <pbonzini@...hat.com>,
Sean Christopherson <seanjc@...gle.com>,
Marc Zyngier <maz@...nel.org>, Will Deacon <will@...nel.org>,
Yuan Yao <yuan.yao@...ux.intel.com>,
<isaku.yamahata@...il.com>, Kai Huang <kai.huang@...el.com>,
Atish Patra <atishp@...shpatra.org>,
Shaokun Zhang <zhangshaokun@...ilicon.com>,
Qi Liu <liuqi115@...wei.com>,
John Garry <john.garry@...wei.com>,
Daniel Lezcano <daniel.lezcano@...aro.org>,
"Huang Ying" <ying.huang@...el.com>,
Huacai Chen <chenhuacai@...nel.org>
Subject: Re: [PATCH v4 17/26] KVM: Introduce a arch wrapper to check all
processor compatibility
On Thu, Sep 08, 2022 at 04:25:33PM -0700, isaku.yamahata@...el.com wrote:
>From: Isaku Yamahata <isaku.yamahata@...el.com>
>
>Introduce a arch wrapper to check all processor compatibility and define
>default implementation as weak symbol to keep the current logic.
>
>The hardware feature compatibility check is arch dependent, only x86 KVM
>does cpu feature check on all processors. It doesn't make much sense to
>enforce the current implementation to invoke check function on each
>processors. Introduce a arch callback,
>kvm_arch_check_processor_compat_all(), so that arch code can override it.
>
>Eventually feature check should be pushed down into arch callback,
>(kvm_arch_hardware_setup(), kvm_arch_online_cpu(), and kvm_arch_resume()),
>the two compatibility check, kvm_arch_check_processor_compat{,_all}(), will
>be eliminated. This is a transitional step for it.
>
>Signed-off-by: Isaku Yamahata <isaku.yamahata@...el.com>
Reviewed-by: Chao Gao <chao.gao@...el.com>
>+__weak int kvm_arch_check_processor_compat_all(void)
nit: int __weak
Powered by blists - more mailing lists