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 BEAAFC433FE for ; Fri, 4 Nov 2022 10:50:58 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231420AbiKDKu5 (ORCPT ); Fri, 4 Nov 2022 06:50:57 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:60976 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231319AbiKDKu4 (ORCPT ); Fri, 4 Nov 2022 06:50:56 -0400 Received: from mail.skyhub.de (mail.skyhub.de [5.9.137.197]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 03A692B272; Fri, 4 Nov 2022 03:50:53 -0700 (PDT) Received: from zn.tnic (p200300ea9733e72b329c23fffea6a903.dip0.t-ipconnect.de [IPv6:2003:ea:9733:e72b:329c:23ff:fea6:a903]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.skyhub.de (SuperMail on ZX Spectrum 128k) with ESMTPSA id 7F8A81EC02DD; Fri, 4 Nov 2022 11:50:52 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=alien8.de; s=dkim; t=1667559052; 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=M8WImQ7ZL8KrObKcbD6n0+VmHllyJCHfdjTe3x0R7HQ=; b=dN/GvTKKqzlUUDakXZilCZ4uSdGe5CAJbJl40VQolvuHhJtQW1xcdTi0YDrLS0QZB0jMhb eQaBUuNsI7Q4vIQY40V9Yc40Te46X3x4T3b1lTvnHpVMUlN4ouXzHpCyZ5uFQO1dFeSUuO ij0Xzs8AtZKYfBUg49QCf7gN02IzTqM= Date: Fri, 4 Nov 2022 11:50:47 +0100 From: Borislav Petkov To: "Joseph, Jithu" Cc: hdegoede@redhat.com, markgross@kernel.org, tglx@linutronix.de, mingo@redhat.com, dave.hansen@linux.intel.com, x86@kernel.org, hpa@zytor.com, gregkh@linuxfoundation.org, ashok.raj@intel.com, tony.luck@intel.com, linux-kernel@vger.kernel.org, platform-driver-x86@vger.kernel.org, patches@lists.linux.dev, ravi.v.shankar@intel.com, thiago.macieira@intel.com, athenas.jimenez.gonzalez@intel.com Subject: Re: [PATCH 07/14] x86/microcode/intel: Expose microcode_sanity_check() Message-ID: References: <20221021203413.1220137-1-jithu.joseph@intel.com> <20221021203413.1220137-8-jithu.joseph@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: platform-driver-x86@vger.kernel.org On Thu, Nov 03, 2022 at 11:15:12PM -0700, Joseph, Jithu wrote: > If these doesn’t alleviate your concern, I will post v2 without > exporting the aforementioned functions and implementing them > separately in IFS driver as you suggested. So tglx persuaded me yesterday that we should do code sharing after all, so that all blob loading remains consistent. So let's try the cpu/intel.c thing and see what breaks, how and when. As to patch 8, that metadata checking should not be part of microcode_intel_sanity_check() but a separate function. Along with microcode_intel_find_meta_data() - all those should go into the IFS thing. When microcode loading ends up really needing metadata, *then* that functionality should be lifted into a more fitting place like cpu/intel.c Thx. -- Regards/Gruss, Boris. https://people.kernel.org/tglx/notes-about-netiquette