From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@kernel.org>
X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on
	aws-us-west-2-korg-lkml-1.web.codeaurora.org
Received: from vger.kernel.org (vger.kernel.org [23.128.96.18])
	by smtp.lore.kernel.org (Postfix) with ESMTP id 9ABEDC433EF
	for <linux-kernel@archiver.kernel.org>; Wed, 12 Jan 2022 16:00:57 +0000 (UTC)
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1354894AbiALQA4 (ORCPT
        <rfc822;linux-kernel@archiver.kernel.org>);
        Wed, 12 Jan 2022 11:00:56 -0500
Received: from albireo.enyo.de ([37.24.231.21]:57542 "EHLO albireo.enyo.de"
        rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
        id S243611AbiALQAz (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
        Wed, 12 Jan 2022 11:00:55 -0500
Received: from [172.17.203.2] (port=50701 helo=deneb.enyo.de)
        by albireo.enyo.de ([172.17.140.2]) with esmtps (TLS1.3:ECDHE_SECP256R1__RSA_PSS_RSAE_SHA256__AES_256_GCM:256)
        id 1n7g3N-00G4bR-CE; Wed, 12 Jan 2022 16:00:49 +0000
Received: from fw by deneb.enyo.de with local (Exim 4.94.2)
        (envelope-from <fw@deneb.enyo.de>)
        id 1n7g3N-003Vt2-1y; Wed, 12 Jan 2022 17:00:49 +0100
From:   Florian Weimer <fw@deneb.enyo.de>
To:     Peter Zijlstra <peterz@infradead.org>
Cc:     Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
        linux-kernel <linux-kernel@vger.kernel.org>,
        Thomas Gleixner <tglx@linutronix.de>,
        paulmck <paulmck@kernel.org>, Boqun Feng <boqun.feng@gmail.com>,
        "H. Peter Anvin" <hpa@zytor.com>, Paul Turner <pjt@google.com>,
        linux-api <linux-api@vger.kernel.org>,
        Christian Brauner <christian.brauner@ubuntu.com>,
        carlos <carlos@redhat.com>
Subject: Re: [RFC PATCH] rseq: x86: implement abort-at-ip extension
References: <20220107170302.8325-1-mathieu.desnoyers@efficios.com>
        <87a6g7ny0j.fsf@mid.deneb.enyo.de>
        <1968088162.13310.1641584935813.JavaMail.zimbra@efficios.com>
        <87y23l6l2j.fsf@mid.deneb.enyo.de>
        <Yd71+Da44h9Ge0+s@hirez.programming.kicks-ass.net>
Date:   Wed, 12 Jan 2022 17:00:49 +0100
In-Reply-To: <Yd71+Da44h9Ge0+s@hirez.programming.kicks-ass.net> (Peter
        Zijlstra's message of "Wed, 12 Jan 2022 16:38:32 +0100")
Message-ID: <87sftt6j0u.fsf@mid.deneb.enyo.de>
MIME-Version: 1.0
Content-Type: text/plain
Precedence: bulk
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

* Peter Zijlstra:

> On Wed, Jan 12, 2022 at 04:16:36PM +0100, Florian Weimer wrote:
>
>> You could perhaps push a signal frame onto the stack.  It's going to
>> be expensive, but it's already in the context switch path, so maybe it
>> does not matter.
>
> Please no! Signals are a trainwreck that need change (see the whole
> AVX-512 / AMX saga), we shouldn't use more of that just cause.

If it's a signal, it should be modeled as such.  I think it's pretty
close to a synchronous signal.