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 3882DC433FE for ; Thu, 10 Nov 2022 20:23:23 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id A4A416B0071; Thu, 10 Nov 2022 15:23:22 -0500 (EST) Received: by kanga.kvack.org (Postfix, from userid 40) id 9FA496B0072; Thu, 10 Nov 2022 15:23:22 -0500 (EST) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 8C1B96B0074; Thu, 10 Nov 2022 15:23:22 -0500 (EST) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (smtprelay0010.hostedemail.com [216.40.44.10]) by kanga.kvack.org (Postfix) with ESMTP id 7D5F56B0071 for ; Thu, 10 Nov 2022 15:23:22 -0500 (EST) Received: from smtpin01.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay03.hostedemail.com (Postfix) with ESMTP id 3268FA0A78 for ; Thu, 10 Nov 2022 20:23:22 +0000 (UTC) X-FDA: 80118657444.01.67EC5C9 Received: from mail-pg1-f182.google.com (mail-pg1-f182.google.com [209.85.215.182]) by imf26.hostedemail.com (Postfix) with ESMTP id B1AF114000A for ; Thu, 10 Nov 2022 20:23:20 +0000 (UTC) Received: by mail-pg1-f182.google.com with SMTP id s196so2671249pgs.3 for ; Thu, 10 Nov 2022 12:23:20 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20210112; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=4AYdwauMWFqqDYXBV3jcMDZz3wipJiEn+s4Qc8tHNhA=; b=FJwNt96obfbP+KNb2NpoZhay1sn9U5WjCRC4BE4JkNgt82SwFysTgEB5bpFYjRQoN0 nAZx4/lxxRMR7/w4Ek07hgM6T0/H0p7T3Vniy64wYpUd4IrFgu/1eVlDd+aIXVy888Dm iu2Mkj4v6VApZUPCV+CA+The4XApG3x4mAzrSDDGRtvWVsY+C13u3K0xEr9YslJg8C+7 SjfNk7KLz4/SI4fEkq8TtV3qZUh1PM6BPtOuOOKM+a1yfdlCDI0MSt5/rIKU+K7HNoWx LlWVpoImBpLB3u3XUW3KNNl3zdrDe3mWGRq8v+Pzm5JvyLcZcgKwld/s8BKCijWyrdRf tZTQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding: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=4AYdwauMWFqqDYXBV3jcMDZz3wipJiEn+s4Qc8tHNhA=; b=Ptg5nb5DI/yCQik0Z4ACkwqJqlmXWD8gmADqzjJnCUS2de22dO66auj8sWDx5+RYST wN4bYASSAnlIYsIMLAJgRQ+jEujXv6j7dU8nsz5JhM2w8mCsH5BWcmth+EReMoPVaAtp EqvQTXpfwspohoAmwtdT/39z4aVTTKyzyFqx0+EWTN4eulTK58D4E30mDQxQbRgxyklA 3ap6Uy7XaMRj9JPkO6+/7ngx52NSPEogkHfn77NCUM/nH93/PSjMb5dbIT5iTyPiQyMG LGv1COYZC+j2pKqxfgRIXYmB8LlIgxarwxQGBC8A78xlkYUNQbl5rkHw0RifNk/alDFD cTfA== X-Gm-Message-State: ACrzQf2IHTiyQugOMEFkeE+db5gyKl3wJAMxqLUVOTXhnlPybDiAbJ8L Bvr/CABznlrHXEE8McfGbLq/UV0OvOQ+857VY7+S8g== X-Google-Smtp-Source: AMsMyM5yoLlQ+Fk+GWswX3/G4W7KF4GSSHXGW8Ogz1p4cZMFb97xvcQgNaOawg0uUiNW6Fa6idY4jqdUc92D/hMJadE= X-Received: by 2002:a63:689:0:b0:434:bb42:b07d with SMTP id 131-20020a630689000000b00434bb42b07dmr3164410pgg.496.1668111799420; Thu, 10 Nov 2022 12:23:19 -0800 (PST) MIME-Version: 1.0 References: <20221103155029.2451105-1-jiaqiyan@google.com> <7E670362-C29E-4626-B546-26530D54F937@gmail.com> <20221109050425.GA527418@hori.linux.bs1.fc.nec.co.jp> In-Reply-To: <20221109050425.GA527418@hori.linux.bs1.fc.nec.co.jp> From: Jiaqi Yan Date: Thu, 10 Nov 2022 12:23:08 -0800 Message-ID: Subject: Re: [RFC] Kernel Support of Memory Error Detection. To: =?UTF-8?B?SE9SSUdVQ0hJIE5BT1lBKOWggOWPoyDnm7TkuZ8p?= Cc: "Luck, Tony" , Nadav Amit , "dave.hansen@linux.intel.com" , David Hildenbrand , "Aktas, Erdem" , "pgonda@google.com" , "rientjes@google.com" , "Hsiao, Duen-wen" , "Vilas.Sridharan@amd.com" , "Malvestuto, Mike" , "gthelen@google.com" , "linux-mm@kvack.org" , "jthoughton@google.com" Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable ARC-Authentication-Results: i=1; imf26.hostedemail.com; dkim=pass header.d=google.com header.s=20210112 header.b=FJwNt96o; spf=pass (imf26.hostedemail.com: domain of jiaqiyan@google.com designates 209.85.215.182 as permitted sender) smtp.mailfrom=jiaqiyan@google.com; dmarc=pass (policy=reject) header.from=google.com ARC-Seal: i=1; s=arc-20220608; d=hostedemail.com; t=1668111800; a=rsa-sha256; cv=none; b=Wqc04V9nc3x5aymuAdvNuXWtTKLR+OZCiup/+oKr6PjPp8SBdEtM0YYnfN3QwCHpUmhkd5 3FDZNH76v5+Ap2ePAon6o2uyzkM8MlQKijnIzDTa1owAj/gukBhCXwsxd+uM5klQYTg4xN oCKO6ekPV24LTTSNFlGmFh4zGZUDka8= ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=hostedemail.com; s=arc-20220608; t=1668111800; 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:content-transfer-encoding: in-reply-to:in-reply-to:references:references:dkim-signature; bh=4AYdwauMWFqqDYXBV3jcMDZz3wipJiEn+s4Qc8tHNhA=; b=yy6M6IzxkwkbbAEHKSXwCRX4JXSbC2MfpFTt8Sp/fP60YYSfMGkfeaO5bhJnTwBZ0tlW24 9TjzqDLi2FgRprFXcRpYXcbXgpoMzKtcz2cApjKCcGLdLv/XA9/NxUTVDnl2i1BlEoG6Va xlDFjxQibTbcA4ewMyGJOlFn56fg14E= X-Rspam-User: Authentication-Results: imf26.hostedemail.com; dkim=pass header.d=google.com header.s=20210112 header.b=FJwNt96o; spf=pass (imf26.hostedemail.com: domain of jiaqiyan@google.com designates 209.85.215.182 as permitted sender) smtp.mailfrom=jiaqiyan@google.com; dmarc=pass (policy=reject) header.from=google.com X-Stat-Signature: 65rt7erfndc787tih84p6ucqkjftjxj8 X-Rspamd-Queue-Id: B1AF114000A X-Rspamd-Server: rspam09 X-HE-Tag: 1668111800-946707 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, Nov 8, 2022 at 9:04 PM HORIGUCHI NAOYA(=E5=A0=80=E5=8F=A3=E3=80=80= =E7=9B=B4=E4=B9=9F) wrote: > > On Tue, Nov 08, 2022 at 04:17:06PM +0000, Luck, Tony wrote: > > > If it is feasible in future that hardware vendors can make patrol > > > scrubber programmable, we can even direct the scanning to patrol > > > scrubber. > > > > There was an attempt to create an ACPI interface for this. I don't know= if it made > > it into the standard. > > I briefly checked the latest ACPI spec, and it seems that some interfaces > to control (h/w based) patrol scrubbing are defined. > > https://uefi.org/specs/ACPI/6.5/05_ACPI_Software_Programming_Model.html#a= cpi-ras-feature-table-rasf Thanks for the link! Once the "how to scan" part reaches consensus, we will make sure the concrete API/implementation is compatible/able to direct scan to patrol scrubber. > > > I didn't do anything with it for Linux because the interface was > > quite complex. > > > > From a h/w perspective it might always be complex. Consecutive system p= hysical > > addresses are generally interleaved across multiple memory controllers,= channels, > > DIMMs and ranks. While patrol scrubbing may be done by each memory cont= roller > > at the channel level. > > > > So a simple request to scan a few megabytes of system physical address = would > > require address translation to figure out the channel addresses on each= of the > > memory controllers and programming each to scan the pieces they contrib= ute to > > the target range. > > I expect that the physical address visible to the kernel is transparently > translated to the real address in which DIMM in which channel. > > - Naoya Horiguchi