[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <48be541f-bc28-b7e1-3b5b-6ac1cbe62150@suse.com>
Date: Fri, 8 Dec 2017 12:14:45 +0100
From: Juergen Gross <jgross@...e.com>
To: Ingo Molnar <mingo@...nel.org>
Cc: linux-kernel@...r.kernel.org, xen-devel@...ts.xenproject.org,
x86@...nel.org, boris.ostrovsky@...cle.com, hpa@...or.com,
tglx@...utronix.de, mingo@...hat.com, corbet@....net,
rjw@...ysocki.net, lenb@...nel.org, linux-acpi@...r.kernel.org
Subject: Re: [PATCH v2 2/3] x86/acpi: take rsdp address for boot params if
available
On 08/12/17 08:05, Ingo Molnar wrote:
>
> * Juergen Gross <jgross@...e.com> wrote:
...
> acpi_physical_address acpi_arch_get_root_pointer(void)
> {
> return boot_params.hdr.acpi_rsdp_addr;
> }
>
> 4)
>
> Add this to arch/x86/include/asm/acpi.h:
>
> extern acpi_physical_address acpi_arch_get_root_pointer(void);
Uuh, this leads to problems for files including <asm/acpi.h> directly:
acpi_physical_address won't be defined, and including <acpi/actypes.h>
from arch/x86/include/asm/acpi.h will lead to:
#error unknown ACPI_MACHINE_WIDTH
This can only be avoided by including <linux/acpi.h> from <asm/acpi.h>
which seems to be the wrong layering.
So I could:
a) modify the sources including <asm/acpi.h> to use <linux/acpi.h>
instead
b) don't use acpi_physical_address but either u64 or unsigned long.
c) ?
What would be your preference?
Juergen
Powered by blists - more mailing lists