All of lore.kernel.org
 help / color / mirror / Atom feed
From: Erik Mouw <erik@harddisk-recovery.com>
To: Alexey Dobriyan <adobriyan@openvz.org>
Cc: ak@suse.de, Pavel Emelianov <xemul@openvz.org>,
	devel@openvz.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Print number of oopses in Sysrq-P output
Date: Thu, 18 Jan 2007 18:46:31 +0100	[thread overview]
Message-ID: <20070118174631.GA16489@harddisk-recovery.com> (raw)
In-Reply-To: <20070118170522.GA23679@localhost.sw.ru>

On Thu, Jan 18, 2007 at 08:05:22PM +0300, Alexey Dobriyan wrote:
> From: Pavel Emelianov <xemul@openvz.org>
> 
> Useful in deciding whether said output should be ignored
> in absence of other info. :)
> 
> Signed-off-by: Pavel Emelianov <xemul@openvz.org>
> Signed-off-by: Alexey Dobriyan <adobriyan@openvz.org>
> ---
> 
>  arch/i386/kernel/process.c   |    4 +++-
>  arch/i386/kernel/traps.c     |    2 +-
>  arch/x86_64/kernel/process.c |    6 ++++--
>  arch/x86_64/kernel/traps.c   |    3 ++-
>  4 files changed, 10 insertions(+), 5 deletions(-)

What about the other architectures?

> --- a/arch/i386/kernel/traps.c
> +++ b/arch/i386/kernel/traps.c
> @@ -366,6 +366,7 @@ int is_valid_bugaddr(unsigned long eip)
>  	return ud2 == 0x0b0f;
>  }
>  
> +int die_counter = 0;

Global variables don't have to be initialised at 0. They live in the
.bss segment so they will automatically initialised at 0 and not take
space in the kernel image.


Erik

-- 
+-- Erik Mouw -- www.harddisk-recovery.com -- +31 70 370 12 90 --
| Lab address: Delftechpark 26, 2628 XH, Delft, The Netherlands

  reply	other threads:[~2007-01-18 17:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-18 17:05 [PATCH] Print number of oopses in Sysrq-P output Alexey Dobriyan
2007-01-18 17:46 ` Erik Mouw [this message]
2007-01-18 23:19 ` Andi Kleen
2007-01-19 11:36 ` [Devel] " Kirill Korotaev

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=20070118174631.GA16489@harddisk-recovery.com \
    --to=erik@harddisk-recovery.com \
    --cc=adobriyan@openvz.org \
    --cc=ak@suse.de \
    --cc=devel@openvz.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=xemul@openvz.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.