From: Andi Kleen <andi@firstfloor.org>
To: Ingo Molnar <mingo@kernel.org>
Cc: Andi Kleen <andi@firstfloor.org>,
x86@kernel.org, linux-kernel@vger.kernel.org,
Andi Kleen <ak@linux.intel.com>
Subject: Re: [PATCH] x86: Fix AMD K6 indirect call check
Date: Sun, 21 Apr 2013 16:29:00 +0200 [thread overview]
Message-ID: <20130421142900.GV16732@two.firstfloor.org> (raw)
In-Reply-To: <20130421095843.GB10683@gmail.com>
> Would be useful to read in the changelog about how you found the bug:
>
> - saw miscalculated values and figured out the reason
> - saw a new warning in GCC
> - saw it during review
>
> ?
Saw it during code review when I was fixing the code for LTO.
I don't have a K6 anymore, but I still have fond memories of my K6
system.
-Andi
prev parent reply other threads:[~2013-04-21 14:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-21 3:35 [PATCH] x86: Fix AMD K6 indirect call check Andi Kleen
2013-04-21 9:58 ` Ingo Molnar
2013-04-21 14:29 ` 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=20130421142900.GV16732@two.firstfloor.org \
--to=andi@firstfloor.org \
--cc=ak@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--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