From: David Rientjes <rientjes@google.com>
To: Jiaqi Yan <jiaqiyan@google.com>,
"Luck, Tony" <tony.luck@intel.com>,
"Grimm, Jon" <jon.grimm@amd.com>,
dave.hansen@linux.intel.com, vilas.sridharan@amd.com
Cc: Jonathan Cameron <Jonathan.Cameron@huawei.com>,
linuxarm@huawei.com, shiju.jose@huawei.com,
linux-acpi@vger.kernel.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, rafael@kernel.org, lenb@kernel.org,
naoya.horiguchi@nec.com, james.morse@arm.com, david@redhat.com,
jthoughton@google.com, somasundaram.a@hpe.com,
erdemaktas@google.com, pgonda@google.com, duenwen@google.com,
mike.malvestuto@intel.com, gthelen@google.com,
tanxiaofei@huawei.com, prime.zeng@hisilicon.com
Subject: Re: [RFC PATCH 2/9] memory: scrub: sysfs: Add Documentation entries for set of scrub attributes
Date: Wed, 4 Oct 2023 20:18:12 -0700 (PDT) [thread overview]
Message-ID: <92f48c1c-3235-49b2-aabd-7da87ad3febc@google.com> (raw)
In-Reply-To: <CACw3F539gZc0FoJLo6VvYSyZmeWZ3Pbec7AzsH+MYUJJNzQbUQ@mail.gmail.com>
On Wed, 27 Sep 2023, Jiaqi Yan wrote:
> > > 1. I am not aware of any chip/platform hardware that implemented the
> > > hw ps part defined in ACPI RASF/RAS2 spec. So I am curious what the
> > > RAS experts from different hardware vendors think about this. For
> > > example, Tony and Dave from Intel, Jon and Vilas from AMD. Is there
> > > any hardware platform (if allowed to disclose) that implemented ACPI
> > > RASF/RAS2? If so, will vendors continue to support the control of
> > > patrol scrubber using the ACPI spec? If not (as Tony said in [1], will
> > > the vendor consider starting some future platform?
> > >
> > > If we are unlikely to get the vendor support, creating this ACPI
> > > specific sysfs API (and the driver implementations) in Linux seems to
> > > have limited meaning.
> >
> > There is a bit of a chicken and egg problem here. Until there is
> > reasonable support in kernel (or it looks like there will be),
> > BIOS teams push back on a requirement to add the tables.
> > I'd encourage no one to bother with RASF - RAS2 is much less
> > ambiguous.
>
> Here mainly to re-ping folks from Intel (Tony and Dave) and AMD (Jon
> and Vilas) for your opinion on RAS2.
>
We'll need to know from vendors, ideally at minimum from both Intel and
AMD, whether RAS2 is the long-term vision here. Nothing is set in stone,
of course, but deciding whether RAS2 is the standard that we should be
rallying around will help to guide future development including in the
kernel.
If RAS2 is insufficient for future use cases or we would need to support
multiple implementations in the kernel for configuring the patrol scrubber
depending on vendor, that's great feedback to have.
I'd much rather focus on implementing something in the kernel that we have
some clarity about the vendors supporting, especially when it comes with
user visible interfaces, as opposed to something that may not be used long
term. I think that's a fair ask and that vendor feedback is required
here?
next prev parent reply other threads:[~2023-10-05 14:11 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-15 17:28 [RFC PATCH 0/9] ACPI:RASF: Add support for ACPI RASF, ACPI RAS2 and configure scrubbers shiju.jose
2023-09-15 17:28 ` [RFC PATCH 1/9] memory: scrub: Add scrub driver supports configuring memory scrubbers in the system shiju.jose
2023-09-15 17:28 ` [RFC PATCH 2/9] memory: scrub: sysfs: Add Documentation entries for set of scrub attributes shiju.jose
2023-09-22 0:07 ` Jiaqi Yan
2023-09-22 10:20 ` Jonathan Cameron
2023-09-28 5:25 ` Jiaqi Yan
2023-09-28 13:14 ` Jonathan Cameron
2023-10-05 3:18 ` David Rientjes [this message]
2023-10-06 13:02 ` Jonathan Cameron
2023-10-06 13:06 ` Sridharan, Vilas
2023-10-11 16:35 ` Jonathan Cameron
2023-10-12 13:41 ` Sridharan, Vilas
2023-10-12 15:02 ` Jonathan Cameron
2023-10-12 15:44 ` Sridharan, Vilas
2023-10-13 9:07 ` Jonathan Cameron
2023-09-15 17:28 ` [RFC PATCH 3/9] Documentation/scrub-configure.rst: Add documentation for scrub driver shiju.jose
2023-09-18 7:23 ` David Hildenbrand
2023-09-18 10:25 ` Shiju Jose
2023-09-18 12:15 ` David Hildenbrand
2023-09-18 12:28 ` Jonathan Cameron
2023-09-18 12:34 ` David Hildenbrand
2023-09-18 15:03 ` Shiju Jose
2023-09-15 17:28 ` [RFC PATCH 4/9] ACPI:RASF: Add extract RASF table to register RASF platform devices shiju.jose
2023-09-15 17:28 ` [RFC PATCH 5/9] ACPI:RASF: Add common library for RASF and RAS2 PCC interfaces shiju.jose
2023-09-15 17:28 ` [RFC PATCH 6/9] memory: RASF: Add memory RASF driver shiju.jose
2023-09-15 17:28 ` [RFC PATCH 7/9] ACPICA: ACPI 6.5: Add support for RAS2 table shiju.jose
2023-09-15 17:28 ` [RFC PATCH 8/9] ACPI:RAS2: Add driver for ACPI RAS2 feature table (RAS2) shiju.jose
2023-09-15 17:28 ` [RFC PATCH 9/9] memory: RAS2: Add memory RAS2 driver shiju.jose
2023-09-17 21:14 ` [RFC PATCH 0/9] ACPI:RASF: Add support for ACPI RASF, ACPI RAS2 and configure scrubbers Jiaqi Yan
2023-09-18 10:19 ` Shiju Jose
2023-09-18 17:47 ` Jiaqi Yan
2023-09-19 8:28 ` Shiju Jose
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=92f48c1c-3235-49b2-aabd-7da87ad3febc@google.com \
--to=rientjes@google.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=dave.hansen@linux.intel.com \
--cc=david@redhat.com \
--cc=duenwen@google.com \
--cc=erdemaktas@google.com \
--cc=gthelen@google.com \
--cc=james.morse@arm.com \
--cc=jiaqiyan@google.com \
--cc=jon.grimm@amd.com \
--cc=jthoughton@google.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linuxarm@huawei.com \
--cc=mike.malvestuto@intel.com \
--cc=naoya.horiguchi@nec.com \
--cc=pgonda@google.com \
--cc=prime.zeng@hisilicon.com \
--cc=rafael@kernel.org \
--cc=shiju.jose@huawei.com \
--cc=somasundaram.a@hpe.com \
--cc=tanxiaofei@huawei.com \
--cc=tony.luck@intel.com \
--cc=vilas.sridharan@amd.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).