From: Andreas Herrmann <andreas.herrmann3@amd.com>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: Dmitry Adamushko <dmitry.adamushko@gmail.com>,
Ingo Molnar <mingo@elte.hu>,
linux-kernel@vger.kernel.org
Subject: Re: x86-microcode: get rid of set_cpus_allowed()
Date: Thu, 12 Mar 2009 18:58:07 +0100 [thread overview]
Message-ID: <20090312175807.GJ20716@alberich.amd.com> (raw)
In-Reply-To: <20090312174010.GI20716@alberich.amd.com>
On Thu, Mar 12, 2009 at 06:40:10PM +0100, Andreas Herrmann wrote:
> 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.
Some further testing seem to indicate that suspend/resume does not
work when I have done CPU hotplug before.
During today's tests I did:
(1) set offline/online CPU 1 and 2
(2) perform suspend/resume afterwards
After that microcode update failed on some CPUs when performing
suspend/resume. (When skipping step 1, microcode update during
suspend/resume works.)
Looks strange, but should be debuggable.
Regards,
Andreas
--
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
next prev parent reply other threads:[~2009-03-12 17:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-09 19:38 x86-microcode: get rid of set_cpus_allowed() Dmitry Adamushko
2009-03-11 6:44 ` Rusty Russell
2009-03-12 17:40 ` Andreas Herrmann
2009-03-12 17:58 ` Andreas Herrmann [this message]
2009-03-13 3:31 ` Ingo Molnar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090312175807.GJ20716@alberich.amd.com \
--to=andreas.herrmann3@amd.com \
--cc=dmitry.adamushko@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rusty@rustcorp.com.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.