linux-kernel - Re: [PATCH] x86, AMD: Extend support to future families

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: <20100612041504.GB14077@aftab>
Date:	Sat, 12 Jun 2010 06:15:04 +0200
From:	Borislav Petkov <bp@...64.org>
To:	"H. Peter Anvin" <hpa@...or.com>
Cc:	Ingo Molnar <mingo@...e.hu>, Thomas Gleixner <tglx@...utronix.de>,
	LKML <linux-kernel@...r.kernel.org>, x86 <x86@...nel.org>
Subject: Re: [PATCH] x86, AMD: Extend support to future families

From: "H. Peter Anvin" <hpa@...or.com>
Date: Wed, Jun 09, 2010 at 06:53:12PM -0400

> On 06/02/2010 11:29 AM, Borislav Petkov wrote:
> > Extend support to future families, and in particular:
> > 
> > * extend direct mapping split of Tseg SMM area.
> > * extend K8 flavored alternatives (NOPS).
> > * rep movs* prefix is fast in ucode.
> > 
> > Signed-off-by: Borislav Petkov <borislav.petkov@....com>
> 
> This doesn't reflect any currently shipping hardware, right?

Not yet. And I'm assuming you're driving at tagging it for -stable?
If yes, I think a stable tag makes sense since this way the distros
will pick it up more easily and we most definitely will need to do the
backport later otherwise.

Do you need another version with the stable tag resent or is it easier
for you to edit the commit message of the one you have already?

Thanks.

-- 
Regards/Gruss,
Boris.

Operating Systems Research Center
Advanced Micro Devices, Inc.
--
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/