From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Linux ACPI <linux-acpi@vger.kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Erik Kaneda <erik.kaneda@intel.com>,
Bob Moore <robert.moore@intel.com>,
Len Brown <len.brown@intel.com>,
Dan Williams <dan.j.williams@intel.com>,
Dan Williams <dan.j.williams.korg@gmail.com>
Subject: [PATCH 1/3] ACPI: OSL: Use deferred unmapping in acpi_os_unmap_generic_address()
Date: Thu, 02 Jul 2020 14:11:12 +0200 [thread overview]
Message-ID: <2627540.Zly3GVl0Zp@kreacher> (raw)
In-Reply-To: <22474080.3crLlKV2y5@kreacher>
From: "Rafael J. Wysocki" <rafael.j.wysocki@intel.com>
There is no reason (knwon to me) why any of the existing users of
acpi_os_unmap_generic_address() would need to wait for the unused
memory mappings left by it to actually go away, so use the deferred
unmapping of ACPI memory introduced previously in that function.
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
---
drivers/acpi/osl.c | 5 +----
1 file changed, 1 insertion(+), 4 deletions(-)
diff --git a/drivers/acpi/osl.c b/drivers/acpi/osl.c
index abbf8630f774..5c56f084e8b0 100644
--- a/drivers/acpi/osl.c
+++ b/drivers/acpi/osl.c
@@ -518,12 +518,9 @@ void acpi_os_unmap_generic_address(struct acpi_generic_address *gas)
mutex_unlock(&acpi_ioremap_lock);
return;
}
- if (acpi_os_drop_map_ref(map, false))
- map = NULL;
+ acpi_os_drop_map_ref(map, true);
mutex_unlock(&acpi_ioremap_lock);
-
- acpi_os_map_cleanup(map);
}
EXPORT_SYMBOL(acpi_os_unmap_generic_address);
--
2.26.2
next prev parent reply other threads:[~2020-07-02 12:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-02 12:09 [PATCH 0/3] ACPI: OSL: Always use deferred unmapping of memory Rafael J. Wysocki
2020-07-02 12:11 ` Rafael J. Wysocki [this message]
2020-07-02 12:13 ` [PATCH 2/3] ACPI: OSL: Use deferred unmapping in acpi_os_unmap_iomem() Rafael J. Wysocki
2020-07-02 12:14 ` [PATCH 3/3] ACPI: OSL: Clean up the removal of unused memory mappings 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=2627540.Zly3GVl0Zp@kreacher \
--to=rjw@rjwysocki.net \
--cc=dan.j.williams.korg@gmail.com \
--cc=dan.j.williams@intel.com \
--cc=erik.kaneda@intel.com \
--cc=len.brown@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).