From: Oleg Nesterov <oleg@redhat.com>
To: Andy Lutomirski <luto@kernel.org>, Borislav Petkov <bp@alien8.de>,
Brian Gerst <brgerst@gmail.com>, Ingo Molnar <mingo@redhat.com>,
Peter Anvin <hpa@zytor.com>
Cc: linux-kernel@vger.kernel.org, x86@kernel.org
Subject: Q: does force_iret() make any sense today?
Date: Wed, 18 Dec 2019 16:31:07 +0100 [thread overview]
Message-ID: <20191218153107.GA3489@redhat.com> (raw)
I do not pretend I understand the arch/x86/entry/ code, but it seems that
asm does all the necessary checks and the "extra" TIF_NOTIFY_RESUME simply
has no effect except tracehook_notify_resume() will be called for no reason?
Oleg.
next reply other threads:[~2019-12-18 15:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-18 15:31 Oleg Nesterov [this message]
2019-12-18 15:45 ` Q: does force_iret() make any sense today? Brian Gerst
2019-12-18 16:06 ` Oleg Nesterov
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=20191218153107.GA3489@redhat.com \
--to=oleg@redhat.com \
--cc=bp@alien8.de \
--cc=brgerst@gmail.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.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