From: Hans de Goede <hdegoede@redhat.com>
To: "Barnabás Pőcze" <pobrn@protonmail.com>,
"Mark Pearson" <markpearson@lenovo.com>
Cc: "rjw@rjwysocki.net" <rjw@rjwysocki.net>,
"mgross@linux.intel.com" <mgross@linux.intel.com>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
"mario.limonciello@dell.com" <mario.limonciello@dell.com>,
"eliadevito@gmail.com" <eliadevito@gmail.com>,
"hadess@hadess.net" <hadess@hadess.net>,
"bberg@redhat.com" <bberg@redhat.com>,
"platform-driver-x86@vger.kernel.org"
<platform-driver-x86@vger.kernel.org>,
"dvhart@infradead.org" <dvhart@infradead.org>
Subject: Re: [PATCH v3] ACPI: platform-profile: Add platform profile support
Date: Sat, 21 Nov 2020 15:27:37 +0100 [thread overview]
Message-ID: <761671b3-ad26-230b-e709-05ce3bd69498@redhat.com> (raw)
In-Reply-To: <nRyY5CKaU6WrkbMiM25gTT_bJlrQjTY_UCcQkj8ty-2mPEMVZd4BB9KwrRp7z4GaE3TTOFCXuXnt0_7J_Tj50syusBxTmS5yNZAvYX02X74=@protonmail.com>
Hi,
On 11/20/20 8:50 PM, Barnabás Pőcze wrote:
> Hi
>
>
> 2020. november 15., vasárnap 1:44 keltezéssel, Mark Pearson írta:
>
>> [...]
>> +int platform_profile_register(struct platform_profile_handler *pprof)
>> +{
>> + mutex_lock(&profile_lock);
>> + /* We can only have one active profile */
>> + if (cur_profile) {
>> + mutex_unlock(&profile_lock);
>> + return -EEXIST;
>> + }
>> +
>> + cur_profile = pprof;
>> + mutex_unlock(&profile_lock);
>> + return sysfs_create_group(acpi_kobj, &platform_profile_group);
>> +}
>> +EXPORT_SYMBOL_GPL(platform_profile_register);
>> +
>> +int platform_profile_unregister(void)
>> +{
>> + mutex_lock(&profile_lock);
>> + sysfs_remove_group(acpi_kobj, &platform_profile_group);
>> + cur_profile = NULL;
>> + mutex_unlock(&profile_lock);
>> + return 0;
>> +}
>> +EXPORT_SYMBOL_GPL(platform_profile_unregister);
>> [...]
>
>
> I just realized that the sysfs attributes are only created if a profile provider
> is registered, and it is removed when the provide unregisters itself. I believe
> it would be easier for system daemons if those attributes existed from module load
> to module unload since they can just just open the file and watch it using poll,
> select, etc. If it goes away when the provider unregisters itself, then I believe
> a more complicated mechanism (like inotify) would need to be implemented in the
> daemons to be notified when a new provider is registered. Thus my suggestion
> for the next iteration is to create the sysfs attributes on module load,
> and delete them on unload.
>
> What do you think?
Actually I asked Mark to move this to the register / unregister time since
having a non functioning files in sysfs is a bit weird.
You make a good point about userspace having trouble figuring when this will
show up though (I'm not worried about removal that will normally never happen).
I would expect all modules to be loaded before any interested daemons load,
but that is an assumption and I must admit that that is a bit racy.
Bastien, what do you think about Barnabás' suggestion to always have the
files present and use poll (POLL_PRI) on it to see when it changes, listing
maybe "none" as available profiles when there is no provider?
Regards,
Hans
next prev parent reply other threads:[~2020-11-21 14:28 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-15 0:44 [PATCH v3] ACPI: platform-profile: Add platform profile support Mark Pearson
2020-11-15 18:26 ` Barnabás Pőcze
2020-11-15 23:04 ` [External] " Mark Pearson
2020-11-16 10:24 ` Barnabás Pőcze
2020-11-16 15:25 ` Mark Pearson
2020-11-16 14:33 ` Hans de Goede
2020-11-16 15:19 ` Mark Pearson
2020-11-20 19:50 ` Barnabás Pőcze
2020-11-21 4:14 ` [External] " Mark Pearson
2020-11-21 14:27 ` Hans de Goede [this message]
2020-11-21 21:18 ` Barnabás Pőcze
2020-11-22 9:32 ` Hans de Goede
2020-11-24 15:30 ` Bastien Nocera
2020-11-25 16:42 ` Hans de Goede
2020-11-25 19:41 ` [External] " Mark Pearson
2020-11-25 22:32 ` Bastien Nocera
2020-11-26 10:36 ` Hans de Goede
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=761671b3-ad26-230b-e709-05ce3bd69498@redhat.com \
--to=hdegoede@redhat.com \
--cc=bberg@redhat.com \
--cc=dvhart@infradead.org \
--cc=eliadevito@gmail.com \
--cc=hadess@hadess.net \
--cc=linux-acpi@vger.kernel.org \
--cc=mario.limonciello@dell.com \
--cc=markpearson@lenovo.com \
--cc=mgross@linux.intel.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=pobrn@protonmail.com \
--cc=rjw@rjwysocki.net \
/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).