linux-kernel - Re: Removing sysdevs?

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:	Thu, 03 Jul 2008 08:17:58 +1000
From:	Benjamin Herrenschmidt <benh@...nel.crashing.org>
To:	Andi Kleen <andi@...stfloor.org>
Cc:	Greg KH <greg@...ah.com>, "Rafael J. Wysocki" <rjw@...k.pl>,
	Nathan Lynch <ntl@...ox.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Paul Mackerras <paulus@...ba.org>,
	torvalds@...ux-foundation.org, linux-kernel@...r.kernel.org
Subject: Re: Removing sysdevs?

On Wed, 2008-07-02 at 23:57 +0200, Andi Kleen wrote:
> > The plan is:
> > 	- remaining driver core cleanups to allow for multiple drivers
> > 	  to be bound to individual devices
> > 	- add multiple binding support to the core
> > 	- migrate existing sysdevs to struct device, now that multiple
> > 	  binding is allowed
> > 	- delete sysdev structure
> > 	- profit!
> 
> I hope the sysdev semantics of running with interrupts etc. will be kept?

What "running with interrupts" ? :-) Are you talking specifically about
suspend/resume ? In this case, normal devices also provide irq_off
variants of suspend/resume.

In some areas, those semantics are even a problem for sysdevs. For
example, it's been a pain in the neck for cpufreq on powermac not to be
able to schedule in its suspend routine. Among others...

Cheers,
Ben.


--
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/