From: William Lee Irwin III <wli@holomorphy.com>
To: sparclinux@vger.kernel.org
Subject: Re: [sparc32] vm fault code handling
Date: Thu, 23 Dec 2004 03:23:17 +0000 [thread overview]
Message-ID: <20041223032317.GX771@holomorphy.com> (raw)
In-Reply-To: <20041222143113.GT771@holomorphy.com>
On Wed, Dec 22, 2004 at 06:31:13AM -0800, William Lee Irwin III wrote:
>> Convert arch/sparc/mm/fault.c to symbolic fault codes, default to minor
>> faults for unrecognized fault codes. Also treat VM_FAULT_OOM similarly
>> to VM_FAULT_SIGBUS in force_user_fault(), thereby fixing a latent bug.
>>
>> [ ... snip patch ... ]
On Wed, Dec 22, 2004 at 05:38:36PM -0600, Art Haas wrote:
> Here's a slightly modified version of that patch which makes the sparc32
> code more closely match the sparc64 code by setting the default branch
> of the case statement to BUG(). The rest of the patch matched what was
> posted above.
I considered that, flipped a coin, and went with defaulting to minor
faults. Since someone has an opinion (though not necessarily strong)
I'll switch it over to that way.
-- wli
prev parent reply other threads:[~2004-12-23 3:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-22 14:31 [sparc32] vm fault code handling William Lee Irwin III
2004-12-22 23:38 ` Art Haas
2004-12-23 3:23 ` William Lee Irwin III [this message]
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=20041223032317.GX771@holomorphy.com \
--to=wli@holomorphy.com \
--cc=sparclinux@vger.kernel.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.