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>?
