From: Arjan van de Ven <arjan@infradead.org>
To: Max Krasnyansky <maxk@qualcomm.com>
Cc: Peter Oruba <peter.oruba@amd.com>, Ingo Molnar <mingo@elte.hu>,
Thomas Gleixner <tglx@linutronix.de>,
Dmitry Adamushko <dmitry.adamushko@gmail.com>,
Tigran Aivazian <tigran@aivazian.fsnet.co.uk>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [patch 3/5] [PATCH 3/5] x86: Run Intel ucode-updates via workqueue.
Date: Wed, 6 Aug 2008 13:45:22 -0700 [thread overview]
Message-ID: <20080806134522.697b09f1@infradead.org> (raw)
In-Reply-To: <489A0A16.8060802@qualcomm.com>
On Wed, 06 Aug 2008 13:31:18 -0700
Max Krasnyansky <maxk@qualcomm.com> wrote:
> Arjan van de Ven wrote:
> > On Wed, 6 Aug 2008 17:21:20 +0200
> > Peter Oruba <peter.oruba@amd.com> wrote:
> >
> > [ no description or reason ]
> >
> > Why is this?
> >
> > I'm not very happy about this.. it means practically that this stuff
> > *has* to run late. Probably later than we want to.
> > (Like.. we may want to redo the microcode during resume.. which is
> > not a schedulable context)
>
> Dmitry and I tried to figure out how soon does it need to run.
you're not going to like the answer, but it's "as soon as possible".
Unlike normal boot, hotplug is a case where the bios hasn't been able
to put a normal microcode in.
> Nobody had a strong argument why it must run synchronously in the
> hotplug path.
Ok we as Intel really want it as early as possible.
> Sure we want it as soon as possible and I'd say
> workqueue is soon enough.
> Existing hotplug path does not guaranty any ordering and original
> microcode interface was driven from user-space. So clearly it was not
> considered very critical.
well that's why it changed to no longer use the userspace driven thing..
>
> Max
--
If you want to reach me at my work email, use arjan@linux.intel.com
For development, discussion and tips for power savings,
visit http://www.lesswatts.org
next prev parent reply other threads:[~2008-08-06 20:46 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-06 15:21 [patch 0/5] x86-microcode: run ucode update via workqueue Peter Oruba
2008-08-06 15:21 ` [patch 1/5] [PATCH 1/5] x86: microcode generic updates Peter Oruba
2008-08-11 19:24 ` Ingo Molnar
2008-08-06 15:21 ` [patch 2/5] [PATCH 2/5] x86: Minor correction to header file Peter Oruba
2008-08-11 19:25 ` Ingo Molnar
2008-08-06 15:21 ` [patch 3/5] [PATCH 3/5] x86: Run Intel ucode-updates via workqueue Peter Oruba
2008-08-06 15:44 ` Arjan van de Ven
2008-08-06 15:56 ` Dmitry Adamushko
2008-08-06 15:57 ` Dmitry Adamushko
2008-08-06 20:31 ` Max Krasnyansky
2008-08-06 20:45 ` Arjan van de Ven [this message]
2008-08-11 19:25 ` Ingo Molnar
2008-08-06 15:21 ` [patch 4/5] [PATCH 4/5] x86: Minor correction to Intel microcode patch loader Peter Oruba
2008-08-11 19:27 ` Ingo Molnar
2008-08-12 14:14 ` Peter Oruba
2008-08-06 15:21 ` [patch 5/5] [PATCH 5/5] x86: Run AMD microcode updates via workqueue Peter Oruba
2008-08-06 20:14 ` [patch 0/5] x86-microcode: run ucode update " Dmitry Adamushko
2008-08-06 20:35 ` Max Krasnyansky
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=20080806134522.697b09f1@infradead.org \
--to=arjan@infradead.org \
--cc=dmitry.adamushko@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maxk@qualcomm.com \
--cc=mingo@elte.hu \
--cc=peter.oruba@amd.com \
--cc=tglx@linutronix.de \
--cc=tigran@aivazian.fsnet.co.uk \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox