From: Peter Zijlstra <peterz@infradead.org>
To: x86@kernel.org, Lai Jiangshan <jiangshanlai@gmail.com>,
Josh Poimboeuf <jpoimboe@redhat.com>
Cc: Andrew Cooper <Andrew.Cooper3@citrix.com>, linux-kernel@vger.kernel.org
Subject: Re: [RFC][PATCH] x86: PUSH_AND_CLEAR_REGS_COMPAT
Date: Sat, 9 Apr 2022 01:14:47 +0200 [thread overview]
Message-ID: <20220408231447.GS2731@worktop.programming.kicks-ass.net> (raw)
In-Reply-To: <20220408223827.GR2731@worktop.programming.kicks-ass.net>
On Sat, Apr 09, 2022 at 12:38:27AM +0200, Peter Zijlstra wrote:
>
> How insane?
Anyway, the questino is; since int80 doesn't wipe the high regs, can we
get away with the SYS*_compat things not doing that either and then all
using the normal PUSH_AND_CLEAR_REGS without having to invent _COMPAT
for that?
next prev parent reply other threads:[~2022-04-08 23:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-08 22:38 [RFC][PATCH] x86: PUSH_AND_CLEAR_REGS_COMPAT Peter Zijlstra
2022-04-08 23:14 ` Peter Zijlstra [this message]
2022-04-09 2:00 ` Josh Poimboeuf
2022-04-10 15:20 ` Brian Gerst
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=20220408231447.GS2731@worktop.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=Andrew.Cooper3@citrix.com \
--cc=jiangshanlai@gmail.com \
--cc=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.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