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 2D9A1C433F5 for ; Tue, 26 Apr 2022 18:18:30 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id B5F986B0075; Tue, 26 Apr 2022 14:18:29 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id B0E4A6B007B; Tue, 26 Apr 2022 14:18:29 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 9D6876B007E; Tue, 26 Apr 2022 14:18:29 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (relay.hostedemail.com [64.99.140.26]) by kanga.kvack.org (Postfix) with ESMTP id 907666B0075 for ; Tue, 26 Apr 2022 14:18:29 -0400 (EDT) Received: from smtpin01.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay12.hostedemail.com (Postfix) with ESMTP id 68154120D0D for ; Tue, 26 Apr 2022 18:18:29 +0000 (UTC) X-FDA: 79399840338.01.C81BAE7 Received: from mga11.intel.com (mga11.intel.com [192.55.52.93]) by imf31.hostedemail.com (Postfix) with ESMTP id 9D2EA20059 for ; Tue, 26 Apr 2022 18:18:20 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1650997108; x=1682533108; h=message-id:date:mime-version:subject:to:cc:references: from:in-reply-to:content-transfer-encoding; bh=rDi9xlQfFTSOhAM3G6fIwJqP2shkhn0Ax1Qe/Oy+39A=; b=HCHAa/TnQdanJJqW6lBqPeVPHyihtS1U+/PIBX2IqyE1J0rNPtYkupTS XjyOgX5qdn0N/1yt0lFPNBUrF0h2bu3AJmC5fpdJW0DtyqZ8Nmi+T3I9l eH5lgTNls+jjDA36yDGpELp47mE4SXNM1CQsLM3CuiUMWznFWthsGXPek SkddaPt1XJqaJXn68wqYMDhH/yzhfYEPS9xLp05J1xgx/PvT183vQmPlm aeEOQmGX84cVs9vjyF8VPcKlXnYlOSY/iXrR+zgRIEzs+lXBmw7FC0OOe sMaJkBX8Pga9BSuyQsVdQnZ5S5LP+35u++l3b69sL/aU27s0+aBk2iGD2 w==; X-IronPort-AV: E=McAfee;i="6400,9594,10329"; a="263272507" X-IronPort-AV: E=Sophos;i="5.90,291,1643702400"; d="scan'208";a="263272507" Received: from orsmga008.jf.intel.com ([10.7.209.65]) by fmsmga102.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 26 Apr 2022 11:18:27 -0700 X-IronPort-AV: E=Sophos;i="5.90,291,1643702400"; d="scan'208";a="580075997" Received: from dsocek-mobl2.amr.corp.intel.com (HELO [10.212.69.119]) ([10.212.69.119]) by orsmga008-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 26 Apr 2022 11:18:26 -0700 Message-ID: <8eceffc0-01e8-2a55-6eb9-b26faa9e3caf@intel.com> Date: Tue, 26 Apr 2022 11:21:09 -0700 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.7.0 Subject: Re: [RFC] Expose a memory poison detector ioctl to user space. Content-Language: en-US To: Jue Wang Cc: Naoya Horiguchi , Tony Luck , Dave Hansen , Jiaqi Yan , Greg Thelen , Mina Almasry , linux-mm@kvack.org, Sean Christopherson References: <20220425163451.3818838-1-juew@google.com> From: Dave Hansen In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Authentication-Results: imf31.hostedemail.com; dkim=pass header.d=intel.com header.s=Intel header.b="HCHAa/Tn"; spf=none (imf31.hostedemail.com: domain of dave.hansen@intel.com has no SPF policy when checking 192.55.52.93) smtp.mailfrom=dave.hansen@intel.com; dmarc=pass (policy=none) header.from=intel.com X-Rspam-User: X-Rspamd-Server: rspam05 X-Rspamd-Queue-Id: 9D2EA20059 X-Stat-Signature: gqhdqp8b4swt8s13i6owxy8rjq6zrmqq X-HE-Tag: 1650997100-537355 X-Bogosity: Ham, tests=bogofilter, spamicity=0.000003, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: On 4/26/22 11:02, Jue Wang wrote: >>> Are there any other physical addresses which are RAM but should not have >>> the detector used on them? > In theory, if some physical address range are never / very rarely > accessed, they can be exempted. How would userspace know to exempt them?