public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jason Wessel <jason.wessel@windriver.com>
To: Mike Travis <travis@sgi.com>
Cc: Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Andrew Morton <akpm@linux-foundation.org>,
	<kgdb-bugreport@lists.sourceforge.net>, <x86@kernel.org>,
	<linux-kernel@vger.kernel.org>, Tim Bird <tim.bird@am.sony.com>
Subject: Re: [PATCH 03/15] KDB: up the default LINES value
Date: Mon, 25 Mar 2013 16:22:34 -0500	[thread overview]
Message-ID: <5150C01A.3030602@windriver.com> (raw)
In-Reply-To: <20130325185007.776886654@gulag1.americas.sgi.com>

On 03/25/2013 01:50 PM, Mike Travis wrote:
> Currently the default for the # of lines displayed by the KDB pager
> is 24.  This does not allow all of the lines for the entry messages,
> reg dump and process trace.  Increase it to something more reasonable.
> 


Unfortunately this is something that breaks compatibility with the
standard VGA console, so this patch will not be merged.

Is it the case that your hardware specifies how many lines and columns
there are in the display?  We have some hooks into the console VT code
to properly detect this but perhaps something is wrong there, or it is
only called in the KMS (kernel mode setting case).  Example:
drivers/tty/vt/vt.c - look at con_debug_enter()

Another option might be to add a variable which allows you to change
the default at compile time, but I would prefer to get the auto detect
code working properly if it is an option.

Jason.



> Cc: Tim Bird <tim.bird@am.sony.com>
> Reviewed-by: Dimitri Sivanich <sivanich@sgi.com>
> Signed-off-by: Mike Travis <travis@sgi.com>
> ---
>  kernel/debug/kdb/kdb_io.c |    2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> --- linux.orig/kernel/debug/kdb/kdb_io.c
> +++ linux/kernel/debug/kdb/kdb_io.c
> @@ -586,7 +586,7 @@ int vkdb_printf(const char *fmt, va_list
>  
>  	diag = kdbgetintenv("LINES", &linecount);
>  	if (diag || linecount <= 1)
> -		linecount = 24;
> +		linecount = 60;
>  
>  	diag = kdbgetintenv("COLUMNS", &colcount);
>  	if (diag || colcount <= 1)
> 
> -- 
> 


  reply	other threads:[~2013-03-25 21:23 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-25 18:50 [PATCH 00/15] x86/UV/KDB/NMI: Updates for NMI/KDB handler for SGI UV Mike Travis
2013-03-25 18:50 ` [PATCH 01/15] KDB: fix the interrupt of the KDB btc command Mike Travis
2013-03-25 21:11   ` Jason Wessel
2013-03-25 18:50 ` [PATCH 02/15] KDB: fix errant character in KDB show regs Mike Travis
2013-03-25 18:50 ` [PATCH 03/15] KDB: up the default LINES value Mike Travis
2013-03-25 21:22   ` Jason Wessel [this message]
2013-03-25 21:31     ` Mike Travis
2013-03-25 18:50 ` [PATCH 04/15] KDB: allow KDB modules to be external modules Mike Travis
2013-03-25 18:50 ` [PATCH 05/15] KDB: add more exports for supporting KDB modules v2 Mike Travis
2013-03-26  2:38   ` Eric W. Biederman
2013-03-26  4:19     ` Mike Travis
2013-03-25 18:50 ` [PATCH 06/15] KDB: consolidate KDB grep code Mike Travis
2013-03-25 18:50 ` [PATCH 07/15] KDB: clean up KDB grep code, add some options Mike Travis
2013-03-25 18:50 ` [PATCH 08/15] KDB: Restore call to kdump from KDB Mike Travis
2013-03-25 18:50 ` [PATCH 09/15] KDB: Add pshelp command Mike Travis
2013-03-25 18:50 ` [PATCH 10/15] KGDB/KDB: add support for external NMI handler to call KGDB/KDB Mike Travis
2013-03-25 18:50 ` [PATCH 11/15] KDB: add new system NMI entry code to KDB Mike Travis
2013-03-25 18:50 ` [PATCH 12/15] x86/UV: Move NMI support Mike Travis
2013-03-25 18:50 ` [PATCH 13/15] x86/UV: Add uvtrace support Mike Travis
2013-03-25 18:50 ` [PATCH 14/15] x86/UV: Update UV support for external NMI signals Mike Travis
2013-03-25 18:50 ` [PATCH 15/15] x86/UV: Add call to KGDB/KDB from NMI handler Mike Travis

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=5150C01A.3030602@windriver.com \
    --to=jason.wessel@windriver.com \
    --cc=akpm@linux-foundation.org \
    --cc=hpa@zytor.com \
    --cc=kgdb-bugreport@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=tim.bird@am.sony.com \
    --cc=travis@sgi.com \
    --cc=x86@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