From: Borislav Petkov <bp@alien8.de>
To: Mikulas Patocka <mpatocka@redhat.com>
Cc: linux-tip-commits@vger.kernel.org, brgerst@gmail.com,
dvlasenk@redhat.com, peterz@infradead.org, mpatocka@redhat.com,
hpa@zytor.com, tglx@linutronix.de, linux-kernel@vger.kernel.org,
luto@kernel.org, jpoimboe@redhat.com,
torvalds@linux-foundation.org, mingo@kernel.org
Subject: Re: [tip:x86/urgent] x86/cpu: Use indirect call to measure performance in init_amd_k6()
Date: Wed, 12 Jul 2017 15:48:44 +0200 [thread overview]
Message-ID: <20170712134844.GA20580@nazgul.tnic> (raw)
In-Reply-To: <tip-429ed86b5c99b388543f6f7f6983b1230326f2bb@git.kernel.org>
On Wed, Jul 12, 2017 at 06:09:57AM -0700, tip-bot for Mikulas Patocka wrote:
> Commit-ID: 429ed86b5c99b388543f6f7f6983b1230326f2bb
> Gitweb: http://git.kernel.org/tip/429ed86b5c99b388543f6f7f6983b1230326f2bb
> Author: Mikulas Patocka <mpatocka@redhat.com>
> AuthorDate: Tue, 11 Jul 2017 07:44:05 -0400
> Committer: Ingo Molnar <mingo@kernel.org>
> CommitDate: Wed, 12 Jul 2017 10:42:32 +0200
>
> x86/cpu: Use indirect call to measure performance in init_amd_k6()
>
> This old piece of code is supposed to measure the performance of indirect
> calls to determine if the processor is buggy or not, however the compiler
> optimizer turns it into a direct call.
Are you booting on a real K6 or qemu?
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
--
next prev parent reply other threads:[~2017-07-12 13:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-11 11:44 [PATCH] x86/kernel/cpu/amd.c: use indirect call Mikulas Patocka
2017-07-12 13:09 ` [tip:x86/urgent] x86/cpu: Use indirect call to measure performance in init_amd_k6() tip-bot for Mikulas Patocka
2017-07-12 13:48 ` Borislav Petkov [this message]
2017-07-13 2:20 ` Mikulas Patocka
2017-07-16 9:14 ` tip-bot for Mikulas Patocka
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=20170712134844.GA20580@nazgul.tnic \
--to=bp@alien8.de \
--cc=brgerst@gmail.com \
--cc=dvlasenk@redhat.com \
--cc=hpa@zytor.com \
--cc=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@kernel.org \
--cc=mpatocka@redhat.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®