public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: houdek.ryan@fex-emu.org
Cc: linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org,
	Ryan Houdek <Houdek.Ryan@fex-emu.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Andy Lutomirski <luto@kernel.org>
Subject: Re: [PATCH 1/4] Move userspace syscall dispatch outside of common entry
Date: Wed, 02 Jun 2021 17:41:53 +0200	[thread overview]
Message-ID: <871r9k1dfi.ffs@nanos.tec.linutronix.de> (raw)
In-Reply-To: <20210529081620.164422-2-Houdek.Ryan@fex-emu.org>

On Sat, May 29 2021 at 01:16, houdek ryan wrote:
> From: Ryan Houdek <Houdek.Ryan@fex-emu.org>
>
> This will allow other architectures to support userspace syscall
> dispatch without supporting the syscall common entry.

NAK.

This is in common entry on purpose and won't go anywhere else. The every
arch has it's own broken entry code ordering mess needs to go away and
not proliferated further.

Move ARM to common entry first.

Thanks,

        tglx

  reply	other threads:[~2021-06-02 15:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-29  8:16 [PATCH 0/4] arm64: Implement userspace syscall dispatch houdek.ryan
2021-05-29  8:16 ` [PATCH 1/4] Move userspace syscall dispatch outside of common entry houdek.ryan
2021-06-02 15:41   ` Thomas Gleixner [this message]
2021-06-03 10:58     ` Ryan Houdek
2021-05-29  8:16 ` [PATCH 2/4] arm64: Track the sigreturn landing pad location houdek.ryan
2021-05-29  8:16 ` [PATCH 3/4] arm64: Enable userspace syscall dispatch houdek.ryan
2021-05-29  8:16 ` [PATCH 4/4] arm64: tools: Update syscall user dispatch tests houdek.ryan

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=871r9k1dfi.ffs@nanos.tec.linutronix.de \
    --to=tglx@linutronix.de \
    --cc=houdek.ryan@fex-emu.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@kernel.org \
    --cc=peterz@infradead.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