Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@oss.sgi.com>
To: Jun Sun <jsun@mvista.com>
Cc: linux-mips@oss.sgi.com
Subject: Re: Should /dev/kmem support above 0x80000000 area?
Date: Sat, 9 Dec 2000 00:32:23 +0100	[thread overview]
Message-ID: <20001209003222.A10669@bacchus.dhis.org> (raw)
In-Reply-To: <3A3051C1.DCFC749B@mvista.com>; from jsun@mvista.com on Thu, Dec 07, 2000 at 07:13:05PM -0800

On Thu, Dec 07, 2000 at 07:13:05PM -0800, Jun Sun wrote:

> Currently one cannot read memory area above 0x80000000 throught /dev/kmem.  In
> fact, an earlier bug would put the process into an infinite loop if you try to
> do that.  That seems to be fixed now.
> 
> It seems to be very useful if we do allow that access.  What do you think?

Actually there is almost nothing left that uses /dev/{mem,kmem} these days.
Nevertheless it's a supported interface, so we have to get it right.

> Ralf, if we do want to enable it - which is pretty simple to do -, should I
> give you the patch or shuld I submit it to somebody else who is maintaining
> /dev/kmem?

Send me the patch and I'll comment.

  Ralf

  reply	other threads:[~2000-12-08 23:33 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-08  3:13 Should /dev/kmem support above 0x80000000 area? Jun Sun
2000-12-08 23:32 ` Ralf Baechle [this message]
2000-12-11 11:28   ` Maciej W. Rozycki
2000-12-11 12:41     ` Guido Guenther
2000-12-12  2:26       ` Jun Sun
2000-12-11 18:56         ` Guido Guenther
2000-12-11 19:05         ` Maciej W. Rozycki
2000-12-12  6:16           ` Jun Sun
2000-12-12 11:58             ` Maciej W. Rozycki
2000-12-12 18:53               ` Jun Sun
2000-12-12  7:38   ` Jun Sun
2000-12-12 13:23     ` Maciej W. Rozycki

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=20001209003222.A10669@bacchus.dhis.org \
    --to=ralf@oss.sgi.com \
    --cc=jsun@mvista.com \
    --cc=linux-mips@oss.sgi.com \
    /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