lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Mon, 12 Jan 2015 11:39:18 -0500 (EST)
From:	Alan Stern <stern@...land.harvard.edu>
To:	"Rafael J. Wysocki" <rjw@...ysocki.net>
cc:	Linux PCI <linux-pci@...r.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Linux PM list <linux-pm@...r.kernel.org>,
	Bjorn Helgaas <bhelgaas@...gle.com>,
	Aaron Lu <aaron.lu@...el.com>,
	Mika Westerberg <mika.westerberg@...ux.intel.com>
Subject: Re: [RFC][PATCH] PCI / PM: Avoid resuming PCI devices during system
 suspend

On Mon, 12 Jan 2015, Rafael J. Wysocki wrote:

> On Thursday, January 08, 2015 10:51:06 AM Alan Stern wrote:
> > On Thu, 8 Jan 2015, Rafael J. Wysocki wrote:
> > 
> > > From: Rafael J. Wysocki <rafael.j.wysocki@...el.com>
> > > 
> > > Commit f25c0ae2b4c4 (ACPI / PM: Avoid resuming devices in ACPI PM
> > > domain during system suspend) modified the ACPI PM domain's system
> > > suspend callbacks to allow devices attached to it to be left in the
> > > runtime-suspended state during system suspend so as to optimize
> > > the suspend process.
> > > 
> > > This was based on the general mechanism introduced by commit
> > > aae4518b3124 (PM / sleep: Mechanism to avoid resuming runtime-suspended
> > > devices unnecessarily).
> > > 
> > > Extend that approach to PCI devices by modifying the PCI bus type's
> > > ->prepare callback to return 1 for devices that are runtime-suspended
> > > when it is being executed and that are in a suitable power state and
> > > need not be resumed going forward.
> > 
> > Does this correctly handle PCI devices that aren't included in the ACPI
> > tables?  For example, add-on PCI cards?
> 
> Well, it would if it took the case when a device was configured for remote
> wakeup at run time but was not supposed to wakeup the system from sleep into
> account.
> 
> That needs to be checked in pci_dev_keep_suspended() rather than in the platform
> callback to cover all devices.
> 
> Updated patch follows.
> 
> Rafael

This looks better, thank you.

Alan Stern


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ