Received: by 2002:a05:6a10:8c0a:0:0:0:0 with SMTP id go10csp1078399pxb; Thu, 4 Mar 2021 02:40:55 -0800 (PST) X-Google-Smtp-Source: ABdhPJxA1I2bypgB9h+i1Sz42vIXm/IfIyo4+4Xv83FWpAUmmbY3I0kpc7JdBlaqX2zLgkpo0nQl X-Received: by 2002:a05:6402:17d5:: with SMTP id s21mr3569053edy.65.1614854455683; Thu, 04 Mar 2021 02:40:55 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1614854455; cv=none; d=google.com; s=arc-20160816; b=H+QOlXbHlGzkZ7fPucITj2ruaXQZVgdBW1+lLw4N8W4XpqIebCAwbgHD0lSQbPykXo JFKdb2k3zX6QLVwUbm0FmfdlEBM+qPZJS0MKGezPDII3+rOft0+OvBzU+/w9OUpSYOd1 yqvieo9q5PeHALIhTAAWaItkYoj7F0B3ejBX6yJtxwsDynPfv+l1AbUgY04e8bC5hsjW 2nd3Q5m1wc/k/1nAB7mrSFD8Nz0P6i+NdL/fKuNFnl3jRSlB3jwaDfi4F0JcpcLEyJH/ UYSgKisybwOpGFvqV67po7y4Je6ktgAsPzjLBC6v6KwUwZcn81wBnsjccrmSbzugz3bu NqcQ== 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=PJFVk9Prwjkxdm586ACwDtBMKBVeZRi7IzKPe/DvaFI=; b=nGAtCqhsZ+W9566+GZhcekSGsJK1yG8uidOnha+nU7iumSXUnscaeiaLaeWvZJU80h 9FFHebuNta+2eG4ndAZR4HzSfwL8q5QDJg99Ka5iQHyr3uqPPOoJvL0Tiec1eFWCaKO6 3/xi5Fa9SDRf1beSodj9MxhCIxHkw2LGbDB2BTB9wRuuE8aS1sciSByMI5r3jtPM3XRY rd/gQiZH5cdNGX/z6/CAGCS6ttyPiHs5Esxepo5DAI7LHd6CYUiLkOlil3GmCga4px3i VF4YkDJ1ksEhgteRcEnk2BIOn9o1PWtM8+8Dz15oZVO+xs5gkMSFxDelCmRHBwIhHC2L pwOg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=hErmplPY; 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 d21si3907593edu.262.2021.03.04.02.40.33; Thu, 04 Mar 2021 02:40:55 -0800 (PST) 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=hErmplPY; 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 S1345282AbhCCRRW (ORCPT + 99 others); Wed, 3 Mar 2021 12:17:22 -0500 Received: from us-smtp-delivery-124.mimecast.com ([63.128.21.124]:48086 "EHLO us-smtp-delivery-124.mimecast.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1380751AbhCCN3g (ORCPT ); Wed, 3 Mar 2021 08:29:36 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1614778080; 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=PJFVk9Prwjkxdm586ACwDtBMKBVeZRi7IzKPe/DvaFI=; b=hErmplPYcuy9JYr5U0+O+j+nsfeI2pSwip1oPv/fxbbFtYEvVx5V34nCqc1FB4+ulF5XlT W7PWfZyohYcMDiU6Ee7TiJBtY7ZJABsj2vhWu5WQVjrCyusU2W0Us1V69ESKfkqzAioFbs 5ylvXPmpTvsIx61ZkPx+q1Yike357Vk= 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-298-YJ8FY7OuMBiHiY1HqX1Adg-1; Wed, 03 Mar 2021 08:27:56 -0500 X-MC-Unique: YJ8FY7OuMBiHiY1HqX1Adg-1 Received: from smtp.corp.redhat.com (int-mx03.intmail.prod.int.phx2.redhat.com [10.5.11.13]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 795176D4E0; Wed, 3 Mar 2021 13:27:54 +0000 (UTC) Received: from dhcp-27-174.brq.redhat.com (unknown [10.40.194.81]) by smtp.corp.redhat.com (Postfix) with SMTP id 614936F999; Wed, 3 Mar 2021 13:27:51 +0000 (UTC) Received: by dhcp-27-174.brq.redhat.com (nbSMTP-1.00) for uid 1000 oleg@redhat.com; Wed, 3 Mar 2021 14:27:54 +0100 (CET) Date: Wed, 3 Mar 2021 14:27:50 +0100 From: Oleg Nesterov To: Alexei Starovoitov Cc: Andy Lutomirski , Andy Lutomirski , bpf , Masami Hiramatsu , Peter Zijlstra , LKML , Anil S Keshavamurthy , "David S. Miller" , X86 ML , Andrew Cooper Subject: Re: Why do kprobes and uprobes singlestep? Message-ID: <20210303132749.GA28955@redhat.com> References: <968E85AE-75B8-42D7-844A-0D61B32063B3@amacapital.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) X-Scanned-By: MIMEDefang 2.79 on 10.5.11.13 Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 03/02, Alexei Starovoitov wrote: > > Especially if such tightening will come with performance boost for > uprobe on a nop and unprobe at the start (which is typically push or > alu on %sp). > That would be a great step forward. Just in case, nop and push are emulated without additional overhead. Oleg.