Received: by 2002:ac0:e350:0:0:0:0:0 with SMTP id g16csp2045466imn; Mon, 1 Aug 2022 09:09:20 -0700 (PDT) X-Google-Smtp-Source: AGRyM1suzawhKHYrRDF1UKcyG9wlggEfYtK3e66u6myjdadBBbXJZrG0rpY5E+IXXvF8gUcXuB5p X-Received: by 2002:a17:906:a219:b0:6e4:86a3:44ea with SMTP id r25-20020a170906a21900b006e486a344eamr13475846ejy.385.1659370159758; Mon, 01 Aug 2022 09:09:19 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1659370159; cv=none; d=google.com; s=arc-20160816; b=KWyhNSer9LsGOlHhl7t2eDuaWw1plUz92plHi1YEEwp8GAut24AO+eyxDZSrzQ+bHd lyOFh+xPLD6Wsu7DYXzokhehy/GFl9SfcDaYOb/IBx3Awz+F2EEJ2airSLP6RH5sVIiR Swr2wVZSSRRLsPFed3EKXNilT6jkvL0xzKuIdBuRPILph7DLS7j8zaHhkhb2oxtXtwSp Q2N/pNvMnhw6bAM1iTHZCQ8HMd+++M1WUTNSWtg7u3YNbbbT7SdcvAQ/VgczXVxIgG6o eumrXbri2F8MSUwxN3pXCB9/hO8T1uFIOzDB+wA83DM7h+aF0p6rJCQBlXKAMhEKSsm3 LlwQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :user-agent:references:in-reply-to:date:cc:to:from:subject :message-id:dkim-signature; bh=YjwnPcemFdKzS6S36gsMhGgEGUlUL1WuNW85mhTQ5/s=; b=lgLHCzmqRyuZTkHYuvZlf+3dzqPZptfYqPcszg0quxp2b5idiM46xPpwcpnMrku3Wm CenkDKryoDsKgZjUMfS84BIdT1DeYhr/eshhR80bBOpsIdW9ZR6TlcFwMkeocS3G401W PELcZwdDkP8XJnW2YihWyIAN2bVZYIuSRUoXg85oyqTb9cCf3bZzXCbJx8PcllzBiGO1 swCcvC7IAw8r3Fd0H7gHK26d4WtOOceWXqIJGSrpD0VZdyplcJxxAiYouXP9asUOXoJK BBILf74h7U4iBIrgyNANJcHL/5WeHQrOYp1O7owlwrLf4xowb7qRg0Ty0Tl3InAhSamL AojA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=NYXKTHhZ; spf=pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-crypto-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id e12-20020a17090658cc00b007306a5f1616si4672906ejs.509.2022.08.01.09.08.33; Mon, 01 Aug 2022 09:09:19 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=NYXKTHhZ; spf=pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-crypto-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232095AbiHAQFp (ORCPT + 99 others); Mon, 1 Aug 2022 12:05:45 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:34418 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232361AbiHAQFn (ORCPT ); Mon, 1 Aug 2022 12:05:43 -0400 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id 269FCA454 for ; Mon, 1 Aug 2022 09:05:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1659369941; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=YjwnPcemFdKzS6S36gsMhGgEGUlUL1WuNW85mhTQ5/s=; b=NYXKTHhZI1rkJZDabEcxbL7llaCZq6vErcJbZM/7Iizn/1DcEGkR7StuD8n28qQDDVS4qw 1dXk3dN2QTloGVqXhptNwc7eJbwKCJ6BZO5UwoWa4VfR1w22CpDap72ZHAVZUeqBlpOMvo bQqyYsfV3V8UNGcm081heiBXONxskNA= Received: from mimecast-mx02.redhat.com (mimecast-mx02.redhat.com [66.187.233.88]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-573-XmrRqtr3MD6uq2OG3uJbAw-1; Mon, 01 Aug 2022 12:05:38 -0400 X-MC-Unique: XmrRqtr3MD6uq2OG3uJbAw-1 Received: from smtp.corp.redhat.com (int-mx06.intmail.prod.int.rdu2.redhat.com [10.11.54.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 63CCE101A58E; Mon, 1 Aug 2022 16:05:36 +0000 (UTC) Received: from starship (unknown [10.40.194.242]) by smtp.corp.redhat.com (Postfix) with ESMTP id 391A32166B26; Mon, 1 Aug 2022 16:05:30 +0000 (UTC) Message-ID: <4a327f06f6e5da6f3badb5ccf80d22a5c9e18b97.camel@redhat.com> Subject: Re: [PATCH v2 0/5] x86: cpuid: improve support for broken CPUID configurations From: Maxim Levitsky To: linux-kernel@vger.kernel.org, kvm@vger.kernel.org Cc: Pawan Gupta , Ingo Molnar , Josh Poimboeuf , Namhyung Kim , Tony Luck , Paolo Bonzini , "H. Peter Anvin" , Arnaldo Carvalho de Melo , Thomas Gleixner , Alexander Shishkin , Tim Chen , Borislav Petkov , "David S. Miller" , Dave Hansen , "Chang S. Bae" , Jane Malalane , Kees Cook , Kan Liang , Peter Zijlstra , "maintainer:X86 ARCHITECTURE (32-BIT AND 64-BIT)" , Herbert Xu , Jiri Olsa , Mark Rutland , linux-perf-users@vger.kernel.org, "open list:CRYPTO API" Date: Mon, 01 Aug 2022 19:05:29 +0300 In-Reply-To: References: <20220718141123.136106-1-mlevitsk@redhat.com> Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.36.5 (3.36.5-2.fc32) MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.78 on 10.11.54.6 X-Spam-Status: No, score=-3.4 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_LOW, SPF_HELO_NONE,SPF_NONE autolearn=unavailable autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-crypto@vger.kernel.org On Thu, 2022-07-28 at 10:30 +0300, Maxim Levitsky wrote: > On Mon, 2022-07-18 at 17:11 +0300, Maxim Levitsky wrote: > > This patch series aims to harden the cpuid code against the case when > > the hypervisor exposes a broken CPUID configuration to the guest, > > in the form of having a feature disabled but not features that depend on it. > > > > This is the more generic way to fix kernel panic in aes-ni kernel driver, > > which was triggered by CPUID configuration in which AVX is disabled but > > not AVX2. > > > > https://lore.kernel.org/all/20211103145231.GA4485@gondor.apana.org.au/T/ > > > > This was tested by booting a guest with AVX disabled and not AVX2, > > and observing that both a warning is now printed in dmesg, and > > that avx2 is gone from /proc/cpuinfo. > > > > V2: > > > > I hopefully addressed all the (very good) review feedback. > > > > Best regards, > > Maxim Levitsky > > > > Maxim Levitsky (5): > > perf/x86/intel/lbr: use setup_clear_cpu_cap instead of clear_cpu_cap > > x86/cpuid: refactor setup_clear_cpu_cap()/clear_cpu_cap() > > x86/cpuid: move filter_cpuid_features to cpuid-deps.c > > x86/cpuid: remove 'warn' parameter from filter_cpuid_features > > x86/cpuid: check for dependencies violations in CPUID and attempt to > > fix them > > > > arch/x86/events/intel/lbr.c | 2 +- > > arch/x86/include/asm/cpufeature.h | 1 + > > arch/x86/kernel/cpu/common.c | 51 +------------------- > > arch/x86/kernel/cpu/cpuid-deps.c | 80 +++++++++++++++++++++++++++---- > > 4 files changed, 74 insertions(+), 60 deletions(-) > > > > -- > > 2.34.3 > > > > > A very kind ping on these patches. Another kind ping on these patches. Best regards, Maxim Levitsky > > Best regards, > Maxim Levitsky