linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: huang ying <huang.ying.caritas@gmail.com>
Cc: "Yan, Zheng" <zheng.z.yan@intel.com>,
	bhelgaas@google.com, linux-kernel@vger.kernel.org,
	linux-pci@vger.kernel.org, linux-pm@vger.kernel.org,
	Lin Ming <ming.m.lin@intel.com>, Zhang Rui <rui.zhang@intel.com>,
	ACPI Devel Mailing List <linux-acpi@vger.kernel.org>
Subject: Re: [RFC PATCH] PCIe: Add PCIe runtime D3cold support
Date: Wed, 18 Apr 2012 21:51:33 +0200	[thread overview]
Message-ID: <201204182151.33854.rjw@sisk.pl> (raw)
In-Reply-To: <CAC=cRTN2QHWu1aD4AGyTB=wuHW-0oyLreZ2QiWSMvf_Ne_Nz0g@mail.gmail.com>

On Wednesday, April 18, 2012, huang ying wrote:
> On Wed, Apr 18, 2012 at 4:20 AM, Rafael J. Wysocki <rjw@sisk.pl> wrote:
> > On Tuesday, April 17, 2012, huang ying wrote:
> >> On Tue, Apr 17, 2012 at 1:07 AM, Rafael J. Wysocki <rjw@sisk.pl> wrote:
> >> > Moreover, I really don't think it's a good idea to put PCI Express ports into
> >> > low-power states in general.  It might work on your platform, whatever it is,
> >> > but that doesn't mean it's going to work on every PCI Express system out
> >> > there.  I actually know of a number of such systems where it surely won't
> >> > work at all.
> >>
> >> The runtime PM support for PCIe port is not turned on by default, we need
> >>
> >> # echo auto > /sys/devices/pcixxxx:xx/<pci id>/power/control
> >>
> >> to turn on it.  And we will turn on it on system it works.  Is this sufficient?
> >
> > No, it is not.  In some cases it shouldn't be enabled at all for PCI Express
> > ports, as far as I can say, so to be on the safe side we should only enable it
> > on platforms where PCI Express ports are known to work correctly with runtime PM.
> 
> Sorry, I did not catch your idea exactly.  I think disable it by
> default and enable it by sysfs interface is what you suggested, isn't
> it?

No, it isn't.  User space shouldn't be able to enable functionality that's
going to break on a subset of systems.

> Or you suggest something like "white list"?

Yes, something like this.

Thanks,
Rafael

  reply	other threads:[~2012-04-18 19:51 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-13  2:35 [RFC PATCH] PCIe: Add PCIe runtime D3cold support Yan, Zheng
2012-04-13  6:06 ` Alex He
2012-04-13  6:28   ` Yan, Zheng
2012-04-16  8:15   ` huang ying
2012-04-13 19:41 ` Rafael J. Wysocki
2012-04-16  0:48   ` Lin Ming
2012-04-16 16:26     ` Rafael J. Wysocki
2012-04-16  2:23   ` Yan, Zheng
2012-04-16 17:07     ` Rafael J. Wysocki
2012-04-17  2:07       ` huang ying
2012-04-17 20:20         ` Rafael J. Wysocki
2012-04-18  1:19           ` huang ying
2012-04-18 19:51             ` Rafael J. Wysocki [this message]
2012-04-17  2:12       ` Yan, Zheng
2012-04-17  5:32         ` huang ying
2012-04-17 20:43           ` Rafael J. Wysocki
2012-04-18  1:22             ` huang ying
2012-04-18 19:52               ` Rafael J. Wysocki
2012-04-17 20:35         ` Rafael J. Wysocki
2012-04-16  7:49   ` Yan, Zheng
2012-04-16 21:11     ` Rafael J. Wysocki
2012-04-16  8:58   ` huang ying
2012-04-16 21:30     ` Rafael J. Wysocki
2012-04-17  2:02       ` huang ying
2012-04-17 21:03         ` Rafael J. Wysocki
2012-04-18  1:45           ` huang ying
2012-04-18 21:00             ` Rafael J. Wysocki
2012-04-19  2:47               ` huang ying
2012-04-19 12:31                 ` Rafael J. Wysocki
2012-04-20  0:48                   ` huang ying
2012-04-17  5:13       ` huang ying
2012-04-17 21:10         ` Rafael J. Wysocki
2012-04-18  2:01           ` huang ying
2012-04-18 20:51             ` Rafael J. Wysocki
2012-04-19  2:08               ` huang ying
2012-04-19 12:36                 ` Rafael J. Wysocki
2012-04-20  0:53                   ` huang ying

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=201204182151.33854.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=bhelgaas@google.com \
    --cc=huang.ying.caritas@gmail.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=ming.m.lin@intel.com \
    --cc=rui.zhang@intel.com \
    --cc=zheng.z.yan@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 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).