All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Al Stone <al.stone@linaro.org>
Cc: "Zheng, Lv" <lv.zheng@intel.com>,
	"Rafael J. Wysocki" <rjw@rjwysocki.net>,
	Olof Johansson <olof@lixom.net>,
	Rob Herring <robherring2@gmail.com>,
	"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
	Linaro Patches <patches@linaro.org>,
	"linaro-kernel@lists.linaro.org" <linaro-kernel@lists.linaro.org>,
	"linaro-acpi@lists.linaro.org" <linaro-acpi@lists.linaro.org>
Subject: Re: [PATCH v2 4/6] ACPI: ARM: exclude DMI calls
Date: Wed, 4 Dec 2013 01:34:30 +0000	[thread overview]
Message-ID: <20131204013430.GA25154@srcf.ucam.org> (raw)
In-Reply-To: <529E85C8.5050805@linaro.org>

On Tue, Dec 03, 2013 at 06:30:48PM -0700, Al Stone wrote:

> I thought I could get this to work, but I am going to have to defer
> to the ACPICA upstream folks.  For the time being, I think that all
> of the architectures that want to use ACPI in either legacy mode or
> in stripped down reduced HW mode will have to use different kernels,
> one for each mode.  I thought there might be enough safety checks to
> allow the kernel to boot in legacy mode and switch into reduced HW at
> boot, but there are not, in my opinion.  I don't see a way to make the
> switch *and* maintain conformance with the spec without significant
> change to ACPICA itself.

Ugh. That needs fixing. There's been a huge amount of work done to 
ensure that x86 only needs a single kernel image for 64-bit, it really 
needs to be runtime. We shouldn't have merged it in this state.

> For example, enforcing that various functions are not allowed while
> in reduced HW mode could be done by a check of the reduced HW flag on
> entry.  If it is set, return the value the function would have returned
> had it been stubbed out for reduced HW mode.  This is simple enough but
> to do so would require modifying at least 29 functions in ACPICA, by my
> count, not something upstream is particularly keen on -- nor am I.  I'd
> rather step back and work with ACPICA over the longer term and see if
> there's some way to get this functionality implemented properly instead
> of trying to bolt it on somehow.

How many of those are calls that we'll actually execute in the HW 
reduced case?

-- 
Matthew Garrett | mjg59@srcf.ucam.org

  reply	other threads:[~2013-12-04  1:34 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-22  0:41 [PATCH v2 0/6] Hardware Reduced Mode cleanup for ACPI al.stone
     [not found] ` < 528F9C65.7010302@linaro.org>
     [not found]   ` < CAOesGMgFBRjO++JSP0ddKKQ2RfG8V4fb97Hd+Oqwixi_Tt7Qwg@mail.gmail.com>
2013-11-22  0:41 ` [PATCH v2 1/6] ACPI: introduce CONFIG_ACPI_REDUCED_HARDWARE to enable this ACPI mode al.stone
2013-11-22  0:41 ` [PATCH v2 2/6] ACPI: bus master reload not supported in reduced HW mode al.stone
2013-11-22  3:06   ` Hanjun Guo
2013-11-27 22:35     ` Al Stone
2013-11-22  0:41 ` [PATCH v2 3/6] ACPI: HW reduced mode does not allow use of the FADT sci_interrupt field al.stone
2013-11-22  0:41 ` [PATCH v2 4/6] ACPI: ARM: exclude DMI calls al.stone
2013-11-22 13:25   ` Rob Herring
2013-11-22 18:03     ` Al Stone
2013-11-22 18:53       ` Olof Johansson
2013-11-22 23:15         ` Rafael J. Wysocki
2013-11-23  0:05           ` Al Stone
2013-11-23 16:38             ` Matthew Garrett
2013-11-25  5:10               ` Zheng, Lv
2013-11-25 15:30                 ` Matthew Garrett
2013-11-25 17:43                   ` Al Stone
2013-11-25 17:45                     ` Matthew Garrett
2013-11-25 18:01                       ` Al Stone
2013-12-04  1:30                         ` Al Stone
2013-12-04  1:34                           ` Matthew Garrett [this message]
2013-12-10 12:45               ` Grant Likely
2013-11-22  0:41 ` [PATCH v2 5/6] ACPI: do not reserve memory regions for some FADT entries in HW reduced mode al.stone
2013-11-22  0:41 ` [PATCH v2 6/6] ACPI: in HW reduced mode, using FADT PM information is not allowed al.stone
2013-11-22 23:18 ` [PATCH v2 0/6] Hardware Reduced Mode cleanup for ACPI Rafael J. Wysocki
2013-11-22 23:33   ` Al Stone

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=20131204013430.GA25154@srcf.ucam.org \
    --to=mjg59@srcf.ucam.org \
    --cc=al.stone@linaro.org \
    --cc=linaro-acpi@lists.linaro.org \
    --cc=linaro-kernel@lists.linaro.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=lv.zheng@intel.com \
    --cc=olof@lixom.net \
    --cc=patches@linaro.org \
    --cc=rjw@rjwysocki.net \
    --cc=robherring2@gmail.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 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.