From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Borislav Petkov <bp@amd64.org>
Cc: "Srivatsa S. Bhat" <srivatsa.bhat@linux.vnet.ibm.com>,
Ingo Molnar <mingo@elte.hu>,
"tigran@aivazian.fsnet.co.uk" <tigran@aivazian.fsnet.co.uk>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"mingo@redhat.com" <mingo@redhat.com>,
"hpa@zytor.com" <hpa@zytor.com>,
"x86@kernel.org" <x86@kernel.org>,
"Herrmann3, Andreas" <Andreas.Herrmann3@amd.com>,
"amd64-microcode@amd64.org" <amd64-microcode@amd64.org>,
Tejun Heo <tj@kernel.org>,
Linux PM mailing list <linux-pm@vger.kernel.org>,
"linux-kernel" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH RESEND] CPU hotplug,x86 Microcode: Don't request microcode from userspace unnecessarily
Date: Mon, 10 Oct 2011 23:18:26 +0200 [thread overview]
Message-ID: <201110102318.27146.rjw@sisk.pl> (raw)
In-Reply-To: <20111010211300.GA31606@aftab>
On Monday, October 10, 2011, Borislav Petkov wrote:
> On Mon, Oct 10, 2011 at 04:58:02PM -0400, Rafael J. Wysocki wrote:
> > On Sunday, October 09, 2011, Srivatsa S. Bhat wrote:
> > > Requesting the microcode from userspace *every time* when onlining CPUs
> > > (during a CPU hotplug operation) is unnecessary.
> > >
> > > So, this patch ensures that once the kernel gets the microcode after booting,
> > > it is not freed nor invalidated when a CPU goes offline, so that it can be
> > > reused when that CPU comes back online, without requesting userspace for it
> > > again. As a result, the CPU hotplug operations become faster as well.
> > >
> > > Tested-by: Borislav Petkov <bp@amd64.org>
> > > Acked-by: Borislav Petkov <bp@amd64.org>
> > >
> > > Signed-off-by: Srivatsa S. Bhat <srivatsa.bhat@linux.vnet.ibm.com>
> >
> > Fine by me. I wonder who should take this?
>
> Ingo, most probably. ucode stuff goes in through -tip.
OK, so
Acked-by: Rafael J. Wysocki <rjw@sisk.pl>
Thanks,
Rafael
next prev parent reply other threads:[~2011-10-10 21:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-08 20:47 [PATCH] " Srivatsa S. Bhat
2011-10-09 11:27 ` Borislav Petkov
2011-10-09 19:38 ` Srivatsa S. Bhat
2011-10-09 19:42 ` [PATCH RESEND] " Srivatsa S. Bhat
2011-10-10 20:58 ` Rafael J. Wysocki
2011-10-10 21:13 ` Borislav Petkov
2011-10-10 21:18 ` Rafael J. Wysocki [this message]
2011-10-11 8:41 ` Andreas Herrmann
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=201110102318.27146.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=Andreas.Herrmann3@amd.com \
--cc=amd64-microcode@amd64.org \
--cc=bp@amd64.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mingo@redhat.com \
--cc=srivatsa.bhat@linux.vnet.ibm.com \
--cc=tglx@linutronix.de \
--cc=tigran@aivazian.fsnet.co.uk \
--cc=tj@kernel.org \
--cc=x86@kernel.org \
/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
all inboxes | Powered by JetHome®