public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: William Lee Irwin III <wli@holomorphy.com>
To: Christopher Li <lkml@chrisli.org>
Cc: Gerardo Exequiel Pozzi <vmlinuz386@yahoo.com.ar>,
	Andrew Morton <akpm@osdl.org>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.0-test9-mm4 (only) and vmware
Date: Wed, 19 Nov 2003 18:57:30 -0800	[thread overview]
Message-ID: <20031120025730.GD22764@holomorphy.com> (raw)
In-Reply-To: <20031119234037.GC20840@64m.dyndns.org>

On Wed, Nov 19, 2003 at 06:34:57PM -0800, William Lee Irwin III wrote:
>> I'm going to ruminate on non-fatal methods of complaining loudly.

On Wed, Nov 19, 2003 at 06:40:37PM -0500, Christopher Li wrote:
> SPARSE checker?

I was thinking of teaching the fault handlers to complain about
->nopage() methods returning invalid results in a non-fatal manner,
possibly with code consolidation.

e.g. every arch does:

	switch (handle_mm_fault(...)) {
		case VM_FAULT_MINOR:
			tsk->min_flt++;
			break;
		case VM_FAULT_MAJOR:
			tsk->maj_flt++;
			break;
		case VM_FAULT_SIGBUS:
			goto do_sigbus;
		case VM_FAULT_OOM:
			goto out_of_memory;
		default:
			BUG();
	}

which is vaguely repetitive. It's not immediately clear how to
consolidate gotos, which is where the thought starts happening.

The other part was replacing default: BUG() with something that
complained (e.g. putting print_symbol() to use on the ->nopage()
method) and treating the invalid statuses like OOM, but that's
not really very hard to do (I posted something that did some
crude reporting of that kind already to handle the sound/ bogons).


-- wli

  reply	other threads:[~2003-11-20  2:57 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-19 21:15 2.6.0-test9-mm4 (only) and vmware Gerardo Exequiel Pozzi
2003-11-19 21:38 ` Andrew Morton
2003-11-20  4:15   ` Gerardo Exequiel Pozzi
2003-11-19 22:34 ` Christopher Li
2003-11-20  1:47   ` William Lee Irwin III
2003-11-19 23:22     ` Christopher Li
2003-11-20  2:34       ` William Lee Irwin III
2003-11-19 23:40         ` Christopher Li
2003-11-20  2:57           ` William Lee Irwin III [this message]
2003-11-20 10:03             ` Voicu Liviu
     [not found]               ` <20031120101830.GH22764@holomorphy.com>
2003-11-20 10:23                 ` Voicu Liviu
2003-11-20 10:31                   ` William Lee Irwin III
2003-11-20 10:37                     ` Voicu Liviu
2003-11-20 10:42                       ` William Lee Irwin III
2003-11-20 10:51                         ` Voicu Liviu
2003-11-20 17:20                           ` Christopher Li
2003-11-20 21:38                             ` Jose Luis Domingo Lopez
2003-11-20 21:55                               ` William Lee Irwin III
2003-11-20 22:53                                 ` Jose Luis Domingo Lopez
2003-11-20 22:56                                   ` William Lee Irwin III
2003-11-21 20:10                                     ` Jose Luis Domingo Lopez
2003-11-21 23:08                                       ` Jose Luis Domingo Lopez
2003-11-20  0:21 ` Jose Luis Domingo Lopez
2003-11-20  1:02   ` Andrew Morton
2003-11-20  1:07     ` William Lee Irwin III
2003-11-20  1:12     ` William Lee Irwin III
2003-11-20  1:58       ` Andrew Morton
2003-11-20  2:12         ` William Lee Irwin III
2003-11-19 23:24           ` Christopher Li
2003-11-20  4:39           ` Gerardo Exequiel Pozzi
  -- strict thread matches above, loose matches on Subject: below --
2003-11-20 10:35 Petr Vandrovec

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=20031120025730.GD22764@holomorphy.com \
    --to=wli@holomorphy.com \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkml@chrisli.org \
    --cc=vmlinuz386@yahoo.com.ar \
    /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