From: Denys Vlasenko <dvlasenk@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "Ingo Molnar" <mingo@kernel.org>,
"Andy Lutomirski" <luto@kernel.org>,
"Dan Williams" <dan.j.williams@intel.com>,
"Alex Deucher" <alexander.deucher@amd.com>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
"Christian König" <christian.koenig@amd.com>,
"Vinod Koul" <vinod.koul@intel.com>,
"Johannes Berg" <johannes.berg@intel.com>,
"Sara Sharon" <sara.sharon@intel.com>,
"Adrian Hunter" <adrian.hunter@intel.com>,
"the arch/x86 maintainers" <x86@kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: RFC: Petition Intel/AMD to add POPF_IF insn
Date: Wed, 17 Aug 2016 20:41:34 +0200 [thread overview]
Message-ID: <8de26c33-5597-bf00-2ac5-d265ba01d0d4@redhat.com> (raw)
In-Reply-To: <CA+55aFy0zq5h7zXcL7KNZuhvVHUZvA__U4ztJvP_WTCN+dub2g@mail.gmail.com>
On 08/17/2016 07:32 PM, Linus Torvalds wrote:
> On Wed, Aug 17, 2016 at 10:20 AM, Denys Vlasenko <dvlasenk@redhat.com> wrote:
>> Last year, a proposal was floated to avoid costly POPF.
>> In particular, each spin_unlock_irqrestore() does it,
>> a rather common operation.
>
> Quiet frankly, it takes so long for hw features that I don't think
> it's worth it for something like this.
True, it will take some ~5 years for new hardware to become
widely used.
OTOH 5 years will inevitably pass. Just like now 32-bit Linux userspace
is commonly compiled to "i686" instruction set, because
inevitably enough time has passed that you can safely assume
most people run at least Pentium Pro-level CPU, with CMOV, CMPXCHG,
etc.
If the new instruction will be implemented with "REPZ POPF" encoding,
no recompilation or alternatives will be needed for the new kernel
to run on an old CPU. On an old CPU, entire EFLAGS will be restored.
On a new one, only EFLAGS.IF.
next prev parent reply other threads:[~2016-08-17 18:51 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-17 17:20 Denys Vlasenko
2016-08-17 17:30 ` Christian König
2016-08-17 18:34 ` Denys Vlasenko
2016-08-17 17:32 ` Linus Torvalds
2016-08-17 18:41 ` Denys Vlasenko [this message]
[not found] ` <CA+55aFwmxwQBkyDjombS4cy1q=a_buhmDjDnaa8rdC8ZDaDYEA@mail.gmail.com>
2016-08-17 19:13 ` Andy Lutomirski
2016-08-17 19:26 ` Denys Vlasenko
2016-08-17 19:32 ` Linus Torvalds
2016-08-17 19:35 ` Denys Vlasenko
2016-08-17 19:54 ` Linus Torvalds
2016-08-17 19:37 ` Linus Torvalds
2016-08-17 21:26 ` Linus Torvalds
2016-08-17 21:35 ` Linus Torvalds
2016-08-17 21:43 ` Andy Lutomirski
2016-08-17 21:48 ` Linus Torvalds
2016-08-18 13:26 ` Denys Vlasenko
2016-08-18 17:24 ` Linus Torvalds
2016-08-18 17:47 ` Denys Vlasenko
2016-08-18 17:49 ` Denys Vlasenko
2016-08-19 10:54 ` Paolo Bonzini
2016-08-31 11:12 ` Denys Vlasenko
2016-08-18 9:21 ` Denys Vlasenko
2016-08-18 12:18 ` Denys Vlasenko
2016-08-18 17:22 ` Paolo Bonzini
2016-08-17 19:29 ` Linus Torvalds
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=8de26c33-5597-bf00-2ac5-d265ba01d0d4@redhat.com \
--to=dvlasenk@redhat.com \
--cc=adrian.hunter@intel.com \
--cc=alexander.deucher@amd.com \
--cc=christian.koenig@amd.com \
--cc=dan.j.williams@intel.com \
--cc=johannes.berg@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@kernel.org \
--cc=rafael.j.wysocki@intel.com \
--cc=sara.sharon@intel.com \
--cc=torvalds@linux-foundation.org \
--cc=vinod.koul@intel.com \
--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®