public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Len Brown <lenb@kernel.org>
Cc: linux-acpi@vger.kernel.org
Subject: Re: [PATCH/RFC] ACPICA: disable ACPI 2.0 _GTS/_BFS support
Date: Fri, 19 Dec 2008 18:48:49 +0100	[thread overview]
Message-ID: <200812191848.49928.rjw@sisk.pl> (raw)
In-Reply-To: <alpine.LFD.2.00.0812190421140.1988@localhost.localdomain>

On Friday, 19 of December 2008, Len Brown wrote:
> From: Len Brown <len.brown@intel.com>
> Organization: Intel Open Source Technology Center
> 
> ACPI 2.0 defined two new methods in the suspend/resume sequence,
> _GTS (Going to Sleep) and _BFS (Back from Sleep)
> 
> They are optional methods, but if the BIOS supplies them,
> the OS is supposed to evaluate them immediately before
> writing the register to sleep, and immediately after waking up --
> a time when interrupts are disabled.
> 
> The spec says that they must be self-contained
> methods, not calling any other methods, perhaps
> because that they are run under unique conditions?
> 
> These methodds are evaluated in Linux by
> acpi_evaluate_object(), which always kmalloc's
> a return structure to conserve stack space.
> But kmalloc with interrupts off is problematic --
> do we really want to insist on GFP_ATOMIC here?

Well, I think we should.

Alternatively, we can keep a preallocated buffer for this purpose.

> Now, several years after ACPI 2.0 was released,
> we have yet to observe a single implementation of
> _GTS/_BFS in the field -- suggesting that they will
> never actually be deployed.
> 
> So lets keep Linux simple by removing this
> theoretical support for _GTS/_BFS, the only
> AML methods that mandated being evaluated
> with interrupts disabled.

I'm not sure if I agree with this approach.

My opinion is that we should be able to execute AML code with interrupts
disabled and there should be means to do that.

The entire irqrouter_resume() thing requires us to evaluate AML with interrupts
disabled and in that particular case it also really _makes_ _sense_.

So, IMO dropping _GTS/_BFS doesn't really buy us anything.

Thanks,
Rafael

  parent reply	other threads:[~2008-12-19 17:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-19  9:23 [PATCH/RFC] ACPICA: disable ACPI 2.0 _GTS/_BFS support Len Brown
2008-12-19 16:39 ` Bjorn Helgaas
2008-12-31  0:16   ` Len Brown
2008-12-19 17:48 ` Rafael J. Wysocki [this message]
2008-12-22  1:42 ` Zhao Yakui

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=200812191848.49928.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.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