http://bugzilla.kernel.org/show_bug.cgi?id=13130
--- Comment #6 from Jesse Barnes <jbar...@virtuousgeek.org> 2009-04-21 15:56:24 --- (In reply to comment #5) > well... _why_ do we want it to work? It's only a debug thing and shouldn't > be needed at all once the driver is finished? Oh not at all; it's also about debugging bad userspace programs that mess with the display but don't crash gracefully (which would automatically restore the display). Maybe they hang or just display a mess and you want your console back. > And if there _is_ a legitimate long-term need for it then it surely should not > be implemented way down > inside one specific driver? It could probably be made drm generic, but so far i915 is the only in-tree driver using the DRM mode setting code. We could factor it out when the radeon stuff lands I guess. > I'm surprised that anyone even found out that sysrq-g exists - I didn't know, > and the chances are good that we'll later steal `g' from you and we won't find > out > for weeks :( Is there a registry or something we should use instead? I saw a few instances of sysrqs being registered in subsystems or arches, but I think I picked one that's free (and somewhat sensible)... > Yes, a schedule_work() thing will probably be OK, although there's a new class > of deadlock around that, so some care will be needed. > > This'll be our fourth sysrq-uses-schedule_work instance (at least). I guess > we > should > add a sysrq_key_op.call_in_process_context and centralise the implementation.. Sounds good. I'll add it to my TODO list. Thanks. -- Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. ------------------------------------------------------------------------------ Stay on top of everything new and different, both inside and around Java (TM) technology - register by April 22, and save $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco. 300 plus technical and hands-on sessions. Register today. Use priority code J9JMT32. http://p.sf.net/sfu/p -- _______________________________________________ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
