From: Andi Kleen <ak@linux.intel.com>
To: whiteheadm@acm.org
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: x86: Fix AMD K6 indirect call check v2
Date: Mon, 21 May 2018 07:10:09 -0700 [thread overview]
Message-ID: <20180521141009.GG4486@tassilo.jf.intel.com> (raw)
In-Reply-To: <CAP8WD_apEh=a8m2zJtUwcFpMRYh3ffjTbT5983413hrfE0w05w@mail.gmail.com>
On Mon, May 21, 2018 at 07:13:37AM -0400, tedheadster wrote:
> Andi,
> I have a K6 regression testing system. I think my K6 is a revision
> C, but I probably can get an earlier cpu (with the bug) to test on.
>
> Do you have any specific tests you would want me to do on the affected cpu?
You answered to an ancient email? Can barely remember what it was about.
But I think if it still boots it's likely fine.
-Andi
prev parent reply other threads:[~2018-05-21 14:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-21 11:13 x86: Fix AMD K6 indirect call check v2 tedheadster
2018-05-21 14:10 ` Andi Kleen [this message]
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=20180521141009.GG4486@tassilo.jf.intel.com \
--to=ak@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=whiteheadm@acm.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