[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <d8f3fda0-5c2d-f19c-23b7-7df6ac38ee41@intel.com>
Date: Tue, 1 Nov 2022 15:59:48 -0700
From: Sohil Mehta <sohil.mehta@...el.com>
To: "Joseph, Jithu" <jithu.joseph@...el.com>, <hdegoede@...hat.com>,
<markgross@...nel.org>
CC: <tglx@...utronix.de>, <mingo@...hat.com>, <bp@...en8.de>,
<dave.hansen@...ux.intel.com>, <x86@...nel.org>, <hpa@...or.com>,
<gregkh@...uxfoundation.org>, <ashok.raj@...el.com>,
<tony.luck@...el.com>, <linux-kernel@...r.kernel.org>,
<platform-driver-x86@...r.kernel.org>, <patches@...ts.linux.dev>,
<ravi.v.shankar@...el.com>, <thiago.macieira@...el.com>,
<athenas.jimenez.gonzalez@...el.com>
Subject: Re: [PATCH 13/14] Documentation/ABI: Update IFS ABI doc
On 11/1/2022 3:48 PM, Joseph, Jithu wrote:
> The testname would be inferred based the sysfs file context (the<N> in /sys/devices/virtual/misc/intel_ifs_<N>/current_batch) from which the operation is triggered.
>
> Meaning if the user writes to /sys/devices/virtual/misc/intel_ifs_0/current_batch it would look for ff-mm-ss.scan and if they write to
> /sys/devices/virtual/misc/intel_ifs_2/current_batch it would look for ff-mm-ss.<test_type_2>
>
So intel_ifs_<N> corresponds to <test_type> i.e. intel_ifs_0 maps to .scan
Is the N to test_type mapping visible to the user somewhere? If not, how
would the user infer that?
Would it be useful to name the misc device as intel_ifs_<test_type>?
Powered by blists - more mailing lists