From: James Liu <james.liu@hpe.com>
To: rafael@kernel.org, lenb@kernel.org
Cc: linux-acpi@vger.kernel.org
Subject: Re: [PATCH] ACPI: OSL: Fix the memory mapping of an ACPI GAS that addresses a data structure
Date: Tue, 17 May 2022 12:17:43 +0000 [thread overview]
Message-ID: <20220517121743.GA4191@ubuntu-20.04.3> (raw)
In-Reply-To: <20220401172840.1252-1-james.liu@hpe.com>
Hi Rafael and all,
Could you take a look at this patch? The mentioned bug blocks EINJ testing
when a firmware can correctly support ACPI 6.4 spec.
On Fri, Apr 01, 2022 at 05:28:40PM +0000, james.liu@hpe.com wrote:
> From: James Liu <james.liu@hpe.com>
>
> Modify acpi_os_map_generic_address and acpi_os_unmap_generic_address
> to handle a case that a GAS table (i.e., Table 5.1 in ACPI 6.4) is used
> to address a data structure; in this case, the GAS has the field of
> "Register Bit Width" equal to 0.
>
> For example, "Injection Instruction Entry" (Table 18.25 in ACPI 6.4)
> has a RegisterRegion field that is a GAS that points to a data
> structure SET_ERROR_TYPE_WITH_ADDRESS (Table 18.30), which is required
> when using EINJ (Error Injection module).
>
> This fix preserves a fairly sufficient memory space (i.e., page size)
> to store the data structure so as to prevent EINJ module from loading
> failure if platform firmware can support Injection Instruction Entry in
> an EINJ table.
>
> Signed-off-by: James Liu <james.liu@hpe.com>
> ---
> drivers/acpi/osl.c | 23 +++++++++++++++++++++--
> 1 file changed, 21 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/acpi/osl.c b/drivers/acpi/osl.c
> index 45c5c0e45..ab2f584b1 100644
> --- a/drivers/acpi/osl.c
> +++ b/drivers/acpi/osl.c
> @@ -457,9 +457,15 @@ void __iomem *acpi_os_map_generic_address(struct acpi_generic_address *gas)
> if (gas->space_id != ACPI_ADR_SPACE_SYSTEM_MEMORY)
> return NULL;
>
> + /* Handle a case that GAS is used to address an ACPI data structure */
> + if (!gas->bit_width) {
> + pr_info("An ACPI data structure at 0x%llx is mapped\n", addr);
> + return acpi_os_map_iomem(addr, PAGE_SIZE);
> + }
> +
> /* Handle possible alignment issues */
> memcpy(&addr, &gas->address, sizeof(addr));
> - if (!addr || !gas->bit_width)
> + if (!addr)
> return NULL;
>
> return acpi_os_map_iomem(addr, gas->bit_width / 8);
> @@ -474,9 +480,22 @@ void acpi_os_unmap_generic_address(struct acpi_generic_address *gas)
> if (gas->space_id != ACPI_ADR_SPACE_SYSTEM_MEMORY)
> return;
>
> + /* Handle a case that GAS is used to address an ACPI data structure */
> + if (!gas->bit_width) {
> + pr_info("An ACPI data structure at 0x%llx is unmapped\n", addr);
> + mutex_lock(&acpi_ioremap_lock);
> + map = acpi_map_lookup(addr, PAGE_SIZE);
> + if (!map) {
> + mutex_unlock(&acpi_ioremap_lock);
> + return;
> + }
> + acpi_os_drop_map_ref(map);
> + mutex_unlock(&acpi_ioremap_lock);
> + }
> +
> /* Handle possible alignment issues */
> memcpy(&addr, &gas->address, sizeof(addr));
> - if (!addr || !gas->bit_width)
> + if (!addr)
> return;
>
> mutex_lock(&acpi_ioremap_lock);
> --
> 2.25.1
>
next prev parent reply other threads:[~2022-05-17 17:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-01 17:28 [PATCH] ACPI: OSL: Fix the memory mapping of an ACPI GAS that addresses a data structure james.liu
2022-04-02 7:01 ` kernel test robot
2022-05-17 12:17 ` James Liu [this message]
2022-05-17 17:56 ` James Liu
2022-05-17 18:25 ` Rafael J. Wysocki
2022-05-17 19:00 ` James Liu
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=20220517121743.GA4191@ubuntu-20.04.3 \
--to=james.liu@hpe.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=rafael@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