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
| ||
|
Date: Tue, 26 Jan 2010 13:46:01 -0800 From: "H. Peter Anvin" <hpa@...or.com> To: Pavel Machek <pavel@....cz> CC: "Rafael J. Wysocki" <rjw@...k.pl>, Alan Cox <alan@...rguk.ukuu.org.uk>, Jesse Barnes <jbarnes@...tuousgeek.org>, Len Brown <lenb@...nel.org>, LKML <linux-kernel@...r.kernel.org>, pm list <linux-pm@...ts.linux-foundation.org>, dri-devel@...ts.sourceforge.net, Eric Anholt <eric@...olt.net>, airlied@...ux.ie Subject: Re: [PATCH] PM / i915: Skip kernel VT switch during suspend/resume if KMS is used On 01/26/2010 06:58 AM, Pavel Machek wrote: >> >> That would have to be done using suspend notifiers and should depend on what >> driver actually controls the screen at the moment. And I guess the only case >> in which we actually _need_ to do the kernel VT switch is when the hardware >> is controlled by X and without KMS. > > We need vt switch when display is controlled by userland app directly > accessing hw. It may or may not be X (svgalib anyone?, > gtk-on-framebuffer? qtopia?). > > Ideally, userspace should explicitely tell us. KD_KERNEL_GRAPHICS > console mode? > It seems that the kernel would already know if it's in control of the mode switch, no? If userspace ever takes control and it doesn't already notify the kernel that it is taking over, we would seem to have a much bigger problem... > Plus the switch is needed for any graphics app using fbcon -- I do not > think we actually save the framebuffer over suspend. (This one should > probably be fixed). Quite. -hpa -- 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