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;
Date:   Sat, 17 Feb 2018 11:42:48 -0200
From:   Henrique de Moraes Holschuh <hmh@hmh.eng.br>
To:     Ashok Raj <ashok.raj@intel.com>
Cc:     bp@suse.de, X86 ML <x86@kernel.org>,
        LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] x86/microcode: Check microcode revision before updating
 sibling threads
Message-ID: <20180217134247.sccdynjiqnk2mjby@khazad-dum.debian.net>
References: <1518806808-4074-1-git-send-email-ashok.raj@intel.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1518806808-4074-1-git-send-email-ashok.raj@intel.com>
User-Agent: NeoMutt/20170113 (1.7.2)
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On Fri, 16 Feb 2018, Ashok Raj wrote:
> After updating microcode on one of the threads in the core, the
> thread sibling automatically gets the update since the microcode
> resources are shared. Check the ucode revision on the cpu before
> performing a ucode update.

I wonder when this broke, because it used to do that just fine.

I even had to explain to a couple Debian users that no, nothing was
broken and yes, while it looked like the kernel was skipping some
"CPUs", it was actually updating all of them...

-- 
  Henrique Holschuh