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 5975DC433FE for ; Fri, 18 Nov 2022 01:19:57 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id ED6668E0001; Thu, 17 Nov 2022 20:19:56 -0500 (EST) Received: by kanga.kvack.org (Postfix, from userid 40) id E867E6B0073; Thu, 17 Nov 2022 20:19:56 -0500 (EST) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id D4E5A8E0001; Thu, 17 Nov 2022 20:19:56 -0500 (EST) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (smtprelay0014.hostedemail.com [216.40.44.14]) by kanga.kvack.org (Postfix) with ESMTP id C6A116B0072 for ; Thu, 17 Nov 2022 20:19:56 -0500 (EST) Received: from smtpin24.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay05.hostedemail.com (Postfix) with ESMTP id 995AC40185 for ; Fri, 18 Nov 2022 01:19:56 +0000 (UTC) X-FDA: 80144806392.24.39D4139 Received: from mail-pf1-f172.google.com (mail-pf1-f172.google.com [209.85.210.172]) by imf02.hostedemail.com (Postfix) with ESMTP id 4E53C80006 for ; Fri, 18 Nov 2022 01:19:55 +0000 (UTC) Received: by mail-pf1-f172.google.com with SMTP id b185so3464860pfb.9 for ; Thu, 17 Nov 2022 17:19:55 -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=FNI2SIRwLbmLuiyKce76UpCzLnjgSBFD7jaGR9ssdZc=; b=PixvEutISBFac98tAyUDZZHTJzLtLFRiGXjQvT08muoCQHGQujOiEGVYtRbmqIRHtY 6F7yVhDae+DXmpRo231boY9C7R/Cuzzj7Hh5eNEUnpNy8IzozY8jGH39uvGWZmi9FFhg j98Ihq5WlM92edW3bbYDTLN0WFokQ2IGK7FHKQPqTd/h7SQi26w5+mTquLdxwuiTvd2O zxD5LSvYJRbTFiMe6sQkyiBw2+hLT1p9Rn6JEf41UIIg68Y3UWnGmBQU/3aHoGzfaY01 7kjKSkx3dXhbWpqL8jbJE/caMVv4/gxDzcIdHLPA6GnI8fZKnnWRnomj2JY+W8dhmDvt q9Gw== 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=FNI2SIRwLbmLuiyKce76UpCzLnjgSBFD7jaGR9ssdZc=; b=xqkpPftjbYv6a74X6vUDOgSsvc3dKMegcmvFAk2W4ad6RBk5c6Uu9tG/iet4aDSrad TfbLV+fqtpGqrMo4Sjwgsm7Qn/C9wrmuitAtO428OcJozpg2URJStiWZXqoqpIAa6HKb PUoytZqNdpphOvRJ9DUuEd/lfmzy4lC06AS7KeQd2XMEAq+BWruXfetHJLq8F6t6eih6 4RGp2rQL1LXHqNrO5hefpbG4JCpYMLNy+u71S3X8f/NX3Vdh1Ham5zx7cXdnCZmkazp4 OjhJvd6qhaquX82/46GTmspJjsmCmxXs96s92xQLL0C8/qFQM0QkkSgRjn8BX9/FtvZq T6qg== X-Gm-Message-State: ANoB5pm8Q0i4sZGjeFGVThdKE8lxEJJcocbEE0vMSnT0Lba/G/24AoAQ eSQkq8qL/7rqce9smegWiLshHYMO71Na7b1qy/H2ew== X-Google-Smtp-Source: AA0mqf5LkpCkavgwPuX366/Pm3Q4tk+NW9MxClsmENp+a0su705fzkgnYga2nL76Sjaglub+42Rv8MEZsYZ713c7xWM= X-Received: by 2002:a63:1626:0:b0:46e:96b9:ed63 with SMTP id w38-20020a631626000000b0046e96b9ed63mr4668287pgl.258.1668734394060; Thu, 17 Nov 2022 17:19:54 -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, 17 Nov 2022 17:19:43 -0800 Message-ID: Subject: Re: [RFC] Kernel Support of Memory Error Detection. To: "Vilas.Sridharan@amd.com" , "Malvestuto, Mike" Cc: =?UTF-8?B?SE9SSUdVQ0hJIE5BT1lBKOWggOWPoyDnm7TkuZ8p?= , Nadav Amit , David Hildenbrand , "Aktas, Erdem" , "pgonda@google.com" , "rientjes@google.com" , "Hsiao, Duen-wen" , "gthelen@google.com" , "linux-mm@kvack.org" , "jthoughton@google.com" , "dave.hansen@linux.intel.com" , "Luck, Tony" Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable ARC-Seal: i=1; s=arc-20220608; d=hostedemail.com; t=1668734395; a=rsa-sha256; cv=none; b=Ye0DiCHwy/LA89k82J5gkRRTBiho8Lte5ycuf9i1Y/EKVfURgKeCJsgcXLtdWqkSPxUyae Xz4UbxonR/eGYiExwYnhl3AyXz8VkSr+cIZ0yOpqYCagQa02H4e5Z6/FyFERApbMM7D/zv /aLQ32SzoDb5n6u98X1RGMLUMjHNIvA= ARC-Authentication-Results: i=1; imf02.hostedemail.com; dkim=pass header.d=google.com header.s=20210112 header.b=PixvEutI; dmarc=pass (policy=reject) header.from=google.com; spf=pass (imf02.hostedemail.com: domain of jiaqiyan@google.com designates 209.85.210.172 as permitted sender) smtp.mailfrom=jiaqiyan@google.com ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=hostedemail.com; s=arc-20220608; t=1668734395; 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=FNI2SIRwLbmLuiyKce76UpCzLnjgSBFD7jaGR9ssdZc=; b=SK1FJ8i1Hh3rbZJH5q4G6CvH+85S5dvPe8Dz9hpzZmD0rxfj7Xkq9HMkn9xrToGhpvC7o7 sc5/OKhB3Da0qMKqWIodNFr+K5tSmOfullQSQHWcTZ0lCCp4Qjljl3OtCIGI2uMtdQ3mfh MVhxr9QTOD2RKBE6rl1xEgqQRriTG0Q= Authentication-Results: imf02.hostedemail.com; dkim=pass header.d=google.com header.s=20210112 header.b=PixvEutI; dmarc=pass (policy=reject) header.from=google.com; spf=pass (imf02.hostedemail.com: domain of jiaqiyan@google.com designates 209.85.210.172 as permitted sender) smtp.mailfrom=jiaqiyan@google.com X-Rspam-User: X-Stat-Signature: zfqpxdofaggw1k3jbybkozkffu3c51ez X-Rspamd-Queue-Id: 4E53C80006 X-Rspamd-Server: rspam11 X-HE-Tag: 1668734395-821581 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 A followup question to Intel and AMD RAS folks (Mike and Vilas), what is your position on the ACPI interface to control hw patrol scrubber, and further make it programmable by kernel? Is this something you are willing to consider? > > > 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