From: "H. Peter Anvin" <hpa@zytor.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Andy Lutomirski <luto@amacapital.net>,
Linus Torvalds <torvalds@linux-foundation.org>,
Thomas Gleixner <tglx@linutronix.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
x86@kernel.org, Gleb Natapov <gleb@kernel.org>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [PATCH v2] x86: Return to kernel without IRET
Date: Sat, 03 May 2014 15:19:38 -0700 [thread overview]
Message-ID: <53656B7A.8050606@zytor.com> (raw)
In-Reply-To: <20140503072428.54f89688@gandalf.local.home>
On 05/03/2014 04:24 AM, Steven Rostedt wrote:
> On Fri, 02 May 2014 21:03:10 -0700
> "H. Peter Anvin" <hpa@zytor.com> wrote:
>
>>
>> I'd really like to see a workload which would genuinely benefit before
>> adding more complexity. Now... if we can determine that it doesn't harm
>> anything and would solve the NMI nesting problem cleaner than the
>> current solution, that would justify things, too...
>>
>
> As I stated before. It doesn't solve the NMI nesting problem. It only
> handles page faults. We would have to implement this for breakpoint
> return paths too. Is that a plan as well?
>
I would assume we would do it for *ALL* the IRETs. There are only three
IRETs in the kernel last I checked...
-hpa
next prev parent reply other threads:[~2014-05-03 22:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-02 23:53 [PATCH v2] x86: Return to kernel without IRET Andy Lutomirski
2014-05-03 4:03 ` H. Peter Anvin
2014-05-03 11:24 ` Steven Rostedt
2014-05-03 22:19 ` H. Peter Anvin [this message]
2014-05-03 23:51 ` Andy Lutomirski
2014-05-04 0:31 ` Andy Lutomirski
2014-05-04 2:15 ` H. Peter Anvin
2014-05-04 2:14 ` H. Peter Anvin
2014-05-05 15:47 ` Andy Lutomirski
2014-05-03 4:32 ` Linus Torvalds
2014-05-03 6:12 ` H. Peter Anvin
2014-05-03 13:54 ` Linus Torvalds
2014-05-03 19:00 ` H. Peter Anvin
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=53656B7A.8050606@zytor.com \
--to=hpa@zytor.com \
--cc=gleb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=pbonzini@redhat.com \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.