linux-kernel - [RFC][PATCH 0/2] x86, CPU: Run stuff on the BSP

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-next>] [day] [month] [year] [list]

Date:	Mon,  8 Aug 2011 20:57:50 +0200
From:	Borislav Petkov <bp@...64.org>
To:	"H. Peter Anvin" <hpa@...or.com>
Cc:	X86-ML <x86@...nel.org>, LKML <linux-kernel@...r.kernel.org>,
	Borislav Petkov <borislav.petkov@....com>
Subject: [RFC][PATCH 0/2] x86, CPU: Run stuff on the BSP

From: Borislav Petkov <borislav.petkov@....com>

Ok,

this is just an RFC and it builds but no further tests have been done on
it. The first patch is a trivial cleanup and can go in.

For the second one I opted to look at c->x86_vendor in cpu/common.c
which is not very clean but still simpler than adding a miscellaneous
struct to contain the ->run_on_bsp() pointer and be statically allocated
as __initdata, in the cpu_dev fashion. We can always do that later if
there's more ofthe similar functionality needed.

Hmm, so please take a look and let me know if this is going in the right
direction.

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