Received: by 2002:ac0:a5b6:0:0:0:0:0 with SMTP id m51-v6csp1084527imm; Thu, 31 May 2018 15:07:13 -0700 (PDT) X-Google-Smtp-Source: ADUXVKL4E1ud5Vg9AK5TqqNNKKrETpCF5Bd5NbSo+3nsFnptLjQfrdmC8pYQC+hemSQKW5c4kjoq X-Received: by 2002:a17:902:a5c7:: with SMTP id t7-v6mr8644806plq.360.1527804433499; Thu, 31 May 2018 15:07:13 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1527804433; cv=none; d=google.com; s=arc-20160816; b=O1/GQHNy4jat5/T282zR4Mt7r0GmfiPXP2IituN3z6yxoYB1FNSRNLQ9fVei3GzWJE twcyFsIKD0HQn7yBW0ChaqegHcQmAfTdO2VJoLvRhfxSgsN/A5FndOhn961aF+iz1Z/h 8dG7iCMZROTha2hYnSPbVyj7hEdVeLf5onvWiIDqxVBYJbA2t16+ia3RFZxejXFGJofw Bdn0zM2/glyNVXVzP6cTdWyluRCWNH4AKe8Ul/9wpm1bkwOZ8iwjmAbTvItk08VrgEou /W3mYBHVn02AlUuXZa2R1gThK4EqCdidtNyKJIvQ8zbYSYktXnIJ8TL8zxsoZEZlCA+d IR7g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:dkim-signature:dkim-signature :arc-authentication-results; bh=Cy6Yhyb6SY3zE4GukyHcduhxI3wtu5I3Ljjc0hl0H14=; b=xm232Fnqi1aNchdBj0DQ2CbAdsZvHgzxNS3diADeE+EsH+3BPGFocjHawLtNy39V09 TWvRJd939LP0zOGv1pMmgjokd+3sudNoqOZTgYNk52d4WU2kgCmu3673L/NgwHw/Q3kB anooSQGDe7gl6odfAQ9vUdNMtvmf7pbxpgh+B0DCTVoY+ZvJVHVL7BbqGYNo1bTz+2bU uF9xgh+sk/4DsyI+hU3y8Qg+hoxcvBChgRRAvYTlHU10vYEs5YWkD2jXJtdNQXlcENm6 Hv+QrkmgtFhITes5oLPErLZ0/2Wc2Os+znIm/g2WKo3tftM68+/udUIGRmNO5+ciwnKy 5qkw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@hmh.eng.br header.s=fm2 header.b=FdFwU2EF; dkim=pass header.i=@messagingengine.com header.s=fm2 header.b=PrJUZ6D6; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id r72-v6si8369649pfb.65.2018.05.31.15.06.40; Thu, 31 May 2018 15:07:13 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@hmh.eng.br header.s=fm2 header.b=FdFwU2EF; dkim=pass header.i=@messagingengine.com header.s=fm2 header.b=PrJUZ6D6; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1750758AbeEaWFJ (ORCPT + 99 others); Thu, 31 May 2018 18:05:09 -0400 Received: from out1-smtp.messagingengine.com ([66.111.4.25]:34183 "EHLO out1-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750711AbeEaWFI (ORCPT ); Thu, 31 May 2018 18:05:08 -0400 Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.nyi.internal (Postfix) with ESMTP id 25B5021B74; Thu, 31 May 2018 18:05:07 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute5.internal (MEProxy); Thu, 31 May 2018 18:05:07 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hmh.eng.br; h=cc :content-type:date:from:in-reply-to:message-id:mime-version :references:subject:to:x-me-sender:x-me-sender:x-sasl-enc; s= fm2; bh=Cy6Yhyb6SY3zE4GukyHcduhxI3wtu5I3Ljjc0hl0H14=; b=FdFwU2EF +CXQzg+rf+ob72tzviFKj1hzaL6owNzmqWJogCbMRH6wTupknmvsYFp4HezRKu/8 qvgQzIYaNfUR+hvvu+sUzSEOpCoy9E5kxMPCTzMXGXsv4b0Yjh7PFUbDUM5ORZmI Nx3mCZqyTHlj+evoEFt9hVE9KUwcVeQc9V5fWZ4aLRUW5K9kip0gniclKc8yb0gt +/0lPnOi/D3QQXRbXFKxtYLXy8PYYZT2XWoPuA3cHrxwENlzK7R1H09N/gjYzT81 c2R8sUwtIlo4FQbd0Yf8QxxGPMA2uNh+FH+X41th4sfvKePn8/qXdRHma4Ai0M/N P6EODbaZAHPi5Q== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm2; bh=Cy6Yhyb6SY3zE4GukyHcduhxI3wtu 5I3Ljjc0hl0H14=; b=PrJUZ6D6AP2jKFqjU519uMOWIqRCDrhManiS4UhMsIm0o P2BF9e01v+rD44zV/Xx/o3nyUQ6nXqlILPbxg62k8Krt9+8DbdbIE3096+GxIcr7 Y4Ozr+TT87KH8eb0+q/Ex9juIuhFPbPD1NrkoeJ3y3mnaDDHKS3HTLsqVXE0B9xd xE1YuwgAJNnfnph1sYsqQu67nlJHaGVE70fvTPc2UB00USMZgotUpGUEDSo+PGfi rNw5HiFtLPHtTwJ8C0seM7h1Fs9s32yrtVabjL7btOYq/o241EIRELGzim2x6+jm 3Oxnvb/Ev5dfySfeknMRuZPBcgC4dIA4B7ZVqUlxg== X-ME-Proxy: X-ME-Proxy: X-ME-Proxy: X-ME-Proxy: X-ME-Proxy: X-ME-Proxy: X-ME-Sender: Received: from khazad-dum.debian.net (unknown [201.53.245.99]) by mail.messagingengine.com (Postfix) with ESMTPA id 783061026E; Thu, 31 May 2018 18:05:06 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by localhost.khazad-dum.debian.net (Postfix) with ESMTP id AAB5E340131D; Thu, 31 May 2018 19:05:04 -0300 (-03) X-Virus-Scanned: Debian amavisd-new at khazad-dum.debian.net Received: from khazad-dum.debian.net ([127.0.0.1]) by localhost (khazad-dum2.khazad-dum.debian.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id d6UcXyKViU7o; Thu, 31 May 2018 19:05:03 -0300 (-03) Received: by khazad-dum.debian.net (Postfix, from userid 1000) id CAF993400BEA; Thu, 31 May 2018 19:05:03 -0300 (-03) Date: Thu, 31 May 2018 19:05:03 -0300 From: Henrique de Moraes Holschuh To: Ivan Ivanov Cc: Josh Boyer , Sherry Hurwitz , Linux Firmware , "Linux-Kernel@Vger. Kernel. Org" , Rudolf Marek , suravee.suthikulpanit@amd.com Subject: Re: [PATCH 1/1] Update AMD cpu microcode for family 15h Message-ID: <20180531220503.2jqs3oiqsnw7ye2t@khazad-dum.debian.net> References: <1527213479-121361-1-git-send-email-sherry.hurwitz@amd.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-GPG-Fingerprint1: 4096R/0x0BD9E81139CB4807: C467 A717 507B BAFE D3C1 6092 0BD9 E811 39CB 4807 User-Agent: NeoMutt/20170113 (1.7.2) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 30 May 2018, Ivan Ivanov wrote: > This is still not addressing the outdated 15h microcode version issue > that Rudolf Marek has pointed out. Also, we still hope to see an > updated microcode for 16h architecture as well - it has not received > any updates for two years already True, but now at least it won't regress old boxes anymore, so we can ship it in the stable branches of the distros with less restrictions. It would be really good to be able to actually mitigate spectre v2/v4 on most AMD systems, though. And current experience shows this is only going to happen if we can have the required microcode update also going through the operating system update channels. -- Henrique Holschuh