From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id BFE96C433EF for ; Wed, 8 Jun 2022 14:00:41 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S240533AbiFHOAk (ORCPT ); Wed, 8 Jun 2022 10:00:40 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:50280 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S240530AbiFHOAj (ORCPT ); Wed, 8 Jun 2022 10:00:39 -0400 Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 775F231D9D0; Wed, 8 Jun 2022 07:00:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1654696838; x=1686232838; h=message-id:date:mime-version:subject:to:cc:references: from:in-reply-to:content-transfer-encoding; bh=hMOWQic/jVTuD2Wq8YgUFKqJpBQ/U8MDI3wleWZjJec=; b=AoRqAi3VteIn9LWS4COLyc1cfxGuLdycZDMksI5fCSolcwu9mIKSprWp EFeSRHquuzq06ybVLgfK+nuDKZtApWwEm5bjpZEEuLG1wgfaGt/4TonKK QaHLH0a+SS8lCr/jHc4gV0Ak2/Nrc3od3e/Cn8D4aXZzyy7V2OjnZz42J iIi5eOe/KQmHYGmU8Wlt2BCLE4kb57m+wsr7DrMfXWJA1osDXZZ4OBMms zeUsuiLgJ5b0nDPub2xMhaeXJBfeOpBLMnY4z/Xo0viiG+RZWOU+5XptF 5qcQxxZmZHBuOnVlzhyCi7CF8aIl1zb1L9auoUFaw0DSfXWT2HQpzVrzb w==; X-IronPort-AV: E=McAfee;i="6400,9594,10371"; a="277739839" X-IronPort-AV: E=Sophos;i="5.91,286,1647327600"; d="scan'208";a="277739839" Received: from fmsmga002.fm.intel.com ([10.253.24.26]) by orsmga102.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 08 Jun 2022 07:00:37 -0700 X-IronPort-AV: E=Sophos;i="5.91,286,1647327600"; d="scan'208";a="683344035" Received: from kbrownfi-mobl2.amr.corp.intel.com (HELO [10.212.170.198]) ([10.212.170.198]) by fmsmga002-auth.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 08 Jun 2022 07:00:36 -0700 Message-ID: <2e3286b4-a13b-1be0-2b6a-902eec54e960@intel.com> Date: Wed, 8 Jun 2022 07:00:35 -0700 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.9.1 Subject: Re: [PATCH] crypto: x86/aes-ni: fix AVX detection Content-Language: en-US To: Maxim Levitsky , linux-kernel@vger.kernel.org Cc: "maintainer:X86 ARCHITECTURE (32-BIT AND 64-BIT)" , "open list:CRYPTO API" , Dave Hansen , Thomas Gleixner , Herbert Xu , Borislav Petkov , Paolo Bonzini , Ingo Molnar , "David S. Miller" , "H. Peter Anvin" , Tim Chen References: <20211103124614.499580-1-mlevitsk@redhat.com> <622444d6-f98b-dae4-381e-192e5cb02621@intel.com> <3943020ac3540af8055c487e4810c63a422d65e7.camel@redhat.com> From: Dave Hansen In-Reply-To: <3943020ac3540af8055c487e4810c63a422d65e7.camel@redhat.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-crypto@vger.kernel.org On 6/8/22 04:29, Maxim Levitsky wrote: > filter_cpuid_features can be extended to filter known bogus CPUID depedencies, > like case when AVX2 supported and AVX not supported in CPUID. > If you agree, then it seems the best case to deal with this issue. Yes, it should have been doing this all along. Patches to fix that would be very welcome.