Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
From:   Maxim Levitsky <mlevitsk@redhat.com>
To:     linux-kernel@vger.kernel.org, kvm@vger.kernel.org
Cc:     Pawan Gupta <pawan.kumar.gupta@linux.intel.com>,
        Ingo Molnar <mingo@redhat.com>,
        Josh Poimboeuf <jpoimboe@kernel.org>,
        Namhyung Kim <namhyung@kernel.org>,
        Tony Luck <tony.luck@intel.com>,
        Paolo Bonzini <pbonzini@redhat.com>,
        "H. Peter Anvin" <hpa@zytor.com>,
        Arnaldo Carvalho de Melo <acme@kernel.org>,
        Thomas Gleixner <tglx@linutronix.de>,
        Alexander Shishkin <alexander.shishkin@linux.intel.com>,
        Tim Chen <tim.c.chen@linux.intel.com>,
        Borislav Petkov <bp@alien8.de>,
        "David S. Miller" <davem@davemloft.net>,
        Dave Hansen <dave.hansen@linux.intel.com>,
        "Chang S. Bae" <chang.seok.bae@intel.com>,
        Jane Malalane <jane.malalane@citrix.com>,
        Kees Cook <keescook@chromium.org>,
        Kan Liang <kan.liang@linux.intel.com>,
        Peter Zijlstra <peterz@infradead.org>,
        Maxim Levitsky <mlevitsk@redhat.com>,
        x86@kernel.org (maintainer:X86 ARCHITECTURE (32-BIT AND 64-BIT)),
        Herbert Xu <herbert@gondor.apana.org.au>,
        Jiri Olsa <jolsa@kernel.org>,
        Mark Rutland <mark.rutland@arm.com>,
        linux-perf-users@vger.kernel.org,
        linux-crypto@vger.kernel.org (open list:CRYPTO API)
Subject: [PATCH v2 0/5] x86: cpuid: improve support for broken CPUID configurations
Date:   Mon, 18 Jul 2022 17:11:18 +0300
Message-Id: <20220718141123.136106-1-mlevitsk@redhat.com>
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Precedence: bulk

This patch series aims to harden the cpuid code against the case when=0D
the hypervisor exposes a broken CPUID configuration to the guest,=0D
in the form of having a feature disabled but not features that depend on it=
.=0D
=0D
This is the more generic way to fix kernel panic in aes-ni kernel driver,=0D
which was triggered by CPUID configuration in which AVX is disabled but=0D
not AVX2.=0D
=0D
https://lore.kernel.org/all/20211103145231.GA4485@gondor.apana.org.au/T/=0D
=0D
This was tested by booting a guest with AVX disabled and not AVX2,=0D
and observing that both a warning is now printed in dmesg, and=0D
that avx2 is gone from /proc/cpuinfo.=0D
=0D
V2:=0D
=0D
I hopefully addressed all the (very good) review feedback.=0D
=0D
Best regards,=0D
	Maxim Levitsky=0D
=0D
Maxim Levitsky (5):=0D
  perf/x86/intel/lbr: use setup_clear_cpu_cap instead of clear_cpu_cap=0D
  x86/cpuid: refactor setup_clear_cpu_cap()/clear_cpu_cap()=0D
  x86/cpuid: move filter_cpuid_features to cpuid-deps.c=0D
  x86/cpuid: remove 'warn' parameter from filter_cpuid_features=0D
  x86/cpuid: check for dependencies violations in CPUID and attempt to=0D
    fix them=0D
=0D
 arch/x86/events/intel/lbr.c       |  2 +-=0D
 arch/x86/include/asm/cpufeature.h |  1 +=0D
 arch/x86/kernel/cpu/common.c      | 51 +-------------------=0D
 arch/x86/kernel/cpu/cpuid-deps.c  | 80 +++++++++++++++++++++++++++----=0D
 4 files changed, 74 insertions(+), 60 deletions(-)=0D
=0D
-- =0D
2.34.3=0D
=0D