From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Hidetoshi Seto <seto.hidetoshi@jp.fujitsu.com>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
linux-pci@vger.kernel.org, Len Brown <lenb@kernel.org>,
ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
linux-pm@lists.linux-foundation.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Jesse Barnes <jbarnes@virtuousgeek.org>
Subject: Re: [RFC][PATCH] PCI / PCIe: Ask BIOS for control of all native services simultaneously
Date: Wed, 28 Jul 2010 12:55:43 +0100 [thread overview]
Message-ID: <20100728115543.GA11697@srcf.ucam.org> (raw)
In-Reply-To: <4C4FA663.9090204@jp.fujitsu.com>
On Wed, Jul 28, 2010 at 12:39:15PM +0900, Hidetoshi Seto wrote:
> Hi,
>
> (2010/07/25 8:05), Rafael J. Wysocki wrote:
> > It turns out that asking ACPI BIOS, through _OSC, for control of each
> > PCIe port native service individually sometimes confuses the BIOS if
> > one sevice is requested while the others are not (eg. requesting
> > control of the native PCIe PME without requesting control of the
> > native PCIe hot-plug at the same time leads to interrupt storms on
> > some systems).
>
> Then why not invent quirks or something for such systems?
Because we'll have a quirk table with dozens of entries and it won't be
comprehensive.
> IMHO it sounds like a BIOS bug since it should grant PME control to
> OS only when both of PME and pciehp (plus PCIe caps) are requested
> at same time.
We're in the business of writing an operating system that's able to
drive the hardware that exists, not just the hardware that follows the
specs completely. It's implausible that we'll get every broken BIOS
fixed, and it's implausible that we'll be able to work out a list of
every broken computer.
--
Matthew Garrett | mjg59@srcf.ucam.org
prev parent reply other threads:[~2010-07-28 11:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-24 23:05 [RFC][PATCH] PCI / PCIe: Ask BIOS for control of all native services simultaneously Rafael J. Wysocki
2010-07-25 12:23 ` [RFC][PATCH] PCI / PCIe: Ask BIOS for control of all native services at once Rafael J. Wysocki
2010-07-27 0:43 ` [RFC][PATCH] PCI / PCIe: Ask BIOS for control of all native services simultaneously Kenji Kaneshige
2010-07-27 17:18 ` Matthew Garrett
2010-07-27 18:42 ` Rafael J. Wysocki
2010-07-27 18:56 ` Matthew Garrett
2010-07-27 22:55 ` [RFC][PATCH] PCI / PCIe: Ask BIOS for control of all native services at once (v2) Rafael J. Wysocki
2010-07-28 10:59 ` [RFC][PATCH] PCI / PCIe: Ask BIOS for control of all native services at once (v3) Rafael J. Wysocki
2010-07-27 18:31 ` [RFC][PATCH] PCI / PCIe: Ask BIOS for control of all native services simultaneously Rafael J. Wysocki
2010-07-28 3:39 ` Hidetoshi Seto
2010-07-28 10:49 ` Rafael J. Wysocki
2010-07-28 11:55 ` Matthew Garrett [this message]
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=20100728115543.GA11697@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=jbarnes@virtuousgeek.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=rjw@sisk.pl \
--cc=seto.hidetoshi@jp.fujitsu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox