Received: by 2002:a05:6a10:6744:0:0:0:0 with SMTP id w4csp1367592pxu; Thu, 8 Oct 2020 09:46:09 -0700 (PDT) X-Google-Smtp-Source: ABdhPJycfbnSh5St018dfSaHI1pg/PbMLU3EzqkdTeQnriKBwNE4rhjy0QVUv1wqo+Dzvd3V3c0V X-Received: by 2002:aa7:de82:: with SMTP id j2mr10451743edv.3.1602175568805; Thu, 08 Oct 2020 09:46:08 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1602175568; cv=none; d=google.com; s=arc-20160816; b=FRB50KIVGRFnJ6eB51nj+b5hJKCE/LSXdixSDlHSE1sQVzkBg6cIObci2NbEYCZEaM 5R8EHHL+7etKTtEYbRNHwF4+tdRkYcv1PtrBqxSNNL6zzZi/jmCeJ2SGdO7vl2OIrT+l eSWwvUEakiYqrdjsQYxezXM/2kMq3QMx6F4fcCRMjdo0yx2Qa8ywRfToDQKTn3GMO94r kMRwJmopW87/qHEX0dPzUjqA4k/uubQWp1fV2ghpFH6J8NQCg2v9PJpgnTlPcy3Wc2dK 5+Ng6h465ysOrdTJkwBZTPbufSFLjEbHiL+GjjaeVWkcRKgO0fGxQO4crLbhcXQvjfgD 2uYQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:user-agent:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date :dkim-signature; bh=GRXQSa6ZC+nnaEc4pw80e/cx2CLDkgRRUVhzsvrA1kM=; b=HizHsZXJxg2OfVqVHI9XFekBst6l4+gYlFuw3dfUmzmO+h2RR7rGEfaXugM7Z7ZXCu KgiG0BPqbPpPk3BWfYIeY3haAR48eB28cge5qsMSWzSNVkjbpRo6ioMdwHoWA+cHU2di v/m4Q+sVin/aCTdD1PjfkVRUhhU9XwZCeV1cAjajPijAXOIzR0PfmzUC+qCFHAwgKjbE GSqJ2zcW8YvjNr19GNHGTy+apLokUPdJOnAMDE4egP8ukcp7UYWKms+K7Js2+UFxzWA7 yShHBREhsvBs4QZ4poz5bkmJovTmUI0lwNwYbw/E+T4bNPSoKb5EMG6eInHQab4JcLhk 9IQg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=C+HNpFnj; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id q4si4035182ejr.240.2020.10.08.09.45.45; Thu, 08 Oct 2020 09:46:08 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=C+HNpFnj; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730752AbgJHO4W (ORCPT + 99 others); Thu, 8 Oct 2020 10:56:22 -0400 Received: from us-smtp-delivery-124.mimecast.com ([216.205.24.124]:47792 "EHLO us-smtp-delivery-124.mimecast.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1730721AbgJHO4V (ORCPT ); Thu, 8 Oct 2020 10:56:21 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1602168981; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=GRXQSa6ZC+nnaEc4pw80e/cx2CLDkgRRUVhzsvrA1kM=; b=C+HNpFnjKpn9RL0Lc6wL5hP2fZgjJYvdtkYj7S/9/Ejr6hHbZlocDqP8Wn22TSinn2iCNl qCPawQh2PThskAXxJSIFEnLCvdn/GnDqjnUcfMQjhjKR6nWMzsOG+YsvBLeRj+3SRH9PjY gCXB8UniWeyj0/FthU6QYjsx5v2yKPA= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-161-TTlEaReGNDirHxMkhKntvA-1; Thu, 08 Oct 2020 10:56:16 -0400 X-MC-Unique: TTlEaReGNDirHxMkhKntvA-1 Received: from smtp.corp.redhat.com (int-mx07.intmail.prod.int.phx2.redhat.com [10.5.11.22]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 19C8F10BBEC3; Thu, 8 Oct 2020 14:56:15 +0000 (UTC) Received: from dhcp-27-174.brq.redhat.com (unknown [10.40.192.132]) by smtp.corp.redhat.com (Postfix) with SMTP id B186610013C1; Thu, 8 Oct 2020 14:56:12 +0000 (UTC) Received: by dhcp-27-174.brq.redhat.com (nbSMTP-1.00) for uid 1000 oleg@redhat.com; Thu, 8 Oct 2020 16:56:14 +0200 (CEST) Date: Thu, 8 Oct 2020 16:56:11 +0200 From: Oleg Nesterov To: Jens Axboe Cc: linux-kernel@vger.kernel.org, io-uring@vger.kernel.org, peterz@infradead.org, tglx@linutronix.de Subject: Re: [PATCHSET RFC v3 0/6] Add support for TIF_NOTIFY_SIGNAL Message-ID: <20201008145610.GK9995@redhat.com> References: <20201005150438.6628-1-axboe@kernel.dk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20201005150438.6628-1-axboe@kernel.dk> User-Agent: Mutt/1.5.24 (2015-08-30) X-Scanned-By: MIMEDefang 2.84 on 10.5.11.22 Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 10/05, Jens Axboe wrote: > > Hi, > > The goal is this patch series is to decouple TWA_SIGNAL based task_work > from real signals and signal delivery. I think TIF_NOTIFY_SIGNAL can have more users. Say, we can move try_to_freeze() from get_signal() to tracehook_notify_signal(), kill fake_signal_wake_up(), and remove freezing() from recalc_sigpending(). Probably the same for TIF_PATCH_PENDING, klp_send_signals() can use set_notify_signal() rather than signal_wake_up(). Oleg.