Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@oss.sgi.com>
To: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
	Wayne Gowcher <wgowcher@yahoo.com>,
	Linux-MIPS <linux-mips@oss.sgi.com>
Subject: Re: Equivalent of ioperm / iopl in linux mips ?
Date: Mon, 22 Apr 2002 10:44:17 -0700	[thread overview]
Message-ID: <20020422104417.B10146@dea.linux-mips.net> (raw)
In-Reply-To: <Pine.GSO.3.96.1020422170125.7706H-100000@delta.ds2.pg.gda.pl>; from macro@ds2.pg.gda.pl on Mon, Apr 22, 2002 at 05:30:08PM +0200

On Mon, Apr 22, 2002 at 05:30:08PM +0200, Maciej W. Rozycki wrote:

>  Well, for Alpha ioperm/iopl functions check the system type in
> /proc/cpuinfo (we seem to have enough information there as well) and
> failing this they check a result of readlink of /etc/alpha_systype.  Then
> an appropriate region of /dev/mem is mmapped with per-page permissions set
> up as requested if ioperm is used (with a worse granularity, though) and
> subsequent in/out function invocations access the area as appropriate. 
> See sysdeps/unix/sysv/linux/alpha/ioperm.c in glibc for details -- it's a
> pretty clever solution with good performance and only a few trade-offs.

Thanks for volunteering ;)

  Ralf

  parent reply	other threads:[~2002-04-22 17:43 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-21  1:36 set_io_port_base()? Matthew Dharm
2002-02-21  1:57 ` set_io_port_base()? Ralf Baechle
2002-02-21  2:05   ` set_io_port_base()? Matthew Dharm
2002-02-21  2:13     ` set_io_port_base()? Ralf Baechle
2002-02-21  2:27       ` set_io_port_base()? Jun Sun
2002-02-21  2:48         ` set_io_port_base()? Matthew Dharm
2002-02-21  2:48           ` set_io_port_base()? Matthew Dharm
2002-02-21  3:03           ` set_io_port_base()? Jason Gunthorpe
2002-02-21  5:35           ` set_io_port_base()? Jun Sun
2002-02-21  3:30         ` set_io_port_base()? Ralf Baechle
2002-02-21 16:34         ` pthread support in mipsel-linux Wayne Gowcher
2002-02-21 17:55           ` H . J . Lu
2002-02-21 18:12             ` Wayne Gowcher
2002-02-21 18:25               ` H . J . Lu
2002-02-21 18:45                 ` Wayne Gowcher
2002-02-22  8:52                   ` Florian Lohoff
2002-02-22 13:38                 ` Maciej W. Rozycki
2002-02-22 13:45                   ` Hiroyuki Machida
2002-02-22 14:28                     ` Maciej W. Rozycki
2002-02-22 16:53                   ` H . J . Lu
2002-02-22 16:57                     ` H . J . Lu
2002-02-22 17:06                     ` Maciej W. Rozycki
2002-02-22 17:14                       ` H . J . Lu
2002-04-19 17:06             ` Equivalent of ioperm / iopl in linux mips ? Wayne Gowcher
2002-04-20  9:03               ` Geert Uytterhoeven
2002-04-22 11:35                 ` Maciej W. Rozycki
2002-04-22 14:55                   ` Geert Uytterhoeven
2002-04-22 15:30                     ` Maciej W. Rozycki
2002-04-22 15:33                       ` Geert Uytterhoeven
2002-04-22 17:44                       ` Ralf Baechle [this message]
2002-04-22 18:01                         ` Maciej W. Rozycki
2002-02-21  2:08   ` set_io_port_base()? Matthew Dharm
2002-02-21  2:16     ` set_io_port_base()? Ralf Baechle

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=20020422104417.B10146@dea.linux-mips.net \
    --to=ralf@oss.sgi.com \
    --cc=geert@linux-m68k.org \
    --cc=linux-mips@oss.sgi.com \
    --cc=macro@ds2.pg.gda.pl \
    --cc=wgowcher@yahoo.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