Received: by 2002:a25:8b91:0:0:0:0:0 with SMTP id j17csp4196099ybl; Mon, 3 Feb 2020 14:29:39 -0800 (PST) X-Google-Smtp-Source: APXvYqzna0/j7O/cXAbuSdEcaR7nsbpJkI/OE0E829oRtngLKTTc3po+nwjEjzn5KCL8W6jgt5JJ X-Received: by 2002:aca:db41:: with SMTP id s62mr905491oig.87.1580768978897; Mon, 03 Feb 2020 14:29:38 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1580768978; cv=none; d=google.com; s=arc-20160816; b=Xz+uMyM3Mgy9R+ulKBohaBdOcg/71ZkEEidbokJ5EnnnKjn+vstmJidzNPTKcjQP0x spOXvpzOasmo/SXMxwVDqKqg4UuxK8ocO1ZdKvPM7zSQbicR+/Abg2p11wzPxggeZ1/S Vq/MX4fyxj1v3sjPMnrT3m+zZd18APLz56mZGsoI7zUl+EmvnYdFDCL1troa0cQ9YZPd k5Vdq4h/ZJlS0Jb4oKO9Al0FKCEdHOorUE7qpSFUzLvDSdpSS+9RXtGcYnWl/FAfhooC hD2zWHqcXtVG1qkPWo7HQk32oYp7800XuGO52hYDA21CebakY1w6R8VCVrioQ4V6xy6z xfyA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:references:in-reply-to:message-id:date :subject:cc:to:from:dkim-signature; bh=Yr95hrNi5JfgkOfoS1PjLAI5Z/W4hgT7UGFvqBbgOxM=; b=tmyb/Qq8jWp6hz7UAXzf4wTENJY5KXK9f7axEJZ6TqktVtxY0jkD3nCuGIWwbxIidg GgEHKKeMS2f08zOkZ1AeKnr+otH3o55MHGG78z9pFrgLMmDlJ00oj4hvzwV5zhP4QZmd UIrm4JJpUamV4xls8KB3r0PM96Cy4z+sydh0Vd8IEJt18wfOIaGHCrms33ihH8+CjOhU 5ULQxqvdKi1AUoa7lBhjBYjlCjCfNAOw4YDSui+Muo2LxRL0wu8lcXUB2v061U9kzAK8 5NTILt6A18EpuHUL8gu5Sbqtp5wWBHb1O2FXzgqIhnRRMNjgLlL+3GWGGjl8BbvJrCXn SWBw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=KnUBd3aC; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 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. [209.132.180.67]) by mx.google.com with ESMTP id j2si9709112otr.255.2020.02.03.14.29.26; Mon, 03 Feb 2020 14:29:38 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=KnUBd3aC; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 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 S1727166AbgBCW0o (ORCPT + 99 others); Mon, 3 Feb 2020 17:26:44 -0500 Received: from us-smtp-2.mimecast.com ([205.139.110.61]:37692 "EHLO us-smtp-delivery-1.mimecast.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1726369AbgBCW0o (ORCPT ); Mon, 3 Feb 2020 17:26:44 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1580768803; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:in-reply-to:in-reply-to:references:references; bh=Yr95hrNi5JfgkOfoS1PjLAI5Z/W4hgT7UGFvqBbgOxM=; b=KnUBd3aCR/tZuJdEITrkOHznPTqA4xfxWfo16IftF+la0cWZZU1Xb5WPC1haR5VboANGsh X+iJ2YFrYl+YR/VN37Z7I0KW8Rc6brm93bRtsrKm7Y8fJDOo5EcrGnl7jXT8Q9f1FWUNZX SSWuryi7XaRxoUzO1dGcbSuOMfjtins= Received: from mail-pg1-f197.google.com (mail-pg1-f197.google.com [209.85.215.197]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-78-9LEhusYPMvS5slWbjfBQjA-1; Mon, 03 Feb 2020 17:26:40 -0500 X-MC-Unique: 9LEhusYPMvS5slWbjfBQjA-1 Received: by mail-pg1-f197.google.com with SMTP id n7so5116351pgt.7 for ; Mon, 03 Feb 2020 14:26:40 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id:in-reply-to :references; bh=Yr95hrNi5JfgkOfoS1PjLAI5Z/W4hgT7UGFvqBbgOxM=; b=O6BB0sqPUjNFDWfXYq39Pj8NMeYOVUPWD0ehuRAWc86Twgd3N9VPzHrU8YVl8m3XX3 KmCf7KbcFL+Cd+m7wsRqrY9DJj5imn1EnLIFLKNQ8zeB8+GzciDAiffpYqA+pORxrYld Y60/4prWaukx9di9GwcugLTrO7qc8VaalAInJDZfQ1yViJd3dPYlxXAKDRZhlRVhQs/8 wEK4FUFUqdfDaP13BdrdP3/RLlMRY377m66ScLvFGHSPmFftkGwqI2EpkzJmlhn5nmLb NCer3XPmEP+d8OXNgwZDSRJjKH+seATGexHBF7aaVzu6wxTUkhldUOHnb94/ubCMWfCB 20qw== X-Gm-Message-State: APjAAAVGQRIwFm5ldBRYlEmzWUgDhHrr2zEhWJjiAbAm7jhD/JVNQpkl Ljw2jTmLSpYPjkVp5qTKCXaLLKszrJqMcxl2LAfDYw1JCXgBfhQ4QANrtR61LIdiWO7pP2Ye9o1 0HOOv+JhqizNn11A/EpEM4fDW X-Received: by 2002:a63:d406:: with SMTP id a6mr28302965pgh.264.1580768799553; Mon, 03 Feb 2020 14:26:39 -0800 (PST) X-Received: by 2002:a63:d406:: with SMTP id a6mr28302937pgh.264.1580768799210; Mon, 03 Feb 2020 14:26:39 -0800 (PST) Received: from localhost ([122.177.227.116]) by smtp.gmail.com with ESMTPSA id v9sm466061pja.26.2020.02.03.14.26.38 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 03 Feb 2020 14:26:38 -0800 (PST) From: Bhupesh Sharma To: linux-arm-kernel@lists.infradead.org Cc: linux-kernel@vger.kernel.org, bhsharma@redhat.com, bhupesh.linux@gmail.com, Mark Rutland , Will Deacon , Catalin Marinas , Ard Biesheuvel Subject: [PATCH 2/2] perf/arm64: Allow per-task kernel breakpoints Date: Tue, 4 Feb 2020 03:56:24 +0530 Message-Id: <1580768784-25868-3-git-send-email-bhsharma@redhat.com> X-Mailer: git-send-email 2.7.4 In-Reply-To: <1580768784-25868-1-git-send-email-bhsharma@redhat.com> References: <1580768784-25868-1-git-send-email-bhsharma@redhat.com> Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org commit 478fcb2cdb23 ("arm64: Debugging support") disallowed per-task kernel breakpoints on arm64 since these would have potentially complicated the stepping code. However, we now have several use-cases (for e.g. perf) which require per-task address execution h/w breakpoint to be exercised/set on arm64: For e.g. we can set address execution h/w breakpoints, using the format prescribed by 'perf-list' command: mem:[/len][:access] [Hardware breakpoint] Without this patch, currently 'perf stat -e' reports that per-task address execution h/w breakpoints are 'not supported' on arm64. See below: $ TEST_FUNC="vfs_read" $ ADDR=0x`cat /proc/kallsyms | grep -P "\\s$TEST_FUNC\$" | cut -f1 -d' '` $ perf stat -e mem:$ADDR:x -x';' -- cat /proc/cpuinfo > /dev/null ;;mem:0xffff00001031dd68:x;0;100.00;; After this patch, this use-case can be supported: $ TEST_FUNC="vfs_read" $ ADDR=0x`cat /proc/kallsyms | grep -P "\\s$TEST_FUNC\$" | cut -f1 -d' '` $ perf stat -e mem:$ADDR:x -x';' -- cat /proc/cpuinfo > /dev/null 5;;mem:0xfffffe0010361d20:x;912200;100.00;; Cc: Mark Rutland Cc: Will Deacon Cc: Catalin Marinas Cc: Ard Biesheuvel Signed-off-by: Bhupesh Sharma --- arch/arm64/kernel/hw_breakpoint.c | 7 ------- 1 file changed, 7 deletions(-) diff --git a/arch/arm64/kernel/hw_breakpoint.c b/arch/arm64/kernel/hw_breakpoint.c index 0b727edf4104..c28f04e02845 100644 --- a/arch/arm64/kernel/hw_breakpoint.c +++ b/arch/arm64/kernel/hw_breakpoint.c @@ -562,13 +562,6 @@ int hw_breakpoint_arch_parse(struct perf_event *bp, hw->address &= ~alignment_mask; hw->ctrl.len <<= offset; - /* - * Disallow per-task kernel breakpoints since these would - * complicate the stepping code. - */ - if (hw->ctrl.privilege == AARCH64_BREAKPOINT_EL1 && bp->hw.target) - return -EINVAL; - return 0; } -- 2.7.4