linux-kernel - Re: [PATCH] perf/x86: check ucode before disabling PEBS on SandyBridge

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4FD89CD3.8050005@zytor.com>
Date:	Wed, 13 Jun 2012 06:59:47 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Peter Zijlstra <peterz@...radead.org>
CC:	Borislav Petkov <bp@...64.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 06/13/2012 01:32 AM, Peter Zijlstra wrote:
> On Tue, 2012-06-12 at 21:49 +0200, Borislav Petkov wrote:
>>
>> But why, do you see a better option for how to tell the kernel to load a
>> binary blob early at boot? 
> 
> built it in? There's this feature where you can included firmware blobs
> in the kernel image. It has all the benefits of initrd, since the only
> time I ever would update initrd if used it, would be when I install a
> new kernel, which I just built anyway.
> 

You know you can build in an initramfs blob in the kernel, right?  In
fact, there always is one there even if you don't create it explicitly.

Problem solved, methinks.

	-hpa

-- 
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel.  I don't speak on their behalf.

--
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/