linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Linh Dang" <linh@linhdang.home>
To: "Embedded Linux PPC list" <linuxppc-embedded@lists.linuxppc.org>
Subject: BAT mapping exported to user-space
Date: Mon, 26 Jul 2004 13:20:40 -0400	[thread overview]
Message-ID: <wn5wu0qsn13.fsf@linhd-2.ca.nortel.com> (raw)


Hi all,

In our project, our application continuously does random-access to
various ASICs. The ASICs are mapped by a bat register:

- Forcing the application to use system-calls for accessing the ASICs
  would incur a too-big overhead.

- Adding _PAGE_USER to bat-mapping is ok but would export the mapping
  to every single userspace processes.

- I'm contemplating adding 2 bitmasks (1 read, 1 write) into the
  mm_struct:
  - each bit in the mask represent a BAT register that should be
    accessible from userspace.
  - in switch_mm, prior to the call to set_context(), the BATs's Vp
    bits would be updated based on the masks of the `next' mm.

My questions are:
- has it been discussed/comptemplate/done before?
- what issues (performance,style,...) do you think such a change would
  create?
- How the X server access the hw on PPC?


Thanx

--
Linh Dang

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

             reply	other threads:[~2004-07-26 17:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-26 17:20 Linh Dang [this message]
2004-07-26 18:09 ` BAT mapping exported to user-space Dan Malek
2004-07-26 18:33   ` Linh Dang
2004-07-27  1:18     ` Dan Malek
2004-07-27  2:27       ` Linh Dang
2004-07-27 16:36         ` Dan Malek
2004-07-27 17:34           ` Dang, Linh [CAR:2X23:EXCH]
2004-07-27 18:02             ` Dan Malek
2004-07-27 19:32               ` Linh Dang
2004-07-27 20:09                 ` Dan Malek
2004-07-28  8:12                 ` Oliver Korpilla

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=wn5wu0qsn13.fsf@linhd-2.ca.nortel.com \
    --to=linh@linhdang.home \
    --cc=linuxppc-embedded@lists.linuxppc.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).