[lkml]   [2009]   [Mar]   [12]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: x86-microcode: get rid of set_cpus_allowed()
On Wed, Mar 11, 2009 at 07:44:37AM +0100, Rusty Russell wrote:
> On Tuesday 10 March 2009 06:08:59 Dmitry Adamushko wrote:
> >
> > Hi,
> >
> >
> > here is a possible candidate for Rusty's cpumask-refactored series.
> > Note the [*] remark below though.
> Ah, OK, I'll drop my version then (below) in favor of this, and will
> push to Ingo with the others if he doesn't take it directly.

Sorry guys -- for the late reply --
but I missed Dmitry's mail due to some silly mail filtering and had to
restore his mail ...

Now I've tested both patches and both seem to reliably prevent
microcode updates on CPU1 and CPU2 of an Phenom X3 after
suspend/resume. (Just CPU0 was updated.)

Then I've tested mainline kernel w/o your patches and I've observed
similar problems. I've seen that sometimes ucode of CPU0 was not
updated and sometimes CPU1 and CPU2 were not updated.

I'll look into this asap.


Operating | Advanced Micro Devices GmbH
System | Karl-Hammerschmidt-Str. 34, 85609 Dornach b. München, Germany
Research | Geschäftsführer: Jochen Polster, Thomas M. McCoy, Giuliano Meroni
Center | Sitz: Dornach, Gemeinde Aschheim, Landkreis München
(OSRC) | Registergericht München, HRB Nr. 43632

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2009-03-12 18:43    [W:0.091 / U:4.744 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site