linux-kernel - Re: [PATCH 2/8] PM: Asynchronous suspend and resume of devices

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]

Message-ID: <Pine.LNX.4.44L0.1001242155410.4189-100000@netrider.rowland.org>
Date:	Sun, 24 Jan 2010 22:12:29 -0500 (EST)
From:	Alan Stern <stern@...land.harvard.edu>
To:	"Rafael J. Wysocki" <rjw@...k.pl>
cc:	LKML <linux-kernel@...r.kernel.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	pm list <linux-pm@...ts.linux-foundation.org>,
	<linux-usb@...r.kernel.org>, Greg KH <gregkh@...e.de>,
	Arjan van de Ven <arjan@...radead.org>,
	Nigel Cunningham <ncunningham@...a.org.au>
Subject: Re: [PATCH 2/8] PM: Asynchronous suspend and resume of devices

On Mon, 25 Jan 2010, Rafael J. Wysocki wrote:

> > I intend to write this code, but merging it will be a little tricky.  
> > You'll have to coordinate with Greg KH.
> 
> OK, I don't think that's a big deal.  I can defer patch 7/8 until that code has
> been merged.

You may have to delay 6/8 as well, since the controllers are PCI
devices.  Writing the new code shouldn't take too long, though.

Is there a good way to iterate through all PCI devices in a particular
slot, or should it be done by going through all PCI devices and
ignoring those in other slots?  Calling pci_get_slot() multiple times
doesn't look very efficient.

> I'll try that, but my mkinitrd automatically puts the USB drivers into
> initramfs.  I guess I'll need to do some research to really verify it. :-)

Then when you install the test kernel, mkinitrd should build a
corresponding initramfs image with the modified drivers, right?  
Otherwise there would be a version mismatch error when the init code
tried to load the old drivers into the new kernel.

If nothing else works, you can simply unload the standard uhci-hcd,
ohci-hcd, and ehci-hcd drivers and then modprobe the modified versions
before starting the hibernation.

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/