From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by smtp.lore.kernel.org (Postfix) with ESMTP id 59458C433FE for ; Fri, 21 Oct 2022 06:17:26 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id B3B5F8E0002; Fri, 21 Oct 2022 02:17:25 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id AC45F8E0001; Fri, 21 Oct 2022 02:17:25 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 93E368E0002; Fri, 21 Oct 2022 02:17:25 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (smtprelay0011.hostedemail.com [216.40.44.11]) by kanga.kvack.org (Postfix) with ESMTP id 849068E0001 for ; Fri, 21 Oct 2022 02:17:25 -0400 (EDT) Received: from smtpin18.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay10.hostedemail.com (Postfix) with ESMTP id 57D8DC0CC5 for ; Fri, 21 Oct 2022 06:17:25 +0000 (UTC) X-FDA: 80043949650.18.19A1A01 Received: from mail-yw1-f173.google.com (mail-yw1-f173.google.com [209.85.128.173]) by imf03.hostedemail.com (Postfix) with ESMTP id 10DC12001C for ; Fri, 21 Oct 2022 06:17:24 +0000 (UTC) Received: by mail-yw1-f173.google.com with SMTP id 00721157ae682-3321c2a8d4cso14674797b3.5 for ; Thu, 20 Oct 2022 23:17:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=zIf8ZNnAW78yhJlmbsbMxnLGL5lK8A9xrLkSuvVZ5vY=; b=SkzcDLX4HCkfZeJ9ffrRFeR1h5/bxkAsdXmLb5xZZmI03lb+SNf+d4CJAr80URmmy0 VR5Di0JZnz+kr3tals3VVIh3jR2iWhSZI/NM5+uOl5cKJIRiARAj20NYRdK/pq2DsehB ftLO6oIhs1qZ+0gh/jwgpJXcIAhFxuKoHcih6iyh8wkmy3epW/EeJamTH/OgoRUKgxzV T6HWPkAnzVQdg206eX9SlmLMsow6Tw234D7CwkIlwxvQVbEcbRtlwmVWYANJOjYAVQKD YCCFizqNNPoPYI1thXrJENlejclBt0Zn8gxFlPWCCBlC3wvG6Gp6FIIYGziDgBDs/3N+ 3MMw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=zIf8ZNnAW78yhJlmbsbMxnLGL5lK8A9xrLkSuvVZ5vY=; b=GsQUl+K1WALFRtzjPYF9gPaJHIw3A9gfH8Ew/o9k4l03sWGOGJA46Gk5yTIxgbMidP 2jBU8Of4QoBdlAQWcZKlLqjdgxuf5bvtqrhE2H9zM3WcwZcb5WWsv4/m7yJdWEAaf+Xo FQH4cb97TPtUUMcNLzAnnB9l4UdYY8Sd5uCoH7MupYCJie5/nI6NtFJzLpMGPIxTiLfI nOCF3Y0srbW80XqN0UAwssVniS4mIv9zgMfiu0Eo0/0Dportc3qE3h+V/5zRdWQxjgUM wHS4z/WVAcML/5zulmVaMGfgcGJfXfwNj/x/sZX1qtEugLgbkj8K0awPlNOB56RdvInG SL0w== X-Gm-Message-State: ACrzQf0SvRqF1xmuniTe9XoeXLerAzh3VqpAs5IY0M2ZyKNoPodawPfm X3C13vBO98hwAylqOqespJWXPc4C99xMhT1DwE77KA== X-Google-Smtp-Source: AMsMyM7wJTOUnM+n70HWlfhBUHKFGcN4iKPxR8GF36jf5eJRQLjoB9h8ZtenONZtSS8A8XeX5r7Z9kot0IMW+IJOSFQ= X-Received: by 2002:a81:1c07:0:b0:358:6e7d:5118 with SMTP id c7-20020a811c07000000b003586e7d5118mr16062156ywc.255.1666333044032; Thu, 20 Oct 2022 23:17:24 -0700 (PDT) MIME-Version: 1.0 References: <20220915150417.722975-19-glider@google.com> <20221019173620.10167-1-youling257@gmail.com> In-Reply-To: From: Marco Elver Date: Thu, 20 Oct 2022 23:16:47 -0700 Message-ID: Subject: Re: [PATCH v7 18/43] instrumented.h: add KMSAN support To: youling 257 Cc: Alexander Potapenko , Alexander Viro , Alexei Starovoitov , Andrew Morton , Andrey Konovalov , Andy Lutomirski , Arnd Bergmann , Borislav Petkov , Christoph Hellwig , Christoph Lameter , David Rientjes , Dmitry Vyukov , Eric Biggers , Eric Dumazet , Greg Kroah-Hartman , Herbert Xu , Ilya Leoshkevich , Ingo Molnar , Jens Axboe , Joonsoo Kim , Kees Cook , Mark Rutland , Matthew Wilcox , "Michael S. Tsirkin" , Pekka Enberg , Peter Zijlstra , Petr Mladek , Stephen Rothwell , Steven Rostedt , Thomas Gleixner , Vasily Gorbik , Vegard Nossum , Vlastimil Babka , kasan-dev@googlegroups.com, linux-mm@kvack.org, linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org Content-Type: text/plain; charset="UTF-8" ARC-Authentication-Results: i=1; imf03.hostedemail.com; dkim=pass header.d=google.com header.s=20210112 header.b=SkzcDLX4; dmarc=pass (policy=reject) header.from=google.com; spf=pass (imf03.hostedemail.com: domain of elver@google.com designates 209.85.128.173 as permitted sender) smtp.mailfrom=elver@google.com ARC-Seal: i=1; s=arc-20220608; d=hostedemail.com; t=1666333045; a=rsa-sha256; cv=none; b=5aIdZ/KUrrgpCTaBl5VNQLU/h2XcHz//4qrt1Vaz/o88RNbWILVKHr3K1itnk1xpWxBYcp eBn3k1sttIII3OtRbAqAXhr4vbwOcerzvWmZo1pTAaPFh0qsIQ4WxRfeSjEOvV2crIPuu0 53879KabrKnmadI0ND82X4PPETxcmoM= ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=hostedemail.com; s=arc-20220608; t=1666333045; h=from:from:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type:content-transfer-encoding: in-reply-to:in-reply-to:references:references:dkim-signature; bh=zIf8ZNnAW78yhJlmbsbMxnLGL5lK8A9xrLkSuvVZ5vY=; b=WHpNyi7BwxcpoxYjLOa5Q2lAiy2s5uBD1W75Vh/3+YwEXAL8+wM0OWhlWIVjmvtwuO9Z/k +RFAENQqT8pr1j7mJnjL/OTn8JgrXIMMLX53zcmvwGViEXekyQGTLr3Im4i5AwqhTtXsSm mtFKjhtv2EQIjUMYY2uUVtq08EQH6ko= Authentication-Results: imf03.hostedemail.com; dkim=pass header.d=google.com header.s=20210112 header.b=SkzcDLX4; dmarc=pass (policy=reject) header.from=google.com; spf=pass (imf03.hostedemail.com: domain of elver@google.com designates 209.85.128.173 as permitted sender) smtp.mailfrom=elver@google.com X-Rspam-User: X-Rspamd-Server: rspam06 X-Stat-Signature: aauq3z4kzq3dpk74xmmoiuojb45fopae X-Rspamd-Queue-Id: 10DC12001C X-HE-Tag: 1666333044-192116 X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: On Thu, 20 Oct 2022 at 22:55, youling 257 wrote: > > How to use perf tool? The simplest would be to try just "perf top" - and see which kernel functions consume most CPU cycles. I would suggest you compare both kernels, and see if you can spot a function which uses more cycles% in the problematic kernel.