From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Huang Ying <ying.huang@intel.com>
Cc: Len Brown <lenb@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Andi Kleen <andi@firstfloor.org>,
"Luck, Tony" <tony.luck@intel.com>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>
Subject: Re: [PATCH] ACPI, APEI, Add APEI _OSC support
Date: Thu, 16 Jun 2011 02:57:36 +0100 [thread overview]
Message-ID: <20110616015736.GA32533@srcf.ucam.org> (raw)
In-Reply-To: <4DF962AE.60204@intel.com>
On Thu, Jun 16, 2011 at 09:55:58AM +0800, Huang Ying wrote:
> On 06/16/2011 09:38 AM, Matthew Garrett wrote:
> > I think we probably need to make the HEST decision early, and use that
> > to decide how to make the generic call. Our experience has been that
> > many firmware vendors only expect _OSC to be called once with any given
> > UUID - multiple calls can result in unexpected behaviour.
>
> acpi_bus_osc_support is called via subsys_initcall. It is a little hard
> to do all checking before that. Is it possible to call
> acpi_bus_osc_support later?
Yeah, this is going to be a problem. We have the HEST available at this
point so we ought to be able to parse it, though. I'll take a look
tomorrow.
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2011-06-16 1:57 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-25 6:05 [PATCH] ACPI, APEI, Add APEI _OSC support Huang Ying
2011-06-13 14:50 ` Don Zickus
2011-06-14 6:33 ` Chen Gong
2011-06-14 6:33 ` Chen Gong
2011-06-14 12:11 ` Don Zickus
2011-06-14 14:52 ` Matthew Garrett
2011-06-15 3:53 ` Huang Ying
2011-06-15 12:17 ` Matthew Garrett
2011-06-16 0:40 ` Huang Ying
2011-06-16 1:38 ` Matthew Garrett
2011-06-16 1:55 ` Huang Ying
2011-06-16 1:57 ` Matthew Garrett [this message]
2011-06-17 0:57 ` Huang Ying
2011-06-17 1:34 ` Matthew Garrett
2011-06-17 1:40 ` Huang Ying
2011-06-17 1:42 ` Matthew Garrett
2011-06-17 1:53 ` Huang Ying
2011-06-16 9:00 ` Rafael J. Wysocki
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=20110616015736.GA32533@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=andi@firstfloor.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tony.luck@intel.com \
--cc=ying.huang@intel.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.