linux-kernel - Re: [GIT PULL] x86/cpu changes for v3.9

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: <20130219153655.GD26748@pd.tnic>
Date:	Tue, 19 Feb 2013 16:36:55 +0100
From:	Borislav Petkov <bp@...en8.de>
To:	Ingo Molnar <mingo@...nel.org>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	linux-kernel@...r.kernel.org, "H. Peter Anvin" <hpa@...or.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [GIT PULL] x86/cpu changes for v3.9

On Tue, Feb 19, 2013 at 04:25:03PM +0100, Ingo Molnar wrote:
> Linus,
> 
> Please pull the latest x86-cpu-for-linus git tree from:
> 
>    git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86-cpu-for-linus
> 
>    HEAD: f0322bd341fd63261527bf84afd3272bcc2e8dd3 x86, AMD: Enable WC+ memory type on family 10 processors
> 
> The biggest change is the enabling of the WC+ memory type on 
> family 10 processors. (This is a BIOS bug workaround in essence: 
> if the BIOS fails to do this then we fall back to uncacheable, 
> degrading performance, for example for virtualized guests using 
> nested pages.)
> 
>  Thanks,
> 
> 	Ingo
> 
> ------------------>
> Boris Ostrovsky (2):
>       x86, AMD: Clean up init_amd()
>       x86, AMD: Enable WC+ memory type on family 10 processors

Those kill a kvm guest with a #GP. Can we apply the fix for it too pls?

http://marc.info/?l=linux-kernel&m=136077007423065&w=2

-- 
Regards/Gruss,
    Boris.

Sent from a fat crate under my desk. Formatting is fine.
--
--
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/