mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Maxim Levitsky <maximlevitsky@gmail.com>
Cc: Frederic Weisbecker <fweisbec@gmail.com>,
	Arjan van de Ven <arjan@infradead.org>,
	Dave Jones <davej@redhat.com>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Steven Rostedt <rostedt@goodmis.org>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: RFC: Put printk buffer in video ram
Date: Mon, 23 Nov 2009 19:32:20 +0100	[thread overview]
Message-ID: <20091123183220.GB24482@elte.hu> (raw)
In-Reply-To: <1258938089.3134.22.camel@maxim-laptop>


* Maxim Levitsky <maximlevitsky@gmail.com> wrote:

> On Sun, 2009-11-22 at 14:15 +0200, Maxim Levitsky wrote: 
> > On Sun, 2009-11-22 at 09:25 +0100, Ingo Molnar wrote: 
> > > * Frederic Weisbecker <fweisbec@gmail.com> wrote:
> > > 
> > > > On Sun, Nov 22, 2009 at 04:05:06AM +0200, Maxim Levitsky wrote:
> > > > > After doing some successful debugging by placing printk buffer in video
> > > > > ram, here I publish cleaned version of it.
> > > > > 
> > > > > I discovered that on my system video ram isn't cleared on reboot, and I
> > > > > took advantage of that by placing printk buffer directly there.
> > > > > This allows to capture oopses/panicks almost from everywhere.
> > > > > It is also very simple to setup.
> 
> Few more thoughts:
> 
> First of all, if I implement this as a console driver, I won't be able
> to capture all kernel log, but only from the point I register the
> console.

Adding an early console driver would solve this, right?

There's an earlyprintk=..,keep option that also allows such a console 
driver to be active during normal system operation - that way you could 
get this feature with a single console driver.

> My implementation, also isn't set up very early, but I copy already
> written log to the memory buffer.
> 
> Problem of automatic unregistration isn't a problem, its just a feature,
> I could skip using.
> 
> Secondary, I found out that system ram isn't cleared ether on my
> notebook, however I found out that I can't reserve small memory range
> with 'memmap' kernel parameter. System just panics.
> I used for reference 'memmap=2M$0x60000000'
> My system has 2GB of memory.
> 
> I could reserve the memory same way using the code, but it would
> probably fail in same way. Also I could try early reservations, but I am
> not sure I can reserve _any_ address range. I test this.
> 
> I think that patches to put printk buffer at predefined area in system
> ram were once posted on LKML.

The way to early-reserve memory on x86 is to use find_e820_area() + 
reserve_early().

	Ingo

  reply	other threads:[~2009-11-23 18:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-22  2:05 Maxim Levitsky
2009-11-22  2:32 ` Frederic Weisbecker
2009-11-22  8:25   ` Ingo Molnar
2009-11-22 12:15     ` Maxim Levitsky
2009-11-23  1:01       ` Maxim Levitsky
2009-11-23 18:32         ` Ingo Molnar [this message]
2009-11-23 18:55           ` Chris Friesen
2009-11-23 19:03             ` Arnd Bergmann
2009-11-22 12:07   ` Maxim Levitsky

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=20091123183220.GB24482@elte.hu \
    --to=mingo@elte.hu \
    --cc=akpm@linux-foundation.org \
    --cc=arjan@infradead.org \
    --cc=davej@redhat.com \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maximlevitsky@gmail.com \
    --cc=rostedt@goodmis.org \
    --cc=torvalds@linux-foundation.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®