From: Catalin Marinas <catalin.marinas@arm.com>
To: Al Stone <ahs3@redhat.com>
Cc: Arnd Bergmann <arnd@arndb.de>,
linaro-kernel <linaro-kernel@lists.linaro.org>,
"al.stone@linaro.org" <al.stone@linaro.org>,
"patches@linaro.org" <patches@linaro.org>,
"linaro-acpi@lists.linaro.org" <linaro-acpi@lists.linaro.org>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
Hanjun Guo <hanjun.guo@linaro.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v5 1/5] ACPI: introduce CONFIG_ACPI_REDUCED_HARDWARE_ONLY to enforce this ACPI mode
Date: Fri, 10 Jan 2014 10:37:58 +0000 [thread overview]
Message-ID: <20140110103757.GC925@arm.com> (raw)
In-Reply-To: <52CF1297.9030306@redhat.com>
On Thu, Jan 09, 2014 at 09:20:23PM +0000, Al Stone wrote:
> On 01/09/2014 10:38 AM, Catalin Marinas wrote:
> > On 8 January 2014 12:46, Arnd Bergmann <arnd@arndb.de> wrote:
> >> On Wednesday 08 January 2014, al.stone@linaro.org wrote:
> >>> Even though support for X86 in hardware reduced mode is possible, it
> >>> is NOT enabled. Extensive effort has gone into the Linux kernel so that
> >>> there is a single kernel image than can run on all x86 hardware; the kernel
> >>> changes run-time behavior to adapt to the hardware being used. This is not
> >>> currently possible with the existing ACPICA infrastructure but only presents
> >>> a problem on achitectures supporting both hardware-reduced and legacy modes
> >>> of ACPI -- i.e., on x86 only.
> >>
> >> Not sure about the logic here: While it's certainly possible to build a kernel
> >> that runs on all x86 machines, it's also possible to build one that only
> >> runs on some of them when some basic options are turned off. I don't see
> >> any difference between that and what we have on ARM64 or the multiplatform
> >> subset of ARM32.
> >
> > Would we ever need !CONFIG_ACPI_REDUCED_HARDWARE_ONLY on ARM or ARM64?
> > If not, we could even make this always on for these archs.
> >
>
> Not that I know of -- and I would hope not. This mode is so much
> more straightforward that it makes no sense to me to do anything
> but reduced HW if you have the choice.
Thanks for clarifying.
> I assume you were thinking of something like this in the arch Kconfig
> file:
>
> config ARM64
> ....
> select ACPI_REDUCED_HARDWARE_ONLY if ACPI
> ...
>
> But, do let me know if you had something else in mind. I think it does
> make sense to add so I'll put this in the next version.
The change makes sense but I think it should come with the patches for
ACPI support on arm64 rather than your hw-reduced patches.
--
Catalin
WARNING: multiple messages have this Message-ID (diff)
From: catalin.marinas@arm.com (Catalin Marinas)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v5 1/5] ACPI: introduce CONFIG_ACPI_REDUCED_HARDWARE_ONLY to enforce this ACPI mode
Date: Fri, 10 Jan 2014 10:37:58 +0000 [thread overview]
Message-ID: <20140110103757.GC925@arm.com> (raw)
In-Reply-To: <52CF1297.9030306@redhat.com>
On Thu, Jan 09, 2014 at 09:20:23PM +0000, Al Stone wrote:
> On 01/09/2014 10:38 AM, Catalin Marinas wrote:
> > On 8 January 2014 12:46, Arnd Bergmann <arnd@arndb.de> wrote:
> >> On Wednesday 08 January 2014, al.stone at linaro.org wrote:
> >>> Even though support for X86 in hardware reduced mode is possible, it
> >>> is NOT enabled. Extensive effort has gone into the Linux kernel so that
> >>> there is a single kernel image than can run on all x86 hardware; the kernel
> >>> changes run-time behavior to adapt to the hardware being used. This is not
> >>> currently possible with the existing ACPICA infrastructure but only presents
> >>> a problem on achitectures supporting both hardware-reduced and legacy modes
> >>> of ACPI -- i.e., on x86 only.
> >>
> >> Not sure about the logic here: While it's certainly possible to build a kernel
> >> that runs on all x86 machines, it's also possible to build one that only
> >> runs on some of them when some basic options are turned off. I don't see
> >> any difference between that and what we have on ARM64 or the multiplatform
> >> subset of ARM32.
> >
> > Would we ever need !CONFIG_ACPI_REDUCED_HARDWARE_ONLY on ARM or ARM64?
> > If not, we could even make this always on for these archs.
> >
>
> Not that I know of -- and I would hope not. This mode is so much
> more straightforward that it makes no sense to me to do anything
> but reduced HW if you have the choice.
Thanks for clarifying.
> I assume you were thinking of something like this in the arch Kconfig
> file:
>
> config ARM64
> ....
> select ACPI_REDUCED_HARDWARE_ONLY if ACPI
> ...
>
> But, do let me know if you had something else in mind. I think it does
> make sense to add so I'll put this in the next version.
The change makes sense but I think it should come with the patches for
ACPI support on arm64 rather than your hw-reduced patches.
--
Catalin
next prev parent reply other threads:[~2014-01-10 10:38 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-08 0:46 [PATCH v5 0/5] Hardware Reduced Mode Cleanup for ACPI al.stone
2014-01-08 0:46 ` al.stone at linaro.org
2014-01-08 0:46 ` [PATCH v5 1/5] ACPI: introduce CONFIG_ACPI_REDUCED_HARDWARE_ONLY to enforce this ACPI mode al.stone
2014-01-08 0:46 ` al.stone at linaro.org
2014-01-08 12:46 ` Arnd Bergmann
2014-01-08 12:46 ` Arnd Bergmann
2014-01-08 23:55 ` Al Stone
2014-01-08 23:55 ` Al Stone
2014-01-09 17:38 ` Catalin Marinas
2014-01-09 17:38 ` Catalin Marinas
2014-01-09 21:20 ` Al Stone
2014-01-09 21:20 ` Al Stone
2014-01-10 10:37 ` Catalin Marinas [this message]
2014-01-10 10:37 ` Catalin Marinas
2014-01-10 17:12 ` Al Stone
2014-01-10 17:12 ` Al Stone
2014-01-08 0:46 ` [PATCH v5 2/5] ACPI: bus master reload not supported in reduced HW mode al.stone
2014-01-08 0:46 ` al.stone at linaro.org
2014-01-08 0:46 ` [PATCH v5 3/5] ACPI: HW reduced mode does not allow use of the FADT sci_interrupt field al.stone
2014-01-08 0:46 ` al.stone at linaro.org
2014-01-08 0:46 ` [PATCH v5 4/5] ACPI: in HW reduced mode, using FADT PM information is not allowed al.stone
2014-01-08 0:46 ` al.stone at linaro.org
2014-01-08 0:46 ` [PATCH v5 5/5] ACPI: do not map/unmap memory regions for FADT entries in reduced HW mode al.stone
2014-01-08 0:46 ` al.stone at linaro.org
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=20140110103757.GC925@arm.com \
--to=catalin.marinas@arm.com \
--cc=ahs3@redhat.com \
--cc=al.stone@linaro.org \
--cc=arnd@arndb.de \
--cc=hanjun.guo@linaro.org \
--cc=linaro-acpi@lists.linaro.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=patches@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.