Message ID | 20221122225213.2317-1-beaub@linux.microsoft.com |
---|---|
Headers |
Return-Path: <linux-kernel-owner@vger.kernel.org> Delivered-To: ouuuleilei@gmail.com Received: by 2002:adf:f944:0:0:0:0:0 with SMTP id q4csp2477333wrr; Tue, 22 Nov 2022 14:52:41 -0800 (PST) X-Google-Smtp-Source: AA0mqf6Qglm9n1yMCuDwgwZ8RL3yXMdlE9/acFXzCbRiMcQSgbmrEDfdf/ti6qXqoYOtwsEN8Bhy X-Received: by 2002:a17:903:486:b0:186:95ca:1e4c with SMTP id jj6-20020a170903048600b0018695ca1e4cmr6511452plb.13.1669157561254; Tue, 22 Nov 2022 14:52:41 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1669157561; cv=none; d=google.com; s=arc-20160816; b=hbsaaNQ/C0GipKRozlknu3WOetq98viFHO3EsP5Nj3W2sSvnF+7b+jigGYk5G7pkwo K+mPPbD/BBUPqqCtafjjaulTrszcovtryuX/HuilkGHFSaRxRrhdIIBFyiHKVD9fw1n5 GErTQyvpxHdqNYMxiDCYYSv4WMOXy8rGsCd+GOJIR0mCcxgNzB1YbEdqM+XL8o5Z2Vet AbAYqQ1rSTqbxP6/CFeuzXncuR2LPRTRnuHMq5weiXBEyrRafuivzqudL891hltfQwDY 98VoueDjPz1m4aBLYo920TXWlh+OjZxPN6VEsrPsZRziAVIkoxEOGmwVruewePiPVL5p 4jMA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :message-id:date:subject:cc:to:from:dkim-signature:dkim-filter; bh=liwCqPeGdIDPCm09lX9xxuZsfBCSzG819nFGAO73BpE=; b=sgum6yjn7HZRXOfg8zUinUeJBFR/ZQI0Qd5uMg85SI1VEN+ck6xUe0OwwMyeMx3oQY F8SpDd331FYQq17cWiQTfGQLdUtn5JAAgxnXAMqykrwJS+HvPmAxKnRf9jC5LwGuxDiU Ip6jtpn9aCj4K1TcfR7IpXwZOmaaUdRxA738Z7I7mSOJww870yVKz6Zn/Xen82873E7S VadHoX0ro+ga0kbWFpTtCIjWJjG+uRWznAH+dAuOhXF7bbj6Dako3Q/5FFqnRCVRUz2o 0nvb1kyCZTCovCEN+jvboAQMW8wmCzM3ZSwnwFUY6hG1h5o6N+BW31zo7vXTSfJcuaC/ YzsQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linux.microsoft.com header.s=default header.b=pEdTa9cY; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linux.microsoft.com Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id o4-20020a170902d4c400b00179e66b5d2csi16329886plg.398.2022.11.22.14.52.28; Tue, 22 Nov 2022 14:52:41 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@linux.microsoft.com header.s=default header.b=pEdTa9cY; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linux.microsoft.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S235037AbiKVWwU (ORCPT <rfc822;cjcooper78@gmail.com> + 99 others); Tue, 22 Nov 2022 17:52:20 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:51526 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S234753AbiKVWwS (ORCPT <rfc822;linux-kernel@vger.kernel.org>); Tue, 22 Nov 2022 17:52:18 -0500 Received: from linux.microsoft.com (linux.microsoft.com [13.77.154.182]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id CCCC76BDEC; Tue, 22 Nov 2022 14:52:17 -0800 (PST) Received: from W11-BEAU-MD.localdomain (unknown [76.135.50.127]) by linux.microsoft.com (Postfix) with ESMTPSA id 257D520B717A; Tue, 22 Nov 2022 14:52:17 -0800 (PST) DKIM-Filter: OpenDKIM Filter v2.11.0 linux.microsoft.com 257D520B717A DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linux.microsoft.com; s=default; t=1669157537; bh=liwCqPeGdIDPCm09lX9xxuZsfBCSzG819nFGAO73BpE=; h=From:To:Cc:Subject:Date:From; b=pEdTa9cYCVteUWgMmpFt7oiFOdiy00O68MIHvbevu3TuSKSOHpaaO720ThfQPT2q/ O9uuomlwWVc0R2VZJ292myb405sk+QbQMqyArYevPWwl/Z9weJJuas5jEp7eb+hL7A wrmmih8Jg8wyMS038pYxtOQnEjIIjnEiboXNo49Y= From: Beau Belgrave <beaub@linux.microsoft.com> To: rostedt@goodmis.org, mhiramat@kernel.org, mathieu.desnoyers@efficios.com, dcook@linux.microsoft.com, alanau@linux.microsoft.com, brauner@kernel.org, akpm@linux-foundation.org Cc: linux-trace-devel@vger.kernel.org, linux-kernel@vger.kernel.org Subject: [PATCH v3 0/9] tracing/user_events: Remote write ABI Date: Tue, 22 Nov 2022 14:52:04 -0800 Message-Id: <20221122225213.2317-1-beaub@linux.microsoft.com> X-Mailer: git-send-email 2.25.1 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-19.8 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,ENV_AND_HDR_SPF_MATCH,RCVD_IN_DNSWL_MED, SPF_HELO_PASS,SPF_PASS,USER_IN_DEF_DKIM_WL,USER_IN_DEF_SPF_WL autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: <linux-kernel.vger.kernel.org> X-Mailing-List: linux-kernel@vger.kernel.org X-getmail-retrieved-from-mailbox: =?utf-8?q?INBOX?= X-GMAIL-THRID: =?utf-8?q?1750238558563128633?= X-GMAIL-MSGID: =?utf-8?q?1750238558563128633?= |
Series |
tracing/user_events: Remote write ABI
|
|
Message
Beau Belgrave
Nov. 22, 2022, 10:52 p.m. UTC
As part of the discussions for user_events aligned with user space tracers, it was determined that user programs should register a aligned value to set or clear a bit when an event becomes enabled. Currently a shared page is being used that requires mmap(). Remove the shared page implementation and move to a user registered address implementation. In this new model during the event registration from user programs 3 new values are specified. The first is the address to update when the event is either enabled or disabled. The second is the bit to set/clear to reflect the event being enabled. The third is the size of the value at the specified address. This allows for a local 32/64-bit value in user programs to support both kernel and user tracers. As an example, setting bit 31 for kernel tracers when the event becomes enabled allows for user tracers to use the other bits for ref counts or other flags. The kernel side updates the bit atomically, user programs need to also update these values atomically. User provided addresses must be aligned on a natural boundary, this allows for single page checking and prevents odd behaviors such as a enable value straddling 2 pages instead of a single page. Currently page faults are only logged, future patches will handle these. When page faults are encountered they are done asyncly via a workqueue. If the page faults back in, the write update is attempted again. If the page cannot fault-in, then we log and wait until the next time the event is enabled/disabled. This is to prevent possible infinite loops resulting from bad user processes unmapping or changing protection values after registering the address. Change history V3: Rebase to 6.1-rc6. Removed RFC tag on series. Updated documentation to reflect ABI changes. Added self-test for ABI specific clone/fork cases. Moved user_event_mm removal into do_exit() to ensure RSS task accounting is done properly in async fault paths. Also lets us remove the delayed mmdrop(), saving memory in each user_event_mm struct. Fixed timing window where task exits, but write could be in-progress. During exit we now take mmap_write_lock to ensure we drain writes. V2: Rebase to 6.1-rc5. Added various comments based on feedback. Added enable_size to register struct, allows 32/64 bit addresses as long as the enable_bit fits and the address is naturally aligned. Changed user_event_enabler_write to accept a new flag indicating if a fault fixup should be done or not. This allows user_event_enabler_create to return back failures to the user ioctl reg call and retry to fault in data. Added tracking fork/exec/exit of tasks to have the user_event_mm lifetime tied more to the task than the file. This came with extra requirements around when you can lock, such as softirq cases, as well as a RCU pattern to ensure fork/exec/exit take minimal lock times. Changed enablers to use a single word-aligned value for saving the bit to set and any flags, such as faulting asyncly or being freed. This was required to ensure atomic bit set/test for fork cases where taking the event_mutex is not a good scalability decision. Added unregister IOCTL, since file lifetime no longer limits the enable time for any events (the mm does). Updated sample code to reflect the new remote write based ABI. Updated self-test code to reflect the new remote write based ABI. Beau Belgrave (9): tracing/user_events: Split header into uapi and kernel tracing/user_events: Track fork/exec/exit for mm lifetime tracing/user_events: Use remote writes for event enablement tracing/user_events: Fixup enable faults asyncly tracing/user_events: Add ioctl for disabling addresses tracing/user_events: Update self-tests to write ABI tracing/user_events: Add ABI self-test tracing/user_events: Use write ABI in example tracing/user_events: Update documentation for ABI Documentation/trace/user_events.rst | 172 ++-- fs/exec.c | 2 + include/linux/sched.h | 5 + include/linux/user_events.h | 99 ++- include/uapi/linux/user_events.h | 81 ++ kernel/exit.c | 2 + kernel/fork.c | 3 + kernel/trace/Kconfig | 5 +- kernel/trace/trace_events_user.c | 776 ++++++++++++++---- samples/user_events/example.c | 47 +- tools/testing/selftests/user_events/Makefile | 2 +- .../testing/selftests/user_events/abi_test.c | 228 +++++ .../testing/selftests/user_events/dyn_test.c | 2 +- .../selftests/user_events/ftrace_test.c | 162 ++-- .../testing/selftests/user_events/perf_test.c | 39 +- 15 files changed, 1233 insertions(+), 392 deletions(-) create mode 100644 include/uapi/linux/user_events.h create mode 100644 tools/testing/selftests/user_events/abi_test.c base-commit: eb7081409f94a9a8608593d0fb63a1aa3d6f95d8