From: Riana Tauro <riana.tauro@intel.com>
To: Lucas De Marchi <lucas.demarchi@intel.com>,
Michal Wajdeczko <michal.wajdeczko@intel.com>
Cc: <intel-xe@lists.freedesktop.org>
Subject: Re: [PATCH 1/3] drm/xe/configfs: Don't touch survivability_mode on fini
Date: Wed, 3 Sep 2025 11:09:53 +0530 [thread overview]
Message-ID: <12059b2e-e91b-4db6-9602-ac2b09b460b9@intel.com> (raw)
In-Reply-To: <qeq32k6xksjwzg7saglvxlodqxkr75mofjnmfv2bx2dzanciol@2c7ouidjtxly>
On 9/2/2025 11:34 PM, Lucas De Marchi wrote:
> On Tue, Sep 02, 2025 at 03:17:42PM +0200, Michal Wajdeczko wrote:
>> This is a user controlled configfs attribute, we should not
>> modify that outside the configfs attr.store() implementation.
>
> agreed... this was the first user of configfs and I don't think it was
> the right to do it. However for such a change we should propagate it to
> stable too. Riana, any possible issue in userspace? With this change
> userspace should do a rmdir() before proceeding so it drops the
> configuration.
Survivability mode is enabled in early probe and is used for firmware
flashing by admin. If this is not cleared while exiting the mode the
driver keeps entering survivability mode on every unbind/bind till admin
clears the mode in configfs.
rmdir is general and can affect other entries. For survivability mode,
it's better to retain this clear.
Thanks
Riana
>
> Lucas De Marchi
>
>>
>> Signed-off-by: Michal Wajdeczko <michal.wajdeczko@intel.com>
>> Cc: Lucas De Marchi <lucas.demarchi@intel.com>
>> Cc: Riana Tauro <riana.tauro@intel.com>
>> ---
>> drivers/gpu/drm/xe/xe_survivability_mode.c | 1 -
>> 1 file changed, 1 deletion(-)
>>
>> diff --git a/drivers/gpu/drm/xe/xe_survivability_mode.c b/drivers/gpu/
>> drm/xe/xe_survivability_mode.c
>> index 53c5af4b810c..79426ea46861 100644
>> --- a/drivers/gpu/drm/xe/xe_survivability_mode.c
>> +++ b/drivers/gpu/drm/xe/xe_survivability_mode.c
>> @@ -180,7 +180,6 @@ static void xe_survivability_mode_fini(void *arg)
>> struct pci_dev *pdev = to_pci_dev(xe->drm.dev);
>> struct device *dev = &pdev->dev;
>>
>> - xe_configfs_clear_survivability_mode(pdev);
>> sysfs_remove_file(&dev->kobj, &dev_attr_survivability_mode.attr);
>> }
>>
>> --
>> 2.47.1
>>
next prev parent reply other threads:[~2025-09-03 5:40 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-02 13:17 [PATCH 0/3] Allow to filter-out some configfs attrs Michal Wajdeczko
2025-09-02 13:17 ` [PATCH 1/3] drm/xe/configfs: Don't touch survivability_mode on fini Michal Wajdeczko
2025-09-02 16:37 ` Summers, Stuart
2025-09-02 18:04 ` Lucas De Marchi
2025-09-03 5:39 ` Riana Tauro [this message]
2025-09-03 5:49 ` Michal Wajdeczko
2025-09-03 17:50 ` Lucas De Marchi
2025-09-03 19:47 ` Michal Wajdeczko
2025-09-04 4:36 ` Riana Tauro
2025-09-04 10:35 ` [PATCH v2 " Michal Wajdeczko
2025-09-04 15:56 ` Lucas De Marchi
2025-09-09 5:16 ` Riana Tauro
2025-09-02 13:17 ` [PATCH 2/3] drm/xe/configfs: Prepare to filter-out configfs attributes Michal Wajdeczko
2025-09-02 13:17 ` [PATCH 3/3] drm/xe/configfs: Don't expose survivability_mode if not applicable Michal Wajdeczko
2025-09-02 17:25 ` Summers, Stuart
2025-09-02 18:16 ` Michal Wajdeczko
2025-09-02 18:19 ` Summers, Stuart
2025-09-02 18:10 ` Lucas De Marchi
2025-09-02 15:19 ` ✓ CI.KUnit: success for Allow to filter-out some configfs attrs Patchwork
2025-09-02 15:56 ` ✓ Xe.CI.BAT: " Patchwork
2025-09-02 20:41 ` ✗ Xe.CI.Full: failure " Patchwork
2025-09-04 10:54 ` ✓ CI.KUnit: success for Allow to filter-out some configfs attrs (rev2) Patchwork
2025-09-04 11:30 ` ✓ Xe.CI.BAT: " Patchwork
2025-09-04 23:14 ` ✗ Xe.CI.Full: failure " Patchwork
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=12059b2e-e91b-4db6-9602-ac2b09b460b9@intel.com \
--to=riana.tauro@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=lucas.demarchi@intel.com \
--cc=michal.wajdeczko@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