From: "H. Peter Anvin" <h.peter.anvin@intel.com>
To: Linus Torvalds <torvalds@linux-foundation.org>,
Andy Lutomirski <luto@amacapital.net>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
the arch/x86 maintainers <x86@kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
Gleb Natapov <gleb@kernel.org>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [RFC/HACK] x86: Fast return to kernel
Date: Fri, 02 May 2014 13:07:33 -0700 [thread overview]
Message-ID: <5363FB05.4000302@intel.com> (raw)
In-Reply-To: <CA+55aFygkoYnJKdLas3WOq9q9pCEEk6mBOuj-zbLyLumdhStAA@mail.gmail.com>
On 05/02/2014 12:51 PM, Linus Torvalds wrote:
> On Fri, May 2, 2014 at 12:31 PM, Linus Torvalds
> <torvalds@linux-foundation.org> wrote:
>>
>> Also, are you *really* sure that "popf" has the same one-instruction
>> interrupt shadow that "sti" has? Because I'm not at all sure that is
>> true, and it's not documented as far as I can tell. In contrast, the
>> one-instruction shadow after "sti" very much _is_ documented.
>
> Yeah, I'm pretty sure about this. The only instructions with an
> interrupt shadow are "sti", "mov ss" and "pop ss".
>
I believe you are correct here.
-hpa
next prev parent reply other threads:[~2014-05-02 20:07 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-02 19:04 [RFC/HACK] x86: Fast return to kernel Andy Lutomirski
2014-05-02 19:31 ` Linus Torvalds
2014-05-02 19:50 ` Andy Lutomirski
2014-05-04 18:40 ` Ingo Molnar
2014-05-04 19:59 ` H. Peter Anvin
2014-05-04 21:31 ` Linus Torvalds
2014-05-04 22:01 ` H. Peter Anvin
2014-05-02 19:51 ` Linus Torvalds
2014-05-02 20:07 ` H. Peter Anvin [this message]
2014-05-02 20:30 ` Thomas Gleixner
2014-05-02 21:01 ` Linus Torvalds
2014-05-02 21:04 ` Andy Lutomirski
2014-05-02 21:07 ` Linus Torvalds
2014-05-02 21:37 ` H. Peter Anvin
2014-05-02 21:42 ` Andy Lutomirski
2014-05-02 21:44 ` H. Peter Anvin
2014-05-02 21:28 ` Thomas Gleixner
2014-05-04 23:46 ` Paolo Bonzini
2014-05-04 23:49 ` H. Peter Anvin
2014-05-02 20:19 ` Steven Rostedt
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=5363FB05.4000302@intel.com \
--to=h.peter.anvin@intel.com \
--cc=gleb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=pbonzini@redhat.com \
--cc=rostedt@goodmis.org \
--cc=torvalds@linux-foundation.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