From: Mel Gorman <mel@csn.ul.ie>
To: Ingo Molnar <mingo@elte.hu>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/4] Add a basic debugging framework for memory initialisation
Date: Tue, 22 Apr 2008 12:21:52 +0100 [thread overview]
Message-ID: <20080422112151.GB30798@csn.ul.ie> (raw)
In-Reply-To: <20080421151405.GI5474@elte.hu>
On (21/04/08 17:14), Ingo Molnar didst pronounce:
>
> * Mel Gorman <mel@csn.ul.ie> wrote:
>
> > +config DEBUG_MEMORY_INIT
> > + bool "Debug memory initialisation"
> > + depends on DEBUG_KERNEL
> > + help
> > + Enable this to turn on debug checks during memory initialisation. By
> > + default, sanity checks will be made on the memory model and
> > + information provided by the architecture. What level of checking
> > + made and verbosity during boot can be set with the
> > + mminit_debug_level= command-line option.
> > +
> > + If unsure, say N
>
> should be "default y" - and perhaps only disable-able on
> CONFIG_EMBEDDED.
Ok, that would be something like the following?
bool "Debug memory initialisation" if DEBUG_KERNEL && EMBEDDED
depends on DEBUG_KERNEL
default !EMBEDDED
This will slow up boot slightly on debug kernels as the additional checks
are made. It'll remain to be seen as to whether this is a problem for people
or not. I doubt it'll be noticed.
> We generally want such bugs to pop up as soon as
> possible, and the sanity checks should only go away if someone
> specifically aims for lowest system footprint.
>
Seems fair and it's the second time this has been suggested (off-list reviewer
again). The only potential gotcha is if a sanity check is introduced that is
itself broken. It should be very obvious when this type of bug occurs though.
> the default loglevel for debug printouts might deserve another debug
> option - but the core checks should always be included, and _errors_
> should always be printed out.
>
I'll replace mminit_debug_level with mminit_loglevel that determines whether
information is printed at KERN_DEBUG or not. This matches what other similar
debug-frameworks are doing. I'll make sure errors always get printed.
Thanks
--
Mel Gorman
Part-time Phd Student Linux Technology Center
University of Limerick IBM Dublin Software Lab
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2008-04-22 11:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-17 0:06 [PATCH 0/4] Verification and debugging of memory initialisation V2 Mel Gorman
2008-04-17 0:06 ` [PATCH 1/4] Add a basic debugging framework for memory initialisation Mel Gorman
2008-04-21 15:14 ` Ingo Molnar
2008-04-22 11:21 ` Mel Gorman [this message]
2008-04-17 0:07 ` [PATCH 2/4] Verify the page links and memory model Mel Gorman
2008-04-17 0:07 ` [PATCH 3/4] Make defencive checks around PFN values registered for memory usage Mel Gorman
2008-04-17 0:07 ` [PATCH 4/4] Print out the zonelists on request for manual verification Mel Gorman
-- strict thread matches above, loose matches on Subject: below --
2008-04-28 19:28 [PATCH 0/4] Verification and debugging of memory initialisation V4 Mel Gorman
2008-04-28 19:28 ` [PATCH 1/4] Add a basic debugging framework for memory initialisation Mel Gorman
2008-04-22 18:31 [PATCH 0/4] Verification and debugging of memory initialisation V3 Mel Gorman
2008-04-22 18:31 ` [PATCH 1/4] Add a basic debugging framework for memory initialisation Mel Gorman
2008-04-26 6:10 ` Andrew Morton
2008-04-28 9:34 ` Mel Gorman
2008-04-16 13:50 [PATCH 0/4] [RFC] Verification and debugging of " Mel Gorman
2008-04-16 13:51 ` [PATCH 1/4] Add a basic debugging framework for " Mel Gorman
2008-04-16 14:04 ` Ingo Molnar
2008-04-16 19:30 ` Mel Gorman
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=20080422112151.GB30798@csn.ul.ie \
--to=mel@csn.ul.ie \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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