[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20120612203730.GE11137@aftab.osrc.amd.com>
Date: Tue, 12 Jun 2012 22:37:30 +0200
From: Borislav Petkov <bp@...64.org>
To: "H. Peter Anvin" <hpa@...or.com>
Cc: Peter Zijlstra <peterz@...radead.org>,
Stephane Eranian <eranian@...gle.com>,
linux-kernel@...r.kernel.org, andi@...stfloor.org, mingo@...e.hu,
ming.m.lin@...el.com, "Yu, Fenghua" <fenghua.yu@...el.com>
Subject: Re: [PATCH] perf/x86: check ucode before disabling PEBS on
SandyBridge
On Tue, Jun 12, 2012 at 01:28:55PM -0700, H. Peter Anvin wrote:
> On 06/12/2012 12:49 PM, Borislav Petkov wrote:
> >
> > Also, I'd assume we need some of the current functionality to be able to
> > load ucode without rebooting the box.
> >
>
> Yes, the basic idea is that we'll keep the ucode around anyway so we can
> feed it to hotplug CPUs or S3 resume. If the ucode is updated from
> userspace we'd replace the in-memory copy and load it into the CPUs.
You say CPUs, i.e. plural. What is your take on loading ucode on a
single core, i.e. the /sys/devices/system/cpu/cpuX/microcode/reload
interface? Do you guys need to load ucode only system-wide or can you
stomach per-core loads?
I want to disable it (or even remove it, modulo the whole userspace
compat blah blah) on AMD.
Also, if we do system-wide, can we have a single sysfs node where we
give the new ucode from userspace instead of per-cpu files?
--
Regards/Gruss,
Boris.
Advanced Micro Devices GmbH
Einsteinring 24, 85609 Dornach
GM: Alberto Bozzo
Reg: Dornach, Landkreis Muenchen
HRB Nr. 43632 WEEE Registernr: 129 19551
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists