mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Theodore Ts'o" <tytso@mit.edu>
To: Jason Wessel <jason.wessel@windriver.com>,
	Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: linux-kernel@vger.kernel.org
Subject: Hints about using the prototype kms/kdb/kgdb integration?
Date: Sat, 03 Oct 2009 12:13:00 -0400	[thread overview]
Message-ID: <E1Mu7EC-0007g8-Jk@closure.thunk.org> (raw)

Hey Jason, Jesse,

I was very much interested in using the kgdb/kdb integration that you
had demo'ed at the Plumber's Conference.   I know that this stuff is
still under development, so the documentation is rather scant.

According to http://kgdb.wiki.kernel.org, the demo at Plumber's
Conference used "kdb_prototype8 from the kgdb git repository".
Unfortunately, I couldn't find kdb_prototype8; I did find
kdb_prototype7, and a newer branch labelled "for_jesse".  The two
branches seemed largely identical in terms of the intent of the patches,
and for_jesse seemed more recent, so I used the latter.

It looked like the magic to get things working was:

   echo kms,kbd > /sys/module/kgdboc/parameters/kgdboc

However, I wasn't able to make kms work.  In fact, looking at the
sources, it's not clear that it would work at all, since
kgdboc_pre_exp_handler() requires that dbg_kms_console_core be set, and
the only thing which sets it is dbg_kms_console_ops_register() --- and I
couldn't find anything that actually calls
dbg_kms_console_ops_register().

Am I missing something?   Is there a branch that I should be using
instead of kdb_prototype7 or for_jesse?

Thanks!!

						- Ted

                 reply	other threads:[~2009-10-03 16:13 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=E1Mu7EC-0007g8-Jk@closure.thunk.org \
    --to=tytso@mit.edu \
    --cc=jason.wessel@windriver.com \
    --cc=jbarnes@virtuousgeek.org \
    --cc=linux-kernel@vger.kernel.org \
    /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®