From: Borislav Petkov <bp@amd64.org>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>,
LKML <linux-kernel@vger.kernel.org>, x86 <x86@kernel.org>
Subject: Re: [PATCH] x86, AMD: Extend support to future families
Date: Sat, 12 Jun 2010 06:15:04 +0200 [thread overview]
Message-ID: <20100612041504.GB14077@aftab> (raw)
In-Reply-To: <4C101B58.2090208@zytor.com>
From: "H. Peter Anvin" <hpa@zytor.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@amd.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.
next prev parent reply other threads:[~2010-06-12 4:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-02 18:29 [PATCH] x86, AMD: Extend support to future families Borislav Petkov
2010-06-09 22:53 ` H. Peter Anvin
2010-06-12 4:15 ` Borislav Petkov [this message]
2010-06-12 18:22 ` H. Peter Anvin
2010-06-13 6:52 ` Borislav Petkov
2010-06-10 0:10 ` [tip:x86/cpu] " tip-bot for Borislav Petkov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100612041504.GB14077@aftab \
--to=bp@amd64.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox