From: Arnd Bergmann <arnd@arndb.de>
To: linuxppc64-dev@ozlabs.org
Cc: Christopher Friesen <cfriesen@nortel.com>, linuxppc-embedded@ozlabs.org
Subject: Re: modify the cache-inhibit and guard bits from userspace?
Date: Tue, 15 Nov 2005 23:38:53 +0100 [thread overview]
Message-ID: <200511152338.53238.arnd@arndb.de> (raw)
In-Reply-To: <437A5049.9090308@nortel.com>
Am Dienstag 15 November 2005 22:16 schrieb Christopher Friesen:
> What's the most logical way for me to do this? =A0Do I extend mprotect()
> to support additional flags?
>
> Has anyone done this before? =A0I didn't find anything in google.
> Currently the guard bit seems to only be used for ioremap() and in
> __pci_mmap_set_pgprot() if the memory doesn't support write combining.
I have seen an earlier patch that modifies madvise to do this, which seems
a little saner than mprotect, although they can probably both be implemented
in a similar way.
Alternatively, you could write a new file system similar to hugetlbfs and s=
et=20
the cache-inhibit bit in its mmap function.
Arnd <><
next prev parent reply other threads:[~2005-11-15 22:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-15 21:16 modify the cache-inhibit and guard bits from userspace? Christopher Friesen
2005-11-15 22:38 ` Arnd Bergmann [this message]
2005-11-15 23:15 ` Christopher Friesen
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=200511152338.53238.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=cfriesen@nortel.com \
--cc=linuxppc-embedded@ozlabs.org \
--cc=linuxppc64-dev@ozlabs.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).