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 X-Spam-Level: X-Spam-Status: No, score=-2.1 required=3.0 tests=DKIM_INVALID,DKIM_SIGNED, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 3949FECE589 for ; Tue, 1 Oct 2019 11:51:18 +0000 (UTC) Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by mail.kernel.org (Postfix) with ESMTP id EDBA821920 for ; Tue, 1 Oct 2019 11:51:17 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=fail reason="signature verification failed" (2048-bit key) header.d=shutemov-name.20150623.gappssmtp.com header.i=@shutemov-name.20150623.gappssmtp.com header.b="AKJTyjYW" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org EDBA821920 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=shutemov.name Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=owner-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix) id 891E18E0005; Tue, 1 Oct 2019 07:51:17 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id 81D1D8E0001; Tue, 1 Oct 2019 07:51:17 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 6E29E8E0005; Tue, 1 Oct 2019 07:51:17 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from forelay.hostedemail.com (smtprelay0024.hostedemail.com [216.40.44.24]) by kanga.kvack.org (Postfix) with ESMTP id 473038E0001 for ; Tue, 1 Oct 2019 07:51:17 -0400 (EDT) Received: from smtpin19.hostedemail.com (10.5.19.251.rfc1918.com [10.5.19.251]) by forelay03.hostedemail.com (Postfix) with SMTP id BE013824CA14 for ; Tue, 1 Oct 2019 11:51:16 +0000 (UTC) X-FDA: 75995050152.19.coat75_6265f77c82544 X-HE-Tag: coat75_6265f77c82544 X-Filterd-Recvd-Size: 5128 Received: from mail-ed1-f65.google.com (mail-ed1-f65.google.com [209.85.208.65]) by imf24.hostedemail.com (Postfix) with ESMTP for ; Tue, 1 Oct 2019 11:51:16 +0000 (UTC) Received: by mail-ed1-f65.google.com with SMTP id r9so11602186edl.10 for ; Tue, 01 Oct 2019 04:51:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=shutemov-name.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:content-transfer-encoding:in-reply-to :user-agent; bh=WwRvxBteqT86BHeeOqI/ZRhly3cYrwnuA1zRjDpe2Bw=; b=AKJTyjYWQ780+va38hELwk915ZrVX8Czx4v0JlPi0ArAKGbq12iiBTtVn8Hs+PWnoq TbbW29cKSRm5TRz+w4UYwHAyU+dQdFpyPtRds27cBqVYl6tJ6rIA22iLwa7JxAqjHYoo fSD9o0w8n4C6dBV3VgVT7bvFGZxJ5FDNqjFRL8gBnrO61363iInKUw8Oi3c8ehTUqflr pAhZsEco5QURGIn+n2yxxNFrsKme9luUOgPC8N+o7u6CbuNQXtWzSOGV5Z9+TgPWxeph 4Ji7DH0zSeBs+sg143ASUjgxS+hMHm+TOFlR/l82xeolHCLFEfOMRLccCPDPe/fW5Q3n UTEQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:content-transfer-encoding :in-reply-to:user-agent; bh=WwRvxBteqT86BHeeOqI/ZRhly3cYrwnuA1zRjDpe2Bw=; b=UOvhrblhj64mCdabIAgV+DzXJ/UiKgTNbd+UdT4oNx9Yk7FGrfUNfsgC554JCawtro 73j1WblV7G3311P0N6gLYKUk2qtG6czMpiRR3jrTdQSobP6WNLqXAs6p7Xzl3DHN14Xd q5NAsp3aswcMhibbPrtn9cO4TF16TMD2zEPOJr6QHUMY6Yqv6V0/N51Qxwqe0b67cB+/ Pvm84WbFXcOFDLct2d01udjkqDozEXCNsX+vm16qmEX73D2gI+4Q20ukjo9GQ4+qQhOZ TQab7vUAUQihNrjQLwmXTb3FkhpFww3EnTvD9z/JoK21CyxlvfnIduPUImgx0PAoK6q/ XROg== X-Gm-Message-State: APjAAAX3/0uLVSdk1x8CNeBtzQLGwoLVlRCO+tVriyWRjiIEy4LmU+GH E7vPfz+7u84Mf/e1+TynLINccw== X-Google-Smtp-Source: APXvYqz+GamY3Ru0CdQT/sU/Q/oDdsj7Hh5ho70H8ToYhwfIqDdI2ZoB+7fverkSDvUFbvgRau2yEA== X-Received: by 2002:a17:907:40bc:: with SMTP id nu20mr23547119ejb.309.1569930674891; Tue, 01 Oct 2019 04:51:14 -0700 (PDT) Received: from box.localdomain ([86.57.175.117]) by smtp.gmail.com with ESMTPSA id z24sm1818728ejr.83.2019.10.01.04.51.14 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 01 Oct 2019 04:51:14 -0700 (PDT) Received: by box.localdomain (Postfix, from userid 1000) id A87D7102FB8; Tue, 1 Oct 2019 14:51:14 +0300 (+03) Date: Tue, 1 Oct 2019 14:51:14 +0300 From: "Kirill A. Shutemov" To: Vlastimil Babka Cc: Qian Cai , Andrew Morton , linux-mm@kvack.org, linux-kernel@vger.kernel.org, kasan-dev@googlegroups.com, "Kirill A. Shutemov" , Matthew Wilcox , Mel Gorman , Michal Hocko , Dmitry Vyukov , Walter Wu , Andrey Ryabinin Subject: Re: [PATCH v2 2/3] mm, page_owner: decouple freeing stack trace from debug_pagealloc Message-ID: <20191001115114.gnala74q3ydreuii@box> References: <731C4866-DF28-4C96-8EEE-5F22359501FE@lca.pw> <218f6fa7-a91e-4630-12ea-52abb6762d55@suse.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <218f6fa7-a91e-4630-12ea-52abb6762d55@suse.cz> User-Agent: NeoMutt/20180716 Content-Transfer-Encoding: quoted-printable 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 Tue, Oct 01, 2019 at 10:07:44AM +0200, Vlastimil Babka wrote: > On 10/1/19 1:49 AM, Qian Cai wrote: > >=20 > >=20 > >> On Sep 30, 2019, at 5:43 PM, Vlastimil Babka wrote: > >> > >> Well, my use case is shipping production kernels with CONFIG_PAGE_OW= NER > >> and CONFIG_DEBUG_PAGEALLOC enabled, and instructing users to boot-ti= me > >> enable only for troubleshooting a crash or memory leak, without a ne= ed > >> to install a debug kernel. Things like static keys and page_ext > >> allocations makes this possible without CPU and memory overhead when= not > >> boot-time enabled. I don't know too much about KASAN internals, but = I > >> assume it's not possible to use it that way on production kernels ye= t? > >=20 > > In that case, why can=E2=80=99t users just simply enable page_owner=3D= on and > > debug_pagealloc=3Don for troubleshooting? The later makes the kernel > > slower, but I am not sure if it is worth optimization by adding a new > > parameter. There have already been quite a few MM-related kernel > > parameters that could tidy up a bit in the future. >=20 > They can do that and it was intention, yes. The extra parameter was > requested by Kirill, so I'll defer the answer to him :) DEBUG_PAGEALLOC is much more intrusive debug option. Not all architecture= s support it in an efficient way. Some require hibernation. I don't see a reason to tie these two option together. --=20 Kirill A. Shutemov