From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Len Brown <lenb@kernel.org>,
ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
Matthew Garrett <mjg59@srcf.ucam.org>,
linux-pm@lists.linux-foundation.org,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org
Subject: Re: [PATCH] PCI / PM: Do not use native PCIe PME by default
Date: Fri, 18 Jun 2010 09:37:01 -0700 [thread overview]
Message-ID: <20100618093701.681dc238@virtuousgeek.org> (raw)
In-Reply-To: <201006181704.22550.rjw@sisk.pl>
On Fri, 18 Jun 2010 17:04:22 +0200
"Rafael J. Wysocki" <rjw@sisk.pl> wrote:
> From: Rafael J. Wysocki <rjw@sisk.pl>
>
> Commit c7f486567c1d0acd2e4166c47069835b9f75e77b
> (PCI PM: PCIe PME root port service driver) causes the native PCIe
> PME signaling to be used by default, if the BIOS allows the kernel to
> control the standard configuration registers of PCIe root ports.
> However, the native PCIe PME is coupled to the native PCIe hotplug
> and calling pcie_pme_acpi_setup() makes some BIOSes expect that
> the native PCIe hotplug will be used as well. That, in turn, causes
> problems to appear on systems where the PCIe hotplug driver is not
> loaded. The usual symptom, as reported by Jaroslav Kameník and
> others, is that the ACPI GPE associated with PCIe hotplug keeps
> firing continuously causing kacpid to take substantial percentage
> of CPU time.
>
> To work around this issue, change the default so that the native
> PCIe PME signaling is only used if directly requested with the help
> of the pcie_pme= command line switch.
>
> Fixes https://bugzilla.kernel.org/show_bug.cgi?id=15924 , which is
> a listed regression from 2.6.33.
>
> Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
> Reported-by: Jaroslav Kameník <jaroslav@kamenik.cz>
> Tested-by: Antoni Grzymala <antekgrzymala@gmail.com>
> ---
Applied to my for-linus tree, thanks.
--
Jesse Barnes, Intel Open Source Technology Center
prev parent reply other threads:[~2010-06-18 16:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-18 15:04 [PATCH] PCI / PM: Do not use native PCIe PME by default Rafael J. Wysocki
2010-06-18 16:37 ` Jesse Barnes [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=20100618093701.681dc238@virtuousgeek.org \
--to=jbarnes@virtuousgeek.org \
--cc=akpm@linux-foundation.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=mjg59@srcf.ucam.org \
--cc=rjw@sisk.pl \
/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;
as well as URLs for NNTP newsgroup(s).