From: Thomas Gleixner <tglx@linutronix.de>
To: LKML <linux-kernel@vger.kernel.org>
Cc: Jiang Liu <jiang.liu@linux.intel.com>,
x86@kernel.org, Bjorn Helgaas <bhelgaas@google.com>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Borislav Petkov <bp@alien8.de>, Yinghai Lu <yinghai@kernel.org>
Subject: [patch 4/4] acpi: ioapic: Respect the resource flags
Date: Thu, 11 Dec 2014 19:48:23 -0000 [thread overview]
Message-ID: <20141211193112.813391696@linutronix.de> (raw)
In-Reply-To: <20141211191853.613107396@linutronix.de>
[-- Attachment #1: acpi-ioapoc-respect-resource-flags.patch --]
[-- Type: text/plain, Size: 2387 bytes --]
The acpi parser can set the DISABLED flag on a resource. In
setup_res() we clear all flags except MEM, so we ignore the DISABLED
flag. Add proper checks and preserve the flags.
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
---
drivers/acpi/ioapic.c | 38 +++++++++++++++++++++-----------------
1 file changed, 21 insertions(+), 17 deletions(-)
Index: tip/drivers/acpi/ioapic.c
===================================================================
--- tip.orig/drivers/acpi/ioapic.c
+++ tip/drivers/acpi/ioapic.c
@@ -40,29 +40,33 @@ struct acpi_pci_ioapic {
static LIST_HEAD(ioapic_list);
static DEFINE_MUTEX(ioapic_list_lock);
+static inline bool is_valid_mem_resource(struct resource *res)
+{
+ return !(res->flags & IORESOURCE_DISABLED) &&
+ (res->flags & IORESOURCE_MEM);
+}
+
static acpi_status setup_res(struct acpi_resource *acpi_res, void *data)
{
+ struct acpi_resource_address64 addr;
struct resource *res = data;
memset(res, 0, sizeof(*res));
- if (acpi_dev_resource_memory(acpi_res, res)) {
- res->flags &= IORESOURCE_MEM;
- if (res->flags)
- return AE_OK;
- } else if (acpi_dev_resource_address_space(acpi_res, res)) {
- struct acpi_resource_address64 addr;
+ if (acpi_dev_resource_memory(acpi_res, res))
+ return AE_OK;
- res->flags &= IORESOURCE_MEM;
- if (res->flags &&
- ACPI_SUCCESS(acpi_resource_to_address64(acpi_res, &addr)) &&
- addr.info.mem.caching != ACPI_PREFETCHABLE_MEMORY) {
- res->start += addr.translation_offset;
- res->end += addr.translation_offset;
- return AE_OK;
- }
+ if (!acpi_dev_resource_address_space(acpi_res, res) ||
+ !is_valid_mem_resource(res))
+ return AE_OK;
+ /*
+ * FIXME: This lacks a proper comment, why the resource
+ * address needs to be translated.
+ */
+ if (ACPI_SUCCESS(acpi_resource_to_address64(acpi_res, &addr)) &&
+ addr.info.mem.caching != ACPI_PREFETCHABLE_MEMORY) {
+ res->start += addr.translation_offset;
+ res->end += addr.translation_offset;
}
- res->flags = 0;
-
return AE_OK;
}
@@ -150,7 +154,7 @@ static acpi_status handle_ioapic_add(acp
res = &ioapic->res;
acpi_walk_resources(handle, METHOD_NAME__CRS, setup_res, res);
- if (res->flags == IORESOURCE_UNSET) {
+ if (!is_valid_mem_resource(res)) {
acpi_handle_warn(handle, "failed to get resource\n");
goto exit_free;
} else if (request_resource(&iomem_resource, res)) {
next prev parent reply other threads:[~2014-12-11 19:48 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-11 19:48 [patch 0/4] x86: Fix the ACPI resource handling and range checking Thomas Gleixner
2014-12-11 19:48 ` [patch 1/4] x86, pci, acpi: Redo sanity checks for root brigde probing Thomas Gleixner
2014-12-12 11:33 ` Borislav Petkov
2014-12-11 19:48 ` [patch 2/4] x86: pci: acpi: Respect ioresource flags Thomas Gleixner
2014-12-12 13:39 ` Borislav Petkov
2014-12-11 19:48 ` [patch 3/4] x86: pci: acpi: Fix the range check for IO resources Thomas Gleixner
2014-12-12 14:56 ` Borislav Petkov
2014-12-11 19:48 ` Thomas Gleixner [this message]
2014-12-12 2:44 ` [patch 4/4] acpi: ioapic: Respect the resource flags Yinghai Lu
2014-12-12 7:53 ` Thomas Gleixner
2014-12-12 8:24 ` Yinghai Lu
2014-12-12 8:46 ` Jiang Liu
2014-12-12 11:43 ` Thomas Gleixner
2014-12-17 5:44 ` Jiang Liu
2014-12-17 8:55 ` Thomas Gleixner
2014-12-12 11:39 ` Thomas Gleixner
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=20141211193112.813391696@linutronix.de \
--to=tglx@linutronix.de \
--cc=bhelgaas@google.com \
--cc=bp@alien8.de \
--cc=jiang.liu@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=x86@kernel.org \
--cc=yinghai@kernel.org \
/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
Powered by JetHome