[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Fri, 9 Sep 2022 10:15:16 +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 09/26] KVM: Do processor compatibility check on resume
On Thu, Sep 08, 2022 at 04:25:25PM -0700, isaku.yamahata@...el.com wrote:
>From: Isaku Yamahata <isaku.yamahata@...el.com>
>
>So far the processor compatibility check is not done on resume. It should
>be done. The resume is called for resuming from S3/S4. CPUs can be
>replaced or the kernel can resume from S4 on a different machine. So
Are they valid cases handled by other kernel components? Trying to
handle them in KVM only doesn't help as kernel is likely to fail
somewhere else.
Powered by blists - more mailing lists