public inbox for nvdimm@lists.linux.dev
 help / color / mirror / Atom feed
From: <dan.j.williams@intel.com>
To: Shubhakar Gowda <shubakargowdaps@gmail.com>, <dan.j.williams@intel.com>
Cc: <vishal.l.verma@intel.com>, <dave.jiang@intel.com>,
	<ira.weiny@intel.com>, <rafael@kernel.org>, <lenb@kernel.org>,
	<nvdimm@lists.linux.dev>, <linux-acpi@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>,
	Shubhakar Gowda <Shubhakar_gowda.P_s@dell.com>
Subject: Re: [PATCH] ACPI: NFIT:Advertise DSM function 0xA (Query ARS error inject capabilities)
Date: Fri, 23 Jan 2026 16:44:28 -0800	[thread overview]
Message-ID: <697415ec95e13_3095100cb@dwillia2-mobl4.notmuch> (raw)
In-Reply-To: <20260119184438.19942-1-Shubhakar_gowda.P_s@dell.com>

Shubhakar Gowda wrote:
> ACPI 6.6 defines DSM function index 0xA to Query Address Range Scrub
> (ARS) error injection capabilities. This patch adds support for this
> DSM function in the NFIT DSM mask so that userspace and ndctl tool can
> detect platform support for Query ARS error injection capabilities features.
> 
> The patch updates NFIT initialization to include DSM 0xA, logs
> supported DSMs for debugging, and uses the existing DSM infrastructure.
> No kernel ABI changes are introduced.

It does introduce new ABI. This new command can now be passed from
userspace. Can you say a bit more about why this is needed and the plans
for userspace to consume this? Like proposed changes to the "ndctl
inject-error" command, and otherwise what problems occur today with the
kernel blocking this command code?

      parent reply	other threads:[~2026-01-24  0:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-19 18:44 [PATCH] ACPI: NFIT:Advertise DSM function 0xA (Query ARS error inject capabilities) Shubhakar Gowda
2026-01-21 16:38 ` Ira Weiny
2026-01-24  0:44 ` dan.j.williams [this message]

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=697415ec95e13_3095100cb@dwillia2-mobl4.notmuch \
    --to=dan.j.williams@intel.com \
    --cc=Shubhakar_gowda.P_s@dell.com \
    --cc=dave.jiang@intel.com \
    --cc=ira.weiny@intel.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nvdimm@lists.linux.dev \
    --cc=rafael@kernel.org \
    --cc=shubakargowdaps@gmail.com \
    --cc=vishal.l.verma@intel.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