From: Blaisorblade <blaisorblade@yahoo.it>
To: user-mode-linux-devel@lists.sourceforge.net
Cc: Andrew Morton <akpm@linux-foundation.org>,
Jeff Dike <jdike@addtoit.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [uml-devel] [PATCH 2/2] UML - Add stack usage monitoring
Date: Wed, 20 Jun 2007 16:18:56 +0200 [thread overview]
Message-ID: <200706201618.56604.blaisorblade@yahoo.it> (raw)
In-Reply-To: <20070619115422.de61abd5.akpm@linux-foundation.org>
[-- Attachment #1: Type: text/plain, Size: 1653 bytes --]
On martedì 19 giugno 2007, Andrew Morton wrote:
> On Tue, 19 Jun 2007 14:42:45 -0400
>
> Jeff Dike <jdike@addtoit.com> wrote:
> > Add a machanism to see how much of a kernel stack is used. This
> > allocates zeroed stacks and sees where the lowest non-zero byte is on
> > process exit. It keeps track of the lowest value and logs values as
> > they get lower.
>
> remind us again why the generic code is unsuitable?
>
> > + for(p = stack; p < end; p++){
> > + if(*p != 0)
> > + if(left < lowest_to_date){
>
> Are there any plans to fix UML coding style?
In Italy we say "habits are hard to die"...
In an (unanswered) thread, titled "[RFC] Auto-fixups for CodingStyle against
major UML violations" from 31/3/2007, also CC'ed to you, Jeff and LKML, I
published a script (reattached here) which integrates with quilt and kbuild
to fix all sources for these violations. It is not indent based, consequently
it does not do any damages that indent would do.
Plus, with just a couple of tiny changes (for substitutions implying the use
of '^'), it can also be run on unified diffs.
The only problem is just coordinating to run it together on a source tree and
on the patch set applying on it. Otherwise the patchset manager would get
hard-to-fix rejects.
In the end: are you interested in this stuff? I'm busy right now but can work
to apply these changes after this thursday (i.e. tomorrow). I'd need to get
Jeff's patchset to fix it.
Please let me know.
Bye!
--
Inform me of my mistakes, so I can add them to my list!
Paolo Giarrusso, aka Blaisorblade
http://www.user-mode-linux.org/~blaisorblade
[-- Attachment #2: do-src-style-fix --]
[-- Type: application/x-shellscript, Size: 2795 bytes --]
next prev parent reply other threads:[~2007-06-20 14:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-19 18:42 Jeff Dike
2007-06-19 18:54 ` Andrew Morton
2007-06-19 19:50 ` Jeff Dike
2007-06-19 19:57 ` Randy Dunlap
2007-06-20 15:37 ` Jeff Dike
2007-06-19 20:14 ` Andrew Morton
2007-06-20 14:06 ` [uml-devel] " Blaisorblade
2007-06-20 15:17 ` Jeff Dike
2007-06-20 20:20 ` Blaisorblade
2007-06-20 18:23 ` Jeff Dike
2007-06-20 14:18 ` Blaisorblade [this message]
2007-06-20 15:20 ` [uml-devel] " Jeff Dike
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=200706201618.56604.blaisorblade@yahoo.it \
--to=blaisorblade@yahoo.it \
--cc=akpm@linux-foundation.org \
--cc=jdike@addtoit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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
Powered by JetHome