From: Shuah Khan <shuahkhan@gmail.com>
To: Ingo Molnar <mingo@kernel.org>
Cc: shuahkhan@gmail.com, Henrique de Moraes Holschuh <hmh@hmh.eng.br>,
Borislav Petkov <bp@alien8.de>, "H. Peter Anvin" <hpa@zytor.com>,
mingo@redhat.com, tglx@linutronix.de,
tigran@aivazian.fsnet.co.uk,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH RESEND] x86: kernel/microcode_core.c simple_strtoul cleanup
Date: Tue, 08 May 2012 14:42:43 -0600 [thread overview]
Message-ID: <1336509763.7416.30.camel@lorien2> (raw)
In-Reply-To: <20120508040009.GB30652@gmail.com>
On Tue, 2012-05-08 at 06:00 +0200, Ingo Molnar wrote:
> * Henrique de Moraes Holschuh <hmh@hmh.eng.br> wrote:
>
> > > Of course, one can iterate over each core in a shell-loop
> > > and write into the reload file to reload ucode after having
> > > updated the ucode image in /lib/firmware but removing and
> > > then modprobing the module is shorter :-)
> >
> > Can we PLEASE fix it properly by adding a new node (which is
> > _not_ per-cpu) that requests the microcode core to refresh all
> > cpus? Preferably by invalidating the microcode cache, THEN
> > fetching each required microcode just once for the first core
> > that needs it, and caching it for use the other cores. You
> > can leave the (IMHO mostly useless) per-cpu sysfs nodes alone,
> > so as to not break ABI, or deprecate them for an year or
> > something.
> >
> > I am speaking this with my userland maintainer hat. I *do
> > NOT* want to rmmod crap in a production server to update
> > microcode. And I want to be able to support static-compiled
> > microcode.
>
> Seconded. There's also the ability to disable module unloading.
I will take a stab at the disabling module unloading if I may. The rest
of the tasks are a bit out of my league at this time. :)
Thanks,
-- Shuah
next prev parent reply other threads:[~2012-05-08 20:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-06 17:11 [PATCH RESEND] x86: kernel/microcode_core.c simple_strtoul cleanup Shuah Khan
2012-05-07 10:49 ` Borislav Petkov
2012-05-07 18:35 ` H. Peter Anvin
2012-05-07 21:16 ` Borislav Petkov
2012-05-08 1:23 ` Henrique de Moraes Holschuh
2012-05-08 4:00 ` Ingo Molnar
2012-05-08 20:42 ` Shuah Khan [this message]
2012-05-09 7:00 ` Borislav Petkov
2012-05-07 20:49 ` [tip:x86/microcode] x86, microcode: microcode_core. c " tip-bot for Shuah Khan
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=1336509763.7416.30.camel@lorien2 \
--to=shuahkhan@gmail.com \
--cc=bp@alien8.de \
--cc=hmh@hmh.eng.br \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=mingo@redhat.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 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.