Re: [PATCH 03/19] Revert "KVM: SVM: Introduce hybrid-AVIC mode"

From: Jim Mattson
Date: Thu Sep 01 2022 - 07:48:16 EST

Next message: kernel test robot: "[ammarfaizi2-block:wireless/wireless-next/mld-wip 15/20] net/mac80211/link.c:398:9: error: use of undeclared identifier 'BSS_CHANGED_EHT_PUNCTURING'"
Previous message: David Howells: "Re: [PATCH v4] vfs, security: Fix automount superblock LSM init problem, preventing NFS sb sharing"
In reply to: Maxim Levitsky: "Re: [PATCH 03/19] Revert "KVM: SVM: Introduce hybrid-AVIC mode""
Next in thread: Sean Christopherson: "Re: [PATCH 03/19] Revert "KVM: SVM: Introduce hybrid-AVIC mode""
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

On Thu, Sep 1, 2022 at 3:26 AM Maxim Levitsky <mlevitsk@xxxxxxxxxx> wrote:

> I just know that nothing is absolute, in some rare cases (like different APIC base per cpu),
> it is just not feasable to support the spec.

Why isn't this feasible? We supported it when I was at VMware.

Next message: kernel test robot: "[ammarfaizi2-block:wireless/wireless-next/mld-wip 15/20] net/mac80211/link.c:398:9: error: use of undeclared identifier 'BSS_CHANGED_EHT_PUNCTURING'"
Previous message: David Howells: "Re: [PATCH v4] vfs, security: Fix automount superblock LSM init problem, preventing NFS sb sharing"
In reply to: Maxim Levitsky: "Re: [PATCH 03/19] Revert "KVM: SVM: Introduce hybrid-AVIC mode""
Next in thread: Sean Christopherson: "Re: [PATCH 03/19] Revert "KVM: SVM: Introduce hybrid-AVIC mode""
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]