From: Jan Kiszka <jan.kiszka@siemens.com>
To: Mika Westerberg <mika.westerberg@linux.intel.com>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
Len Brown <lenb@kernel.org>, Lv Zheng <lv.zheng@intel.com>,
linux-acpi@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
devel@acpica.org, Bob Moore <robert.moore@intel.com>
Subject: Re: [PATCH] acpi: configfs: Unload SSDT on configfs entry removal
Date: Mon, 29 May 2017 14:53:11 +0200 [thread overview]
Message-ID: <fff98a5c-e18f-d326-e5de-7401173d9af4@siemens.com> (raw)
In-Reply-To: <20170529124755.GR2784@lahna.fi.intel.com>
On 2017-05-29 14:47, Mika Westerberg wrote:
> On Mon, May 29, 2017 at 01:33:29PM +0200, Jan Kiszka wrote:
>> Enhance acpi_load_table to also return the table index. Use that index
>> to unload the table again when the corresponding directory in configfs
>> gets removed. This allows to change SSDTs without rebooting the system.
>> It also allows to destroy devices again that a dynamically loaded SSDT
>> created.
>>
>> This is widely similar to the DT overlay behavior.
>>
>> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
>> ---
>>
>> Can someone explain to me why an unloaded table still sticks around in
>> sysfs and why we cannot release its ID and rather have to use a new one
>> when loading a modified version?
>
> IIRC ACPICA relies the fact that SSDTs are never unloaded. Bob (CC'd)
> can correct me if I got it wrong.
OK... Is that standard-driven or just a limitation of this implementation?
Is there an upper limit of tables? I'm thinking of lengthy development
sessions that play with tables, loading and unloading modified versions.
Jan
--
Siemens AG, Corporate Technology, CT RDA ITP SES-DE
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2017-05-29 12:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-29 11:33 Jan Kiszka
2017-05-29 12:47 ` Mika Westerberg
2017-05-29 12:53 ` Jan Kiszka [this message]
2017-05-30 21:16 ` Moore, Robert
2017-05-30 21:41 ` Rafael J. Wysocki
2017-05-31 14:30 ` Moore, Robert
2017-05-31 16:39 ` Jan Kiszka
2017-05-31 22:47 ` Rafael J. Wysocki
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=fff98a5c-e18f-d326-e5de-7401173d9af4@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=devel@acpica.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lv.zheng@intel.com \
--cc=mika.westerberg@linux.intel.com \
--cc=rjw@rjwysocki.net \
--cc=robert.moore@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
all inboxes | Powered by JetHome®