From: William Lee Irwin III <wli@holomorphy.com>
To: sparclinux@vger.kernel.org
Subject: Re: Current BK kernel error
Date: Wed, 12 Jan 2005 05:38:49 +0000 [thread overview]
Message-ID: <20050112053849.GE14443@holomorphy.com> (raw)
In-Reply-To: <20050111143605.GC4514@artsapartment.org>
William Lee Irwin III wrote:
>> According to Bob Breuer, returning 1 always seems to work for ordinary
>> userspace (as opposed to "unusual" programs). I've got documentation,
>> so I'll brew up something more accurate for it over the weekend.
On Tue, Jan 11, 2005 at 10:02:58PM -0600, Bob Breuer wrote:
> Yes, the easy way out is to return 1 from pte_read. To do it right we will
> need a combined solution for sun4c and sun4m. I think that sun4 can use
> the sun4c version and sun4d will share with sun4m.
> For sun4c, we can use the software managed read bit:
> return pte_val(pte) & _SUN4C_PAGE_READ;
> I can't test this myself, but it mirrors the pte_write functionality.
> For sun4m, there is no software bit for read, so we peek at the hardware
> ACC field from the pte:
> return !(pte_val(pte) & 0x10);
> We need a #define to go with the new usage of this bit, maybe SRMMU_NOREAD?
> I have tested the sun4m solution on my SS20 and it works for me.
> Now, how can these be combined using the btfixup magic?
Ship me what you've got and I'll test it on sun4c and BTFIXUP-ize it.
-- wli
next prev parent reply other threads:[~2005-01-12 5:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-11 14:36 Current BK kernel error Art Haas
2005-01-11 18:49 ` William Lee Irwin III
2005-01-12 3:56 ` Bob Breuer
2005-01-12 5:38 ` William Lee Irwin III [this message]
2005-01-12 6:24 ` William Lee Irwin III
2005-01-12 6:30 ` Bob Breuer
2005-01-21 23:05 ` Art Haas
2005-01-21 23:09 ` William Lee Irwin III
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=20050112053849.GE14443@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.