From: Jason Wessel <jason.wessel@windriver.com>
To: linux-kernel@vger.kernel.org
Cc: kgdb-bugreport@lists.sourceforge.net, mingo@elte.hu
Subject: [PATCH 0/7] kms + kgdb & kdb proposed merge for 2.6.34
Date: Fri, 12 Feb 2010 16:36:21 -0600 [thread overview]
Message-ID: <1266014188-29505-1-git-send-email-jason.wessel@windriver.com> (raw)
Patch set 2 of 3 - The kdb / kgdb merge
This patch set stacks on top of the kgdb / kdb patches and focuses on
further extending kdb to accommodate atomic kernel mode setting (kms).
At the moment only the Intel i915 class video devices are supported,
but the API is generic and would allow for other kms based drivers to
enable atomic mode setting.
The final patch in the series would be omitted from any pull request
as it is still a work in progress, showing the remaining points that do
not have a safe mechanism to work atomically to change the display
context in order to view the kernel debugger shell. At least it
provides a nice proof of concept.
You can find the development branch for this here:
http://git.kernel.org/?p=linux/kernel/git/jwessel/linux-2.6-kgdb.git;a=shortlog;h=kms-merge
Thanks,
Jason.
---
Jason Wessel (6):
kgdboc,debug_core: Add call backs to allow kernel mode switching
kms,kdb: Force unblank a console device
i915: when kgdb is active display compression should be off
drm_fb_helper: Preserve capability to use atomic kms
kgdb,docs: Update the kgdb docs to include kms
RFC,HACK,EXPERIMENTAL,drm,i915 - atomic mutex HACKS
Jesse Barnes (1):
drm: add KGDB/KDB support Add support for KDB entry/exit.
Documentation/DocBook/kgdb.tmpl | 82 ++++++++++++++++++++++---
Documentation/kernel-parameters.txt | 9 ++-
drivers/gpu/drm/drm_fb_helper.c | 93 +++++++++++++++++++++++++--
drivers/gpu/drm/i915/intel_display.c | 114 ++++++++++++++++++++++++++++++++--
drivers/serial/kgdboc.c | 27 ++++++++
drivers/video/console/fbcon.c | 7 ++
include/drm/drm_crtc_helper.h | 2 +
include/drm/drm_fb_helper.h | 4 +
include/linux/kgdb.h | 38 +++++++++++
kernel/debug/Makefile | 1 +
kernel/debug/debug_core.c | 23 +++++++
kernel/debug/kms_hooks.c | 62 ++++++++++++++++++
12 files changed, 438 insertions(+), 24 deletions(-)
create mode 100644 kernel/debug/kms_hooks.c
next reply other threads:[~2010-02-12 22:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-12 22:36 Jason Wessel [this message]
2010-02-12 22:36 ` [PATCH 1/7] kgdboc,debug_core: Add call backs to allow kernel mode switching Jason Wessel
2010-02-25 16:37 ` Jesse Barnes
2010-02-12 22:36 ` [PATCH 2/7] drm: add KGDB/KDB support Add support for KDB entry/exit Jason Wessel
2010-02-12 22:36 ` [PATCH 3/7] kms,kdb: Force unblank a console device Jason Wessel
2010-02-25 16:39 ` Jesse Barnes
2010-02-12 22:36 ` [PATCH 4/7] i915: when kgdb is active display compression should be off Jason Wessel
2010-02-12 22:36 ` [PATCH 5/7] drm_fb_helper: Preserve capability to use atomic kms Jason Wessel
2010-02-12 22:36 ` [PATCH 6/7] kgdb,docs: Update the kgdb docs to include kms Jason Wessel
2010-02-12 23:05 ` Randy Dunlap
2010-02-17 22:01 ` [Kgdb-bugreport] " Jason Wessel
2010-02-12 22:36 ` [PATCH 7/7] RFC,HACK,EXPERIMENTAL,drm,i915 - atomic mutex HACKS Jason Wessel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1266014188-29505-1-git-send-email-jason.wessel@windriver.com \
--to=jason.wessel@windriver.com \
--cc=kgdb-bugreport@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®