From: hpa@zytor.com
To: Peter Zijlstra <peterz@infradead.org>,
Steven Rostedt <rostedt@goodmis.org>
Cc: x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: The killing of ideal_nops[]
Date: Tue, 09 Mar 2021 16:33:45 -0800 [thread overview]
Message-ID: <362BD2A4-016D-4F6B-8974-92C84DC0DDB4@zytor.com> (raw)
In-Reply-To: <YEfnnFUbizbJUQig@hirez.programming.kicks-ass.net>
On March 9, 2021 1:24:44 PM PST, Peter Zijlstra <peterz@infradead.org> wrote:
>On Tue, Mar 09, 2021 at 12:05:19PM -0500, Steven Rostedt wrote:
>> On Tue, 9 Mar 2021 17:58:17 +0100
>> Peter Zijlstra <peterz@infradead.org> wrote:
>>
>> > Hi,
>> >
>> > AFAICT everything made in the past 10 years ends up using p6_nops.
>Is it
>> > time to kill off ideal_nops[] and simplify life?
>> >
>>
>> Well, the one bug that was reported recently was due to a box that
>uses a
>> different "ideal_nops" than p6_nops. Perhaps we should ask him if
>there's
>> any noticeable difference between using p6_nops for every function
>than the
>> ideal_nops that as found for that box.
>
>If the machine is more than a decade old, I'm not really caring about
>optimal performance. If it is 32bit, I really couldn't be arsed as long
>as it boots.
p6_nops don't boot on all 32-bit chips.
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
next prev parent reply other threads:[~2021-03-10 1:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-09 16:58 Peter Zijlstra
2021-03-09 17:05 ` Steven Rostedt
2021-03-09 21:24 ` Peter Zijlstra
2021-03-10 0:33 ` hpa [this message]
2021-03-10 9:14 ` Peter Zijlstra
2021-03-10 9:35 ` Peter Zijlstra
2021-03-10 10:03 ` Peter Zijlstra
2021-03-10 10:22 ` Peter Zijlstra
2021-03-10 14:13 ` Steven Rostedt
2021-03-10 14:24 ` Peter Zijlstra
2021-03-10 14:30 ` Peter Zijlstra
2021-03-10 15:48 ` Alexei Starovoitov
2021-03-10 16:04 ` Peter Zijlstra
2021-03-11 9:28 ` David Laight
2021-03-14 22:43 ` Maciej W. Rozycki
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=362BD2A4-016D-4F6B-8974-92C84DC0DDB4@zytor.com \
--to=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.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
all inboxes | Powered by JetHome®