From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Linux ACPI <linux-acpi@vger.kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Zhang Rui <rui.zhang@intel.com>,
Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>,
Michal Wilczynski <michal.wilczynski@intel.com>,
Hans de Goede <hdegoede@redhat.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
Heikki Krogerus <heikki.krogerus@linux.intel.com>,
Mario Limonciello <mario.limonciello@amd.com>,
Daniel Drake <drake@endlessm.com>
Subject: [PATCH v1 0/3] ACPI: OSL/EC: Use spin locks without disabling interrupts
Date: Fri, 15 Dec 2023 12:23:54 +0100 [thread overview]
Message-ID: <2330034.ElGaqSPkdT@kreacher> (raw)
Hi Everyone,
After
https://patchwork.kernel.org/project/linux-acpi/patch/5745568.DvuYhMxLoT@kreacher/
the SCI interrupt handler is threaded, so ACPICA spin locks can be used without
disabling interrupts, because they cannot be acquired from a hardirq handler
running on the same CPU as any code already holding the spin lock. This patch
[1/3] removes disabling interrupts from acpi_os_acquire_lock() and updates
acpi_os_release_lock() accordingly.
Patch [2/2] uses the observation that if acpi_handle_interrupt() can run
in a threaded interrupt handler in the GPE case, it can also run in a threaded
interrupt handler in the dedicated IRQ case, so it makes the EC driver use a
threaded handler for the dedicated EC interrupt.
Patch [3/3], in analogy with patch [1/3], uses the observation that after patch
[2/2] all of the EC code runs in thread context, so it need not disable
interrupts on the local CPU before acquiring a spin lock, so the EC driver is
updated to operate its spin lock without disabling interrupts.
Thanks!
next reply other threads:[~2023-12-15 11:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-15 11:23 Rafael J. Wysocki [this message]
2023-12-15 11:25 ` [PATCH v1 1/3] ACPI: OSL: Use spin locks without disabling interrupts Rafael J. Wysocki
2023-12-15 11:26 ` [PATCH v1 2/3] ACPI: EC: Use a threaded handler for dedicated IRQ Rafael J. Wysocki
2023-12-15 11:27 ` [PATCH v1 3/3] ACPI: EC: Use a spin lock without disabing interrupts Rafael J. Wysocki
2023-12-28 13:18 ` [PATCH v1 0/3] ACPI: OSL/EC: Use spin locks without disabling interrupts 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=2330034.ElGaqSPkdT@kreacher \
--to=rjw@rjwysocki.net \
--cc=andriy.shevchenko@linux.intel.com \
--cc=drake@endlessm.com \
--cc=hdegoede@redhat.com \
--cc=heikki.krogerus@linux.intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=michal.wilczynski@intel.com \
--cc=mika.westerberg@linux.intel.com \
--cc=rui.zhang@intel.com \
--cc=srinivas.pandruvada@linux.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